Server is Xen / 4GB RAM / Debian Squeeze / Latest 2.0.9 BOA / No errors in the last upgrade and all other functionality (to my knowledge) works as expected.

We generally set up a site with it's primary domain then put the site into maintenance mode whilst in development.
During that stage, we use a custom site alias (generated by the feature) to access the site until development is finished and DNS records are switched.

Up until recently I've noticed sometimes I will be working on development aliased sites and they keep redirecting back to the main original domain, only for /admin pages, but the rest of the site is accessible via the alias domain name.

I believe this problem has existed since the last major version upgrade.
If it is of any help, we use a custom $cookie_domain directive in the local.settings.php file for these custom site aliases or without it we aren't able to log in to the site via that alias. Once the site goes live and we remove the directive all operates fine so this isn't major.

Not sure the logs are going to indicate anything worth while but thought I'd see if anyone else is seeing this behaviour.

Thanks

Comments

omega8cc’s picture

omega8cc commented
Status: Active » Fixed

Try to update the global.inc to HEAD with:

cd
wget -U iCab http://files.aegir.cc/update/global-fix.sh.txt
bash global-fix.sh.txt
rm global-fix.sh.txt

Then create an empty control file: sites/foo.com/modules/disable_admin_dos_protection.info

Done.

snlnz’s picture

snlnz commented

Nice! :)
Thanks for the super quick response and fix.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

snlnz’s picture

snlnz commented
Status: Closed (fixed) » Needs work

I'm noticing similar behaviour on Ubuntu Precise local instance, latest BOA 2.0.9, 1GB RAM, Oracle Virtual Box
Site is Drupal 6.28
PHP 5.2.17

Can access other admin pages but not node/add pages.
Other than attempting the patch in global.inc and touching the control file in sitename.com/modules/ I also tried putting a cookie_domain variable in local.settings.php and this usually resolves the problem but makes no difference on the local boa instance and any attempt to access /node/add/page would result in redirect back to home.

While it's just for testing on local BOA we managed to resolve this in a production environment recently.
Any ideas why this won't work on the local BOA instance but is fine on production BOA machines of the same versions?

Thanks in advance!

omega8cc’s picture

omega8cc commented
Status: Needs work » Closed (fixed)

Unrelated issue, discussed elsewhere #1962458: 403 for anonymous users on node/add