dagadaga
asked on
Looking for alternatives to host a website when ISP block port 80
Dear Experts,
I use Apache on Red Hat Linux 7.2 to host my website. since My ISP, Adelphia, does not offer static IP, I signed up at www.no-ip.com to use their free DNS service.
The only thing that I changed was the server name on httpd.conf (I put dagadaga.no-ip.com as the server name) Then I did a ./etc/init.d/httpd restart to restart the daemon.
I can find my website, so far so good.
when I go to my friend's house, however, I caanot find my website anymore.
I then did a tracert on my friend's windows system and I was able to trace all the way back to my IP (I tested using both the IP address and website address and both worked).
I also did a ping and was able to receive response from my computer.
Interestingly, I can do a telnet to my host from my friend's house without any problems.
Given these observations, can anyone tell me if my ISP blocked my Port 80? Or is there a step that I'm missing? Any alternatives to go around if my ISP really blocked Port 80?
Thank you in advance and I appreciate every feedback!
dagadaga
I use Apache on Red Hat Linux 7.2 to host my website. since My ISP, Adelphia, does not offer static IP, I signed up at www.no-ip.com to use their free DNS service.
The only thing that I changed was the server name on httpd.conf (I put dagadaga.no-ip.com as the server name) Then I did a ./etc/init.d/httpd restart to restart the daemon.
I can find my website, so far so good.
when I go to my friend's house, however, I caanot find my website anymore.
I then did a tracert on my friend's windows system and I was able to trace all the way back to my IP (I tested using both the IP address and website address and both worked).
I also did a ping and was able to receive response from my computer.
Interestingly, I can do a telnet to my host from my friend's house without any problems.
Given these observations, can anyone tell me if my ISP blocked my Port 80? Or is there a step that I'm missing? Any alternatives to go around if my ISP really blocked Port 80?
Thank you in advance and I appreciate every feedback!
dagadaga
ASKER
jlevie, thanks for your feedback.
1. my /var/www/html directory has the following configurations:
Options Indexs FollowSymlinks
AllowOverride None
Order allow, deny
Allow from now
So I guess like you said, everyone can asscess my website, supposely.
2. I took out the firewall. But the result did not improve. my friend still cannot find the website.
3. I checked the httpd.conf file and there are many places tha listen to port 80. Which ones should be changed? and what is the range of the port? Can I just randomly pick one?
Thanks,
dagadaga
1. my /var/www/html directory has the following configurations:
Options Indexs FollowSymlinks
AllowOverride None
Order allow, deny
Allow from now
So I guess like you said, everyone can asscess my website, supposely.
2. I took out the firewall. But the result did not improve. my friend still cannot find the website.
3. I checked the httpd.conf file and there are many places tha listen to port 80. Which ones should be changed? and what is the range of the port? Can I just randomly pick one?
Thanks,
dagadaga
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
did you try to reload you web server everytime the computer connect to the network, using `kill -HUP pid`. This will force the web server to re-binding to new ip interface.
oh, missed some of your text that you did restart the web server. I assume that you are 100% sure the connection was up since the time you restarted web server to when you try from your friend's house. At installation time, RH did ask you about security level which will help the installation to implement a default firewall rule set using ipchains/iptables. These rule may block out access from anywhere else but you localhost! check this with ipchains/iptables (`ipchains -L` or `iptables -L`)! hope it help!
mmmmmm..... what the heck am i doing.... repeat other peoples words... so sorry!
ASKER
jlevie and hnminh,
Thanks for the feedback, I appreciate your information.
I did as you two mentioned and the daemon restarted without any problem. The weired thing was that when I checked the error log (located at /var/log/httpd/error_log),
[crit] (98) Address already in use: make_sock: could not bind to port 12598.
I tried several other ports and the error logs continues to show the same message with the port number that I changed to.
Any ideas to correct this error?
dagadaga
Thanks for the feedback, I appreciate your information.
I did as you two mentioned and the daemon restarted without any problem. The weired thing was that when I checked the error log (located at /var/log/httpd/error_log),
[crit] (98) Address already in use: make_sock: could not bind to port 12598.
I tried several other ports and the error logs continues to show the same message with the port number that I changed to.
Any ideas to correct this error?
dagadaga
Surely, the fact you are using the freedns service name as a your hostname means that you would have to be connected and sync'd to the freedns service BEFORE starting the apache webserver, as it would only read it once on startup.
Try telnetting to port 80 from your friends connection, see if you get some http headers back or not.
I may be wrong on the apache config front, but thats what i thought would happen.
Try telnetting to port 80 from your friends connection, see if you get some http headers back or not.
I may be wrong on the apache config front, but thats what i thought would happen.
Oh yeah, sorry , forgot, make sure you can resolve the freedns name-to-ip from the webserver itself.
sorry I did not have notif email that there were comments :(
Using `netstat -a` and `pas xua` right after you stop httpd to see if httpd is still running or the port specified in httpd.conf is used by other process. it's help if you could post the output of the 2 commands here.
Using `netstat -a` and `pas xua` right after you stop httpd to see if httpd is still running or the port specified in httpd.conf is used by other process. it's help if you could post the output of the 2 commands here.
dagadaga:
This old question needs to be finalized -- accept an answer, split points, or get a refund. For information on your options, please click here-> http:/help/closing.jsp#1
EXPERTS:
Post your closing recommendations! No comment means you don't care.
This old question needs to be finalized -- accept an answer, split points, or get a refund. For information on your options, please click here-> http:/help/closing.jsp#1
EXPERTS:
Post your closing recommendations! No comment means you don't care.
This question has been classified abandoned. I will make a recommendation to the moderators on its resolution in a week or two. I appreciate any comments that would help me to make a recommendation.
Unless it is clear to me that the question has been answered I will recommend delete. It is possible that a Grade less than A will be given if no expert makes a case for an A grade. It is assumed that any participant not responding to this request is no longer interested in its final disposition.
If the user does not know how to close the question, the options are here:
https://www.experts-exchange.com/help/closing.jsp
drewber
Unless it is clear to me that the question has been answered I will recommend delete. It is possible that a Grade less than A will be given if no expert makes a case for an A grade. It is assumed that any participant not responding to this request is no longer interested in its final disposition.
If the user does not know how to close the question, the options are here:
https://www.experts-exchange.com/help/closing.jsp
drewber
Order allow,deny
Allow from all
then anyone can access the server.
It is possible, however, that you may have installed the default firewall on 7.2 that could be blocking access. An easy way to check for that being a problem is just to make sure that there is no firewall running with '/etc/init.d/ipchains stop'. That will shutdown the firewall and you can see if it's the problem. Be aware that a reboot will start the firewall unless that service is disabled.
If there's no firewall in the way and you still can't connect to your web server, then yes, it's likely that your ISP blocks inbound traffic on port 80. You could try having Apache listen on some odd port, like say 19191 (change 'Port 80' to 'Port 19191' and restart Apache) and see if that works.