After updating to BOA-2.1.0 can not access barracuda or octopus aegir admin page

Events happening in the community are now at Drupal community events on www.drupal.org.
ddols's picture

Hi,

After updating to BOA 2.1.0 today I can no longer access the main barracuda aegir admin site or my octopus aegir page. Instead it redirects to the first (alphabetically, not in order of creation) drupal web site. At first when I tried to access either they redirected to aegir.mydomain.net/install.php or o1.comp.mydomain.net/install.php and I got a 403 forbidden error. I then tried rebooting and after that it started redirecting to the first website. All other sites are working fine.

Site is in on a Linode server running Debian squeeze. I changed nothing in the .barracuda.cnf file.

I wonder if there was a process going on in the background after the update said it was finished and I didn't wait for it to finish before trying the reboot? Now I broke it because of that? Any ideas what's going on? I am stumped.

Comments

Make sure if your vhosts in

omega8cc's picture

Make sure if your vhosts in /data/disk/USER/config/server_master/nginx/vhost.d/ use wildcard or IP in the "listen" directive. If they use IP address, then replace wildcard *:80 with your server IP (shown as 123.45.67.89 below)

  listen *:80;

with:

  listen 123.45.67.89:80;

in two Nginx config files:

/var/aegir/config/server_master/nginx/vhost.d/your.master.instance.url
/var/aegir/config/server_master/nginx.conf

Now reload Nginx with:

  service nginx reload

This should help. But it looks like a bug in the Aegir version we use, which affects only some older systems with IP instead of wildcard in the listen directive. If you can, please open an issue at:

https://drupal.org/node/add/project-issue/barracuda

You may need to do the same

omega8cc's picture

You may need to do the same also in your Octopus instance /data/disk/USER/config/server_master/nginx/vhost.d/your.octopus.instance.url config file.

Update

omega8cc's picture

BOA 2.1.0 is now safe to use when Nginx listens on IP (old default) and not a wildcard. Small revert helped: bit.ly/184uW3I

It worked! Thank you!

ddols's picture

I just finally had a moment to try your fix and it worked. My /data/disk/USER/config/server_master/nginx/vhost.d/ files did use wildcards, as did the files you said to change. I still changed the wildcard to the IP address and all worked well after.

Thanks much.

BOA

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds:

Hot content this week