Apache :: Apache 2.2.4 Conection Issues

PCJunkie · Joined: 10 Jan 2007 Posts: 8

Hey guys, I ahve posted this before and didn't get a response. Yet I'll reask it as it is a bit different problem than before.

First off my site is http://nickspublicrealm.com

I had determined that my ISP blocks port 80 so I changed my forewarding port to 60080, as well as my listening port in apache and on my firewalls. I can see my web site over a dial-up ISP via my PDA, Over my network (Obviously), and from 2 friends houses. However, I can not see it from work. I work for a large corporation who likes to block all kinds of keywords with websense and such, but, my server isn't being blocked, it's getting a can not find error. If I Run/Cmd ping www.nickspublicrealm.com at work though, it will sucessfully ping and return my IP.

I'm lost for posible causes. It's not a big deal that I can't see it from work but rather, if I can't see it from work than where else is it not available?

Does anyone have any suggestions? Also, can you see my site from your locations? Thanks guys!

tdonovan

Perhaps a lower port number will help. The three catagories of port numbers are:

Well Known Ports

Registered Ports

Dynamic/Private Ports

Maybe the Dynamic/Private ports are being blocked by your employer.

Try a port in the Registered range (like port 8080), or even one from the Well Known range which is not commonly used (like port 81).

Another possibility is using SSL. The https port (port 443) is often unblocked even when your ISP blocks port 80.

-tom-

PCJunkie · Joined: 10 Jan 2007 Posts: 8

Thank you Tom, I will try switching ports around. I never knew that ports had different categories, and now that I think about it, it sounds like a very good possibility.

Now, I haven't done anything with https as of yet. If I switch to port 443, does this make my site secure all on it's own? Or am I reading your reply wrong?

James Blond

Nope! Only switching the port does not make it secure. Only installing SSL on Apache makes it more secure.

PCJunkie · Joined: 10 Jan 2007 Posts: 8

UPDATE...

I change my port a few times and finally settled on port 81. I used canyouseeme.com to see if the ports were being blocked through my isp and through work and both places have port 81 open. So the port is no longer the issue if it was before. I am guessing that work probably will not accept sites without a certificate?

I downloaded the 2.2.4 server built with openssl that is on apache lounge here and successfully installed it as per the instructions included in the download.

Now I need to create a certificate. As I understand so far, I should have a file on my server somewhere called openssl.cnf? I do not have it. Every site I look at that explains openssl and apache on windows xp sais something completely different. Can you guys help me out with this or link me to a how to that is going to work for me?

tdonovan

hmmmm... your problem may be a bit more complex than it first appeared.
It looks like you go through a dynamic DNS service - DynDNS.

When you request http://nickspublicrealm.com the request really goes to DynDNS
- which creates a browser frame and directs the frame to be filled from port 81 at your current IP address.

In your browser menu, choose [View] [Page Source] and you will see something like ths:

PCJunkie · Joined: 10 Jan 2007 Posts: 8

Ok, I finally got the connection issue all cleared up. It seems that here at work we are using a proxy server. It was a simple matter of bypassing the proxy in IE6 tools.

Now onto finished ssl. Thanks for the info. Unfortunately I have to wait to get home in the morning to do it. You guys are great!!!!