Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
can see site on intranet, but not on internet?
- Thread starter vague
- Start date
sleipnir214
Programmer
Are you using the same IP for both inside and outside?
Hi,
You might try using https in the ULR. If you did an upgrade to your system, it is likely you are running SSL Secure Socket Layer. Also, if you are using a router to forward to your local web server from a static IP, you may need to connect you web server directly, bypassing the router, and assign you web server the static IP address.
Leland F. Jackson, CPA
Software - Master (TM)
Nothing Runs Like the Fox
You might try using https in the ULR. If you did an upgrade to your system, it is likely you are running SSL Secure Socket Layer. Also, if you are using a router to forward to your local web server from a static IP, you may need to connect you web server directly, bypassing the router, and assign you web server the static IP address.
Leland F. Jackson, CPA
Software - Master (TM)
Nothing Runs Like the Fox
sleipnir214
Programmer
Well that post muddied the waters nicely to no good use.
Leland, SSL doesn't just happen. It has to be set up. Unless some upgrade somewhere mangled the httpd.conf beyond all recognition, then SSL has nothing to do with it.
I'm betting with ElectusUnum -- there's an unexpected firewall somewhere.
Leland, SSL doesn't just happen. It has to be set up. Unless some upgrade somewhere mangled the httpd.conf beyond all recognition, then SSL has nothing to do with it.
I'm betting with ElectusUnum -- there's an unexpected firewall somewhere.
I recently upgraded to RedHat 7.3 with a clean install, and it comes with a default test certificate. I was down for a week because everything appeared normal within the local network. However, my web site stopped receiving hits. This went on for about a week before I tried accessing my site from outside the local network, and I was unable to do so. When using netscape I got a message of "unable to connect to the server." With IE I got the usual message of "page cannot be displayed."
I then worked with Cox Communications who provides my static IP address. I had a router configured with the static IP address, and the router would forward all port 80 to the intranet web server.
In working with Cox's Tech support they had me connect the cable modem directly to the web server, bypassing the router, and they were able to ping me. Most router will not reply to pings as a matter of security. Then Cox's Tech support was able to access my web page by using a ULR of However, this would not work when I had the network configured so the router forward the ULR to the web server, evidentially the router strips the s from the https so the connection could not be made unless the web server were directly connected to the cable modem.
This behavior appear to be the default with RedHat 7.3. I have never had this problem with any eariler version of RedHat.
I have been trying to determine if it is possible to disable openssl, but I have not yet discovered how to do so. According to the doc, I need at least a test certificate before I can start the httpd daemon. I checked that out by scrambling the ssl keys, and sure enough, I could not start httpd.
If anyone else has had this problem and has learned how to trun off SSL, I would appreciate you sharing it with me.
Leland F. Jackson, CPA
Software - Master (TM)
Nothing Runs Like the Fox
I then worked with Cox Communications who provides my static IP address. I had a router configured with the static IP address, and the router would forward all port 80 to the intranet web server.
In working with Cox's Tech support they had me connect the cable modem directly to the web server, bypassing the router, and they were able to ping me. Most router will not reply to pings as a matter of security. Then Cox's Tech support was able to access my web page by using a ULR of However, this would not work when I had the network configured so the router forward the ULR to the web server, evidentially the router strips the s from the https so the connection could not be made unless the web server were directly connected to the cable modem.
This behavior appear to be the default with RedHat 7.3. I have never had this problem with any eariler version of RedHat.
I have been trying to determine if it is possible to disable openssl, but I have not yet discovered how to do so. According to the doc, I need at least a test certificate before I can start the httpd daemon. I checked that out by scrambling the ssl keys, and sure enough, I could not start httpd.
If anyone else has had this problem and has learned how to trun off SSL, I would appreciate you sharing it with me.
Leland F. Jackson, CPA
Software - Master (TM)
Nothing Runs Like the Fox
sleipnir214
Programmer
Leland, if Apache is not doing to suit you, reconfigure it. I guarantee you that regardless of the fact that Apache has SSL installed on it, you can serve out port 80 cleartext HTTP on it. You just have to tweak your configuration.
If you can hit a web server on port 80 on a routeable IP address from inside your network, but can't from outside the network, then the problem is not with your web server. It's most likely a firewall misconfiguration on your border or possibly a network adapter misconfiguration on the server.
Speaking of which...Vague...You do have a default gateway set on that web server machine, right?
Other more obscure problems are if you use a new NIC to server the same IP address from a machine. ARP caching in your router will give you headaches.
Leland, you don't point a web browser to a "ULR". The acronym is "URL".
If you can hit a web server on port 80 on a routeable IP address from inside your network, but can't from outside the network, then the problem is not with your web server. It's most likely a firewall misconfiguration on your border or possibly a network adapter misconfiguration on the server.
Speaking of which...Vague...You do have a default gateway set on that web server machine, right?
Other more obscure problems are if you use a new NIC to server the same IP address from a machine. ARP caching in your router will give you headaches.
Leland, you don't point a web browser to a "ULR". The acronym is "URL".
- Status
Similar threads
- Locked
- Question