On Tue, 2025-04-01 at 20:21 -0400, Timothy M Butterworth wrote: > Ok so if I understand you correctly then you are attempting to port > forward 80 and 443 through the router's WAN Wide Area Network > interface to a server located in the DMZ DeMilitarized Zone. Does the > server have Apache ACL's, IP Tables or TCP wrapper running on it? Can > you try to do a port ping or use telnet to connect to port 80 to test > connectivity. ex: `telnet <Routers WAN IP Address or Public DNS Name> > 80`. As you say that the server is on the inside of your network. > Have you tried placing the server in the DMZ?
The server is on the LAN side of the router (192.168.1.65). It's not in the DMZ. My server isn't running Apache ACLs or iptables or TCP wrapper. The router is running a firewall. I've forwarded WAN-side ports 23, 80 and 443 to my server, and another non-22 WAN-side port to port 22 on my server. I can view pages from my server on itself or other computers in my house using 192.168.1.65 (the LAN side of the router), but not 47.229.8.99 (the WAN side of the router). telnet vandyke.mynetgear.com Trying 47.229.8.99... telnet: Unable to connect to remote host: Connection refused telnet vandyke.mynetgear.com 80 telnet: Unable to connect to remote host: No route to host telnet vandyke.mynetgear.com 443 telnet: Unable to connect to remote host: No route to host Maybe my server isn't listening for telnet. I installed telnet and telnetd, but "systemctl start telnetd" said there's no such thing. I can ssh to my server through the router on a non-22 port that is mapped to port 22 on my server. ssh -p #### vandyke.mynetgear.com
