[flojin]

Hello,
I'm having a tough time with websharing.

I sell stock images. To deliver the files, I use websharing. If you bought an image from me, In OS9, I would simply put that image in �a folder with your name on it and drop it into my websharing folder. I would tell you to point your browser to: http://myipaddress/yourfoder
Then you would see the contents of that folder and click and drag the link to your desktop to download the file.

Now I can't do it. I have turned websharing on, I put the folders in the correct folder and when I view them locally, it works. I have noticed that my browser changes my IP address to 127.0.0.1/yourfolder

When I send other people http://myipaddress it works. But, when they try, http://myipaddress/theirfolder the get an error saying that their browser tried to connect to 127.0.0.1 and failed. It would appear that my machine is redicecting their requests to a local address and then they can't connect. I looked at my error logs and found this:

[alert] httpd: Could not determine the server's fully qualified domain name,
using 127.0.0.1 for ServerName
fopen: Permission denied

I don't understand how my ip address could not be fully qualified, since users can view the main directory, just not subdirectories.

Thanks for reading that epic description. I hope someone can help me, I'm a desperate newbie.

The permissions are all set for everyone to read

[Camelot]

My guess from your description is that you're running on a private-class network with some kind of NAT/Firewall/Airport setup between you and the internet.

In this setup, Apache cannot determine your web server address since the machine itself is something like 192.168.1.2 which doesn't resolve in DNS.

The solution is simple.

Edit the file /private/etc/httpd/httpd.conf

and look for the line that begins:

#ServerName

Just uncomment the line (remove the # sign) and change the server name listed to be your real-world server name (e.g. 'ServerName www.mydomain.com').

If you don't have a domain name for this server enter the real-world IP address of your server that remote users would connect to.

Then restart the web server and you should be all set.