Report post

You have 30 minutes to complete this form before the CAPTCHA will expire.

Security image * Required field


This is a reported post for a post in the topic <input class="cms_keep_ui_controlled" size="45" title="[post param="NextCloud"]295[/post]" type="button" value="post Comcode tag (dbl-click to edit/delete)" />, by jacobgkau<br /><br /><comcode-quote param="2"><comcode-quote param="1123artc">I was under the impression I wouldn’t be able to use the public router IP address, so that’s good to know for sure that I can. As I said I’ve got my domain name, and following your tutorial, I learned how to point it to an IP address. I’ll have to do some tests to see if I can get my router IP address to remain static, but if not I’ll look more into dynamic DNS resolvers.<br /><input class="cms_keep_ui_controlled" size="45" title="[snapback]294[/snapback]" type="button" value="snapback Comcode tag (dbl-click to edit/delete)" /></comcode-quote><br />Some ISPs don't really like people hosting things, but Charter/Spectrum and AT&T were both fine with it when I was doing it. The best thing to do is to just do it and see if you hear from them. I used to hear that IP addresses changed often for residential connections, but Charter/Spectrum only changed mine once or twice in the 4 years that I was hosting NOTS servers at that home. Your best bet to avoid having your public IP change is to avoid rebooting your modem and avoid releasing/renewing your IP on your router (so, basically, the exact opposite behavior of if you wanted to intentionally get your IP changed.) I used NoIP briefly, but I don't remember much about it, as that was before I purchased nerdonthestreet.com (before it was available for purchase, actually) and I was only using it for a Minecraft server.<br /><comcode-quote param="1123artc">I was able to log into my router last night and figure out how things work. I’ll have to spend some more time on port forwarding to set it up correctly.<br /><input class="cms_keep_ui_controlled" size="45" title="[snapback]294[/snapback]" type="button" value="snapback Comcode tag (dbl-click to edit/delete)" /></comcode-quote><br />Yep, TCP Port 80 is used for HTTP and TCP Port 443 is used for HTTPS. You can find lists of common ports online, in case you ever want to host any other services (although some ISPs block things like email ports; Charter/Spectrum only allowed outgoing home-hosted email through their designated gateway, ostensibly to prevent spam.) Like I said, it just needs to point to the private/internal IP of your web server. Your router actually tracks every outgoing connection you make in order to route responses to the correct devices, but when it receives unsolicited traffic, it doesn't know which internal device to route it to until you set up port forwarding.<br />What's going on is actually called Port Address Translation (PAT), also called NAT Overload (older versions of NAT were designed to translate many internal IPs to X number of external IPs, where only X number of people can have connections open at once; PAT is generally used when you only have a single external IP, as is the case with home connections, and allows thousands of simultaneous connections from the same IP.) When you connect to nerdonthestreet.com, your router sends a packet with a random source port and a destination port of 80, and NOTS replies with source port 80 and the destination port set to whatever your random source port was. Port forwarding kind of sidesteps that process; when you connect to your own domain name from outside, you're using a destination port of 80, and when your web server responds, it's using a source port of 80, which is the only time you'll actually see outgoing traffic from your home connection on port 80… generally, only one device on your network can be bound to port 80 at a time, hence the port forwarding to a single private IP so your router knows where port 80 is served from. (This example was for HTTP, all the 80's are 443's for HTTPS.)<br />That last paragraph wasn't really necessary, but I'm glad that I typed it, because I remembered that you might not be able to connect to your domain name from inside your network! If your domain name is set to your public IP and you can ping it from outside your network but not from inside, the easiest solution is to edit your hosts file and tell your computer to resolve your domain name to the private IP address instead. (I assume your ISP and/or your router gets confused when it tries to send a NAT-ed packet from your public IP to your public IP; setting the hosts file avoids that by telling your computer to go directly to your web server without touching the internet.) Just do a web search for "Linux hosts file," or "Windows hosts file" if you're using Windows.<br />Sorry for the rant in the middle there, but I'm glad to help. Hope you get everything up and running how you want it.<br /></comcode-quote><br />//// PUT YOUR REPORT BELOW \\\\<br /><br /> Add: Add: Font Size Color This is a reported post for a post in the topic [post param="NextCloud"]295[/post], by jacobgkau [quote="2"] [quote="1123artc"] I was under the impression I wouldn’t be able to use the public router IP address, so that’s good to know for sure that I can. As I said I’ve got my domain name, and following your tutorial, I learned how to point it to an IP address. I’ll have to do some tests to see if I can get my router IP address to remain static, but if not I’ll look more into dynamic DNS resolvers. [snapback]294[/snapback][/quote] Some ISPs don't really like people hosting things, but Charter/Spectrum and AT&T were both fine with it when I was doing it. The best thing to do is to just do it and see if you hear from them. I used to hear that IP addresses changed often for residential connections, but Charter/Spectrum only changed mine once or twice in the 4 years that I was hosting NOTS servers at that home. Your best bet to avoid having your public IP change is to avoid rebooting your modem and avoid releasing/renewing your IP on your router (so, basically, the exact opposite behavior of if you wanted to intentionally get your IP changed.) I used NoIP briefly, but I don't remember much about it, as that was before I purchased nerdonthestreet.com (before it was available for purchase, actually) and I was only using it for a Minecraft server. [quote="1123artc"] I was able to log into my router last night and figure out how things work. I’ll have to spend some more time on port forwarding to set it up correctly. [snapback]294[/snapback][/quote] Yep, TCP Port 80 is used for HTTP and TCP Port 443 is used for HTTPS. You can find lists of common ports online, in case you ever want to host any other services (although some ISPs block things like email ports; Charter/Spectrum only allowed outgoing home-hosted email through their designated gateway, ostensibly to prevent spam.) Like I said, it just needs to point to the private/internal IP of your web server. Your router actually tracks every outgoing connection you make in order to route responses to the correct devices, but when it receives unsolicited traffic, it doesn't know which internal device to route it to until you set up port forwarding. What's going on is actually called Port Address Translation (PAT), also called NAT Overload (older versions of NAT were designed to translate many internal IPs to X number of external IPs, where only X number of people can have connections open at once; PAT is generally used when you only have a single external IP, as is the case with home connections, and allows thousands of simultaneous connections from the same IP.) When you connect to nerdonthestreet.com, your router sends a packet with a random source port and a destination port of 80, and NOTS replies with source port 80 and the destination port set to whatever your random source port was. Port forwarding kind of sidesteps that process; when you connect to your own domain name from outside, you're using a destination port of 80, and when your web server responds, it's using a source port of 80, which is the only time you'll actually see outgoing traffic from your home connection on port 80... generally, only one device on your network can be bound to port 80 at a time, hence the port forwarding to a single private IP so your router knows where port 80 is served from. (This example was for HTTP, all the 80's are 443's for HTTPS.) That last paragraph wasn't really necessary, but I'm glad that I typed it, because I remembered that you might not be able to connect to your domain name from inside your network! If your domain name is set to your public IP and you can ping it from outside your network but not from inside, the easiest solution is to edit your hosts file and tell your computer to resolve your domain name to the private IP address instead. (I assume your ISP and/or your router gets confused when it tries to send a NAT-ed packet from your public IP to your public IP; setting the hosts file avoids that by telling your computer to go directly to your web server without touching the internet.) Just do a web search for "Linux hosts file," or "Windows hosts file" if you're using Windows. Sorry for the rant in the middle there, but I'm glad to help. Hope you get everything up and running how you want it. [/quote] //// PUT YOUR REPORT BELOW \\\\ Use of this website implies that you agree to the website rules and privacy policy.

Report post

Statistics