
Starlink Announces 1TB Monthly Cap, Users Who Go Over Will Get Slower Speeds 25¢/GB For Additional Data + more news.Your router redirect rule needs to be tested next. You've eliminated your mac, its firewall, and the apache config. Now hit that machine on your local subnet from a different machine, using local IP address - let's say it's sitting at 10.0.0.100, so from another machine hit » 10.0.0.100:8201īroken? Head over to the Mac board and ask them On your Mac verify apache up, listening on port 8201 by hitting Let's assume the only thing that broke was the very last thing > (cable modem, nothing to see here) -> router (Air Port) port 80 (redirect rule -> local IP:8201) -> your Mac, running Apache listening on *:8201.Īfter upgrading your Mac, this broke. Internet (yes, you want your dns right, but for now assume we're hitting your comcast public IP)

Let's leave off IP addresses and domain names for now, and sketch out who's doing what And since you mentioned that your public IP address changed, triple check your DNS settings, and the Apache config to make sure that something isn't still pointing to the old public IP address. If a port scan also does not show that port as open when the Apache server is running, you may need to run some kind of packet monitor and see exactly what is reaching your web server box while you are doing the port scan.

It does not matter if it is forwarded through a NAT router, or if it is a direct connection - unless an application is running to respond to the port open request, the TCPIP stack will report the connection as closed. That is not how TCP connections work - if an application is not available to respond to a particular port, that port will show as closed to an external port scan. You keep saying that you expect to find the port in question to be open when the Apache server is not running. Am I missing something here? Thanks for the replies!One of us is missing something. The issue is the port being just won't open whereas it did before without Apache being loaded. And Apple has already checked my IP address. Does OP even need to forward 80 to 8021 or can they use port 80? Does Comcast not block inbound port 80? I don't see it in the list but you would think that would be the most obvious port to block. Which is your IP and did it change when you upgraded your OS maybe?

Is it or ? Both seem to be DYN-DNS domains but comes up as IP 216.146.38.x while comes up as 76.

So to be clear, you have inbound TCP/UDP port 8201 from WAN forwarded to LAN port 80 to that specific Apple computer's static IP? Your NOT forwarding inbound 80 to 8201 right? "Yes, Apache is running in OSX.I've used port 8201 for a web hop for years."
