Rumpus FTP and Wiki Server both running on port 80?

Question

Level 3

534 points

Rumpus FTP and Wiki Server both running on port 80?

At the moment I have the Rumpus FTP server setup on port 8000 and the mac os x built in wiki server on port 80

But some of our clients can't get on the web based ftp so I assume they block port 8000

How do I configure them both on port 80 ? easy guide please!

Macbook Pro 2.16 Ghz 2Gb RAM, Mac OS X (10.5)

Posted on Oct 8, 2009 5:31 AM

Reply

Answer 1

Kevin Neal Author

Level 3

534 points

Oct 8, 2009 5:45 AM in response to Kevin Neal

ok I've found this info, but don't know how to apply it to Mac OS X Server?

Next, you will need to configure Apache to run as a reverse proxy for the Rumpus domain name. The configuration depends on your version of Apache. For Apache 1.X, the configuration will look something like this:

LoadModule proxy_module libexec/httpd/libproxy.so
AddModule mod_proxy.c

<VirtualHost *:80>
ServerName files.acmewidgets.com
ProxyPass / http://files.acmewidgets.com:8000/
ProxyPassReverse / http://files.acmewidgets.com:8000/
</VirtualHost>
For Apache 2.X, the configuration is a bit different, as shown here:

LoadModule proxy_module libexec/apache2/mod_proxy.so

<VirtualHost *:80>
ServerName files.acmewidgets.com
ProxyRequests Off
<Proxy *>
Order deny,allow
Allow from all
</Proxy>
ProxyPass / http://files.acmewidgets.com:8000/
ProxyPassReverse / http://files.acmewidgets.com:8000/
</VirtualHost>

Reply

Answer 2

Camelot

Level 9

58,527 points

Oct 8, 2009 11:40 AM in response to Kevin Neal

ok I've found this info, but don't know how to apply it to Mac OS X Server?

You need to manually edit your Apache configuration files with the appropriate changes.

The big issue is whether you're running Apache 1.3 or 2 - there was a question when you first started the web server, but most people don't remember what they chose. That's important since it defines which configuration file you need to change.

If you're using Apache 2 then you need to look in /etc/apache2/sites/ for your config file (there may be several, one per virtual host you're running).

Reply

Answer 3

Kevin Neal Author

Level 3

534 points

Oct 8, 2009 3:45 PM in response to Camelot

thanks, yes its apach2, I found the file and replace the content with the info in my post, and it does work.

The site in Server Admin looses all its GUI details, is this normal/ok?

I assume I can't make any GUI changes else it will overwrite the changes I made directly to the config file?

Also the first time I did this, when I went to the wiki site it displayed but without any css styling and showed an error in server admin, so I undid everything and tried again, seems ok this time.

Reply

Answer 4

Kevin Neal Author

Level 3

534 points

Oct 16, 2009 3:35 PM in response to Kevin Neal

hmm directly editing the config files is causing real problems, if I ever need to change any site settings in Server Admin or restart the web service I get a "Uncaught exception raised in Web client-side plugin." error and the service doesn't restart anymore and I have to re-edit the config files

Reply