On Tue, 2025-04-01 at 22:30 +0200, john doe wrote: > On 4/1/25 21:10, Van Snyder wrote: > > I have a web server listening to port 80 (http) and 443 (https). > > > > I can load pages from it from any computer in my house, all behind > > the > > same router, using its IP number. > > > > I enabled port forwarding in the DMZ in my router for ports 80 and > > 443. > > > > I can't load pages through my router using its WLAN name or WLAN IP > > number. I get "Unable to connect" from Firefox. or "This site can't > > be > > reached" and ERR_ADDRESS_UNREACHABLE from Konqueror. > > > > Do you mean that you want to access your http server from the outside > world (inbound connection).
Yes. > > The below assumes that this is the case. > > > I have mapped port 8079 to port 80 in my router. I can't load page > > using that mapping. > > You need to point your browser to port tcp 8079 with something like > 'http://<IP>:port'. Yes, I do that. And it doesn't work. I only set that up for testing purposes. My router is also configured to forward incoming port 80 to port 80 on my server, and incoming port 443 to port 443 on my server, and those also don't work. > Get it to work with an IP and than move on to DNS. It works with my internal IP number but not with my router's WLAN IP number (or name). nslookup has no trouble finding my WLAN IP number. > > I also map an external port (not 22) to port 22, and I can "ssh" to > > my computer using its WLAN name. > The correct way to access services on your network from the outside > and the inside is to use Split DNS. My internal servers are intentionally entirely invisible outside my router, except via port forwarding, so Split DNS seems to be irrelevant to this problem. I'm not interested in setting up a reverse proxy or an internal DNS resolver. /etc/hosts works fine behind my router. I don't try to access my apache server using ssh. I only used the ssh login to test that my router is working correctly, and correctly forwarding incoming port 22 to port 22 on my server. It does that properly. The mystery is why it appears to refuse to forward ports 80 and 443. > > This was all working until about three weeks ago. I didn't change > > the firmware in my Linksys. > Something has changed, by the sound of what you are discribing it > looks like it was a miracle. > > ARe you using UPNP? No.
