Ubuntu Server works on Lan but not outside

[alphacrucis2]

After reading all the advice (steel driver, your commands just caused the terminal to hang so was slightly confused about that) I am pretty sure the cause of the problem is my router blocking all incoming requests. Would that make sense with the situation?

You do have port forwarding configured on your router right? That is the only way to get from a public internet address to an internal private RFC type address such as 192.168.1.111

[papibe]

Check if your ISP is blocking the port you're using. Check it here: canyouseeme.org.

Sometimes low standard ports like 22, 25 and 80 are blocked. If that your case, changing the port to a higher value, specially on the dynamic range (49152–65535), would solve this.

If your server set to use a DHCP reservation, or an static IP?

Let us know how it goes.
Regards.

EDIT: removed port trigger part.

[saponempotenti]

Check if your ISP is blocking the port you're using. Check it here: canyouseeme.org.

Sometimes low standard ports like 22, 25 and 80 are blocked. If that your case, changing the port to a higher value, specially on the dynamic range (49152–65535), would solve this.

If your server set to use a DHCP reservation, or an static IP?

Let us know how it goes.
Regards.

EDIT: removed port trigger part.

The server is set to a static IP. I tired port 81 but will try a higher range as you suggested. I believe my motherboard failed so it may be a while before I get back to you :'(

EDIT: Was just a graphics card malfunction! Never fixed a computer hardware issue so fast! Also I tried a higher port (49152) and still got a timeout error

[CharlesA]

The server is set to a static IP. I tired port 81 but will try a higher range as you suggested. I believe my motherboard failed so it may be a while before I get back to you :'(

Good luck. My ISP blocks port 80, so I tested my site with port 8080, which is the alternate HTTP port. Worth a shot once you get the machine back up and running.

[saponempotenti]

Good luck. My ISP blocks port 80, so I tested my site with port 8080, which is the alternate HTTP port. Worth a shot once you get the machine back up and running.

Have tried multiple ports that my ISP should not be blocking.. also called the ISP and after talking to a tech, he assured me that there is no port blocking in the first place. I have scanned the ports on my router as well as on the server and both of them show ssh and http open. When I send a request to the router from an external machine it gets a timeout error every time though.

[CharlesA]

Have tried multiple ports that my ISP should not be blocking.. also called the ISP and after talking to a tech, he assured me that there is no port blocking in the first place. I have scanned the ports on my router as well as on the server and both of them show ssh and http open. When I send a request to the router from an external machine it gets a timeout error every time though.

If they aren't blocking ports and canyouseeme.org shows them as open, the problem must lie elsewhere.

[saponempotenti]

If they aren't blocking ports and canyouseeme.org shows them as open, the problem must lie elsewhere.

canyouseeme.org does not see them because it gets a time out error

[papibe]

canyouseeme.org does not see them because it gets a time out error

That could be a sign of blockage, actually.

Did you try ports on the dynamic range?

Another thoughts:

• Make sure your static IP is outside the DHCP range of the router.
• I would always prefer to set a DHCP reservation, since that way you are sure that the router "knows" the machine.

Regards.

[saponempotenti]

That could be a sign of blockage, actually.

Did you try ports on the dynamic range?

Another thoughts:

• Make sure your static IP is outside the DHCP range of the router.
• I would always prefer to set a DHCP reservation, since that way you are sure that the router "knows" the machine.

Regards.

Ahhhh.. I set up a DHCP reservation and removed the static ip from the server.. its ip is still .111 though. I have tried a DMZ as well as using a range. Still has the same issues.

[saponempotenti]

I'm not a routing expert but that looks OK to me (mine is analogous - assuming 192.168.1.1 is your router/gateway and 192.168.1.111 is the machine's LAN IP)

It still may be worth a quick check on firewall status - since other tools can mess with iptables let's look right down at that level if possible e.g.

$ sudo iptables -L | grep -E 'dpt:((ssh)|(http))'

$ sudo ufw status numbered

paulson@ProQuaerendumScientiam:~$ sudo iptables -L | grep -E 'dpt:((ssh)|(http))'
paulson@ProQuaerendumScientiam:~$ sudo ufw status numbered
Status: inactive
paulson@ProQuaerendumScientiam:~$

Should the status be inactive?