Please login or register to participate.
migrationuser Oct 14, 2009 03:26 PM

I just downloaded and started to test the community edition and I think is a great tool and I would like to use it to collaborate with he rest of my colleagues.

Currently I'm running with one problem. The default listening port for the web interface is port 80, for HTML, unfortunately I already have an application running on that port so I need to change this port for

I tried to check the network settings in admin area but couldn't find any place where I could change this setting.

Do you know how can I change the default listening port so instead of accessing to the log on screen using I can use (or something else)

Any other suggestion that I could use will be great appreciated.


Replies (7)
migrationuser Oct 14, 2009 03:27 PM
Hi franciscovj,

Good to see you try out

Hmm... regarding your problem of running only on port 80 - though it *can* be done, I'd recommend instead that you simply map a different domain name to it. If you already know how to point to it, then you can easily point a different domain name to it and will directly work on that one - or both will work. The appliance will actually run off any hostname that is pointed to it without any worries - this is by design, and is meant for rapid / easy deployment.

Alternatively, if you really need to do this - run off a port other than 80: You need to know these things:

1. is actually running on port 8080 inside the appliance (on the zope server)
2. An apache httpd server is proxying requests from any hostname at port 80 to the port 8080 zope server and back and rewriting all URLs while it's doing this.

To change the port from 80 to another there are 2 approaches:
1. You can go and edit the apache configuration inside the appliance to make it work on a different port. You'll need to be familiar with the linux command line and the vim editor to be able to accomplish this.
2. You can commission a new VirtualHost on any existing apache httpd server you might already be using *external* to the appliance and do this as well.

I'd still recommend simply adding a new host on your DNS domain and letting people use that, and even putting up the link to it on your main site, for easier adoption. In my experience most people find it difficult to remember port numbers. :)

Do tell us how it went. If you want more detail on any of the alternate port changing procedures, post a follow up here and I'll detail it as much as I can.

Dhiraj Gupta.
migrationuser Oct 14, 2009 03:27 PM
Hi Dhiraj,

Many thanks for your prompt response and so detailed too!!. I never though of creating a different alias, that is a great idea.

I appreciate your help!!

Francisco Vidal
migrationuser Oct 14, 2009 03:27 PM

Could you please allaborate on the 2 methods to change the port on the server.

I do need to change the port.

Can you tell me how to change the port in apache, and/or the VirtualHost trick?

Thank you very much in advance.

migrationuser Oct 14, 2009 03:27 PM
Hi Ricardo,

Are you running the community edition appliance or the buildout from source? The instructions for both would be different so you need to tell us that.

Also, what's the particular need to change the port? If you tell us a bit more about your scenario (what you're running, where and what the problem is) I might be able to tell you some better solution.

Dhiraj Gupta.
rasco Jan 30, 2013 09:34 PM
what is the path in linux in order to change the port #
rasco Jan 30, 2013 09:34 PM
what is the path in linux in order to change the port #
fernkb2 Feb 27, 2013 02:41 AM
a better solution to this is adding the http parameter to user.cfg then rebuild. the steps are somewhere within the forum.