[Miniryu]

Ok, actually I do get it. Its just that it won't work outside of the network at our house.
I did everything that the instructions say to, and the site I put into the "Sites" folder on my computer loads fine from other computers on my network. The problem comes when people from outside our network try to access my website. They get a message that says there is no access to the server, or something similar.

I've tried it multiple times, using differnt site folders for different users. I have also checked the permissions of the files being served themselves- and everyone has access to them. We have Comcast cable internet, could our ISP be the problem?

[Spliffdaddy]

Is port 80 open to outside connections on your router?

It's rare for an ISP to block personal webservers. FTP, sometimes, but not http.

[crayz]

If you could tell us what the actual error message is, it would be useful in trying to determine whether it's a problem w/ your machine, your network, or your ISP. My guess is network - make sure you're doing port forwarding so a connection to your IP on port 80 gets sent to your web server box

[tRr]

Originally posted by Spliffdaddy:
Is port 80 open to outside connections on your router?

It's rare for an ISP to block personal webservers. FTP, sometimes, but not http.

I remember when code red was all the rage, a lot did, though that could (should...) have been temporary.

[intake]

Originally posted by Miniryu:
We have Comcast cable internet, could our ISP be the problem?

You did everything else correct. But yes, Comcast blocks inbound Port 80 requests. You can circumvent this by changing the webserver to another port, like 8080. I don't remember how to change the port for Apache at the moment, but I'm sure one of the guys in here can advise.

Also, unless you have you make connected directly to the Comcast modem, you will need to to forward the correct ports in you router/firewall device to point to your computer.

[Xeo]

Originally posted by intake:
You did everything else correct. But yes, Comcast blocks inbound Port 80 requests. You can circumvent this by changing the webserver to another port, like 8080. I don't remember how to change the port for Apache at the moment, but I'm sure one of the guys in here can advise.

You'll need to edit /etc/httpd/httpd.conf. Just look for "Port 80" and replace it with whatever port you like. Commonly this is 8080.

If you aren't familiar with editing text files as root or with command line text editors, here's a one line copy and paste method which will do it for you:

sudo perl -pi -e 's/Port 80/Port 8080/' /etc/httpd/httpd.conf

Just enter your password when it asks. You'll have to turn web sharing off and back on before you will see the changes. If it isn't obvious, you can change it back by swapping the two "Port ##" and you can change it to whatever port you like as well.

[juanvaldes]

Are you in the DMZ?

[mitchell_pgh]

I'm on Comcast and they don't block my port 80...

