Latest BOA stable / Debian 6 / Xen / 4GB RAM

Background is our client wanted to demo a site on Aegir and need to give their client an IP address for the demo rather than a hostname.
I setup the default vhost that by default redirects to Chive.
I added the IP to the "default" vhost file and pointed the server root at our platform directory.

I then had to edit /sites/sites.php to redirect requests from 1.2.3.4 > www.sitename.com
Woallah, all worked as it should and I could access sitename.com via the IP 1.2.3.4. Great!

I went to login and realised cookie settings were messed up as I would keep being redirected back to the login screen.
I fudged the local.settings.php file to include:
$cookie_domain = 'sitename.com';
hit save and reloaded the site, presto everything was working as expected.

My gripe was with the cookie handling, and I'm not sure if this is a bug or system fault.
Your feedback would be greatly appreciated.

Thanks in advance.

Comments

omega8cc’s picture

Status: Active » Closed (works as designed)

Using IP as a site name is not supported and even denied in BOA. We are using it for Chive only, and because of it people often have cookie related issues with it. Don't try that for Drupal sites and don't modify files owned and managed by Aegir. Domain names are cheap these days.

snlnz’s picture

Yes I understand what you are saying and it was a request from a client to avoid exposing a hostname/domain or using any domain on that note.

Primary goal was to disguise the servers hostname from an end client.
In any event, this workaround worked and we want it to be a known solution to a problem we faced.
However, logging in took the addition of the cookie_domain variable in local.settings.php