Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Ive been racking my brain with this all evening. Power went out with a tstorm today, started back up my server... running apache and a team speak server on it. TS is great, cant see my web page outside my network!

Firewall is disabled on the pc running it (centos btw), apache is running and working. correct ports are forwarded on my router (my isp blocks port 80). Ive tried changing ports, pretty much everything i can think of. httpd.conf is pointing to the correct addy and port, and my domain is pointing to the correct external ip. Im at a loss, any ideas out there?

share|improve this question

Run an external port scan to ensure the correct ports are actually open in your router. Double check the Apache service is up and running and try accessing your website by IP address rather than your domain to rule out DNS issues. That ought to narrow down your problem. It is also likely that your router took a dump on you.

share|improve this answer
Thanks for the reply. Cant access the site outside my network with the ip addy. Also, i cannot see the site from a different pc inside my network now. Changed the dest port to 9999, setup rules on the router to forward 80 and 9999 to the host pc. Also have a forwarding rule 80 -> 9999. Wondering if its godaddy's fault with their dns servers or whats going on. – Evermind Oct 14 '12 at 5:04
hmm. If you can't see it internally that suggests other problems. Can you access your page using localhost on the server? – Scandalist Oct 14 '12 at 5:13
changed the port listened to back to 80, i can see it on my home network once more. So... ive changed the server name to and the port listened to back to 80 as mentioned. Router still has a rule to forward 80 traffic to 9999. still cannot see it outside my network – Evermind Oct 14 '12 at 5:15
This would not work. If your ISP blocks port 80 like you said, you need to have the server listening on port 9999 with a rule in your router to forward 9999. Also keep in mind that if you want to access your server internally, you need to append the port number after the address within your browser. ie: YOURSERVER:9999. By default the browser will try connecting on the standard port. (80) which would not work in your case. – Scandalist Oct 14 '12 at 5:22
i now have myserver:9999 as the name in httpd.conf, ports, and forwarding are correct to bypass the port 80 block. works great inside my lan, outside.. not so much – Evermind Oct 14 '12 at 6:24

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.