You need to forward the port in your router to the computer you are using (obviously you can't have both serving content)

[Xeo]

Originally posted by mitchell_pgh:
I'm on Comcast and they don't block my port 80...

You need to forward the port in your router to the computer you are using (obviously you can't have both serving content)

My dad is on Comcast and his is blocked. Apparently Comcast doesn't have a strict set of rules for it... either that or 80 has opened up in the last few months. It's been a while since I checked.

Either way, yes, the ports need to be opened, whether they be 80 or 8080 or 12345

[intake]

Originally posted by Xeo:
You'll need to edit /etc/httpd/httpd.conf. Just look for "Port 80" and replace it with whatever port you like. Commonly this is 8080.

Thanks Xeo, I haven't had the need to do this yet, and forgot to look there.

As for the Comcast port blocking issue, I have a couple of family members that I just got installed and Comcast and they are locked on 80. Your are one of the lucky one. That's or they realize that you are on a Mac and don't have lame IIS problems to deal with.

[spiky_dog]

i have comcast and port 80 (along with all other ports afaik) are unblocked. i would suspect a port forwarding, or, rather, the lack of it, issue to be the problem here. but if switching to a nonstandard port does the trick, then so be it.

[Miniryu]

Originally posted by Xeo:
You'll need to edit /etc/httpd/httpd.conf. Just look for "Port 80" and replace it with whatever port you like. Commonly this is 8080.

If you aren't familiar with editing text files as root or with command line text editors, here's a one line copy and paste method which will do it for you:

sudo perl -pi -e 's/Port 80/Port 8080/' /etc/httpd/httpd.conf

Just enter your password when it asks. You'll have to turn web sharing off and back on before you will see the changes. If it isn't obvious, you can change it back by swapping the two "Port ##" and you can change it to whatever port you like as well.

Thanks for all the help, everyone here is awesome.
I just tried doing this, and it doesn't work. I am assuming that this means all I have to do now is have the port fowarded. Of course I don't know how to do this and I am willing to bet that the guy in our house who is in charge of the internet doesn't know how to do this either.

[spiky_dog]

Originally posted by Miniryu:
Thanks for all the help, everyone here is awesome.
I just tried doing this, and it doesn't work. I am assuming that this means all I have to do now is have the port fowarded. Of course I don't know how to do this and I am willing to bet that the guy in our house who is in charge of the internet doesn't know how to do this either.

step 1: change port back to 80. (do the above command but with the Port 80 and Port 8080 swapped.)

step 2: log into your router. if you check your network preferences you'll see an entry for "gateway". chances are that this is your router. consult your router's manual for the username and password to use, usually something like admin for both.

step 3: forward public port 80 (on the router) to private port 80 (on your own computer's private ip address, likely something 10.10.0.101ish, or 192.168.0.101ish. consult your network preferences to find this, of course.) once again your router's manual will have more detailed and specific instructions. dig it up.

[+ spiral +]

I bet you are using a local IP address (192.etc). You need to use the IP of what your computer is outside your network. On the machine where your pages sit, go to http://www.whatismyip.com .

I have an apple scipt in my menubar that tells me what my external IP is so people can access files.

[tooki]

Would you mind posting that script so that others can do the same? That would be really handy!

tooki

[Miniryu]

Originally posted by + spiral +:
I bet you are using a local IP address (192.etc). You need to use the IP of what your computer is outside your network. On the machine where your pages sit, go to http://www.whatismyip.com .

I have an apple scipt in my menubar that tells me what my external IP is so people can access files.

You are correct- I am using a local IP (I am assuming since it starts with 192.xx.x.x.x) I found my external IP (awesome link) and I tried plugging it into the url that is supposed to link to your webpage:
http://xx.xx.xxx.xxx/~mydirectoryname/

but it asks for authentification. and I apparently don't know the password/username.

[Xeo]

Originally posted by Miniryu:
but it asks for authentification. and I apparently don't know the password/username.

That is your router. The username is generally blank and the password is generally "admin". You should change the password if you never have before (if it's wireless). And from that router page, you can change the port forwarding as has been suggested in this thread.

Accessing your public IP from inside your LAN will result in talking to your router. The router won't forward the ports back into your LAN. I run in to this all the time. To test your setup, you need to try to access that public IP from a computer outside your system.

[ebsidohw]

I have the same problem with my personal web sharing. I set my laptop to use port 8080 as pot 80 is already taken by my router machine running another website. the laptop only runs personal web so I can easily share files with friends by giving the a URL. However, they can't access it.

I have my router box set to forword port 8080 to my ibook, apache is set to listen to port 8080, and i can view my pweb perfectly fine within the lan, its just outside the lan where I run into problems.

[Xeo]

Originally posted by ebsidohw:
I have the same problem with my personal web sharing. I set my laptop to use port 8080 as pot 80 is already taken by my router machine running another website. the laptop only runs personal web so I can easily share files with friends by giving the a URL. However, they can't access it.

I have my router box set to forword port 8080 to my ibook, apache is set to listen to port 8080, and i can view my pweb perfectly fine within the lan, its just outside the lan where I run into problems.

How are you trying to access from the outside? From the inside using the public IP? Or using a computer which is actually outside the LAN?

[Miniryu]

Originally posted by Xeo:
That is your router. The username is generally blank and the password is generally "admin". You should change the password if you never have before (if it's wireless). And from that router page, you can change the port forwarding as has been suggested in this thread.

Accessing your public IP from inside your LAN will result in talking to your router. The router won't forward the ports back into your LAN. I run in to this all the time. To test your setup, you need to try to access that public IP from a computer outside your system.

Well it's not 'admin'. Too bad. I'll just hafta wait until the real 'admin' gets back from spring break.

[ebsidohw]

Originally posted by Xeo:
How are you trying to access from the outside? From the inside using the public IP? Or using a computer which is actually outside the LAN?

I remote desktop to my PC at work, and try accessing my Mac from the pc at work. So, from outside.

When I'm in the lan, everything works peachy. Its just when u try to get in from outside. I've also had friends try accessing me from their computers when I'm at home, same thing happens.

[Miniryu]

For the record, I got it working beautifully! I fowarded the port, and then had to substitute my external IP in the link to files I was serving. Thank you all for your help.

[the_glassman]

I used to host my page through road runner without a problem, I have switched to DSL and it seems no matter what I do I can't access my page externally.
I've switched ports, and my dns update is running successfully. Any thoughts?

[the_glassman]

Originally posted by the_glassman:
I used to host my page through road runner without a problem, I have switched to DSL and it seems no matter what I do I can't access my page externally.
I've switched ports, and my dns update is running successfully. Any thoughts?

Got it to work, now just need to work on masking the :8080 part.

[Graymalkin]

Tip for modifying hardware routers (Neatgeat, Linksys, D-Link, etc) when you've lost the admin password: told down the reset button on the back of the router until all the lights flash or turn off and back on. The reset switch when tapped will just restart the router, holding the switch will reset it to the factory settings. A search on Google will find you the most commonly used administration passwords and user names for these routers. Most companies use the same combinations for all of their products.

Don't be a jerk and use this method to mess with settings of things you don't own. It's a troubleshooting tip, not to a mischief causing tip. Resetting the router will erase all of your custom settings like forwarded ports, ISP authentication, and DHCP settings. When used properly it can help out people that need to adjust their settings but have lost their password. When used to be a jerk it can effectively keep people from accessing the internet and break their network settings.

[Gavin]

Originally posted by Xeo:
Accessing your public IP from inside your LAN will result in talking to your router. The router won't forward the ports back into your LAN. I run in to this all the time. To test your setup, you need to try to access that public IP from a computer outside your system.

Here's a trick.
You can see your site from the outside by using a translator:

http://babelfish.altavista.digital.com/

just pick 'spanish to english' as the language to leave it in english.

[Gavin]

Originally posted by Miniryu:
Well it's not 'admin'. Too bad. I'll just hafta wait until the real 'admin' gets back from spring break.

Most people never change the default password. Maybe you can get it from the manual. You can usually get the manual as a pdf file on the manufacturer's website.


try
name:admin
pass:admin

then try it with caps.


For those of you trying another port (8080, etc.) Did you remember to open that port in the firewall?

Under the sharing control panel, firewall tab. Click the 'new' button.
Port name = Other
Port num=8080
Description= 'My wide open web hole!' ...or something.

Remember you have to add the port the the url:

http://xxx.xxx.xx.xxx:8080/~user

[KrayZ]

Originally posted by intake:
But yes, Comcast blocks inbound Port 80 requests.

Not where I live.

[Krusty]

Originally posted by Gavin:
Here's a trick.
You can see your site from the outside by using a translator:

http://babelfish.altavista.digital.com/

just pick 'spanish to english' as the language to leave it in english.

Fantastic Gavin !! -- That's exactly what is needed to test beyond the loopback limits of a router.

[Gavin]

Glad to help