Posted by kunago on September 25, 2009 at 5:10pm
4 followers
| Project: | Hosting |
| Version: | 6.x-0.4-alpha1 |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
During the installation I am asked to set the default ports. However, this port (80 in my case) is not set neither for my Aegir site, nor for any imported site. The port is then 0 for those sites and there seems to be no option to change the number manually.
When the port number is 0 for a site, Aegir will then prevent one from making additional changes - for site aliases for instance.
Comments
#1
I can reproduce this. Thanks for the bug report!
#2
I've committed a stopgap to cvs that takes the first port from the list of allowed ports on the web server and assigns this port when importing a site. This will need to be improved in the future and will probably be rewritten when we have #570980: allow vhosts of the same name on a different port and #588424: Default port for web servers
But for now it's fixed. If you're not running against HEAD, attached is a patch. There's a hook_update that will go and set any existing sites to the 'default' port if they are port 0 in the db.
Note that apache vhost configs were still written with port 80 for these sites, the reason they are 0 in the database is because the value was simply not being passed, so null.
#3
I can confirm that HEAD now updates all sites to Port 80 that were previously Port 0.
Thanks Mig5!
Steve
#4
Automatically closed -- issue fixed for 2 weeks with no activity.