The weirdest of things are happening on new 7.29 platforms, and not only there.
I've had similar issues in my localhost reported here:
https://www.drupal.org/node/2307967
I think security update is defective, there are several reports in the issue queue.
I have a critical domain pointed to an IP address in my BOA server.
I know that this IP works as I can ssh into it, run BOA scripts, etc.
This domain name and wildcard have been pointed at it for some time, more than enough for propagation.
When adding site to 729 vanilla standard platform, with the same client I use in working sites I get error, if logging via BOA email I get error in spite that site shows in Aegir, I cannot even log into it from anonymous user, I get this:
http://imgur.com/YfT8PzX
that page redirects on click to my registrar, where the A records are set correctly.
Steps I took:
I recently rebooted VM to check if there was a kernel update I was missing, still in the latest Debian stable (wheezy).
deleted site, recreated, same old.
migrated to d728, no luck.
ran barracuda up-stable from IP that hosts site, completed successfully.
ran daily.sh to fix perms, still same image I have never seen before.
cleared browser cache
used different browser
Strange thing is that another site (brokertricounty.com) failed with different error message, which you can see by typing that URL.
Even stranger, there is a site that loaded successfully (firstamericantours).
See image of 3 sites in octopus:
http://imgur.com/lO2grct
I am totally dumbfounded by this unheard of behavior.
New Relic reports everything working OK on server.
BTW, I am continuing work on this issue so first site might not be visible.
Can anybody help?
Comments
DNS
All of this looks like DNS problems to me, nothing related to a Drupal platform. If you check your domains on www.intodns.com you see there are some weird things.
Also, you seem to be using a different IP for each domain. Are those IPs actually assigned to the same server? And if so, did you set up the vhosts on your server for such a configuration?
Thanks for answer ar-jan, I
Thanks for answer ar-jan, I had already scheduled a screen sharing session with my server admin, I have a VM running there, for tomorrow.
Now that you mention it, will check with registrar too.
But to answer your questions, this issue is baffling to me because I had already checked that all four dedicated IPs in my VM worked, I set them up via webmin, actually three of them are a mask for the main one.
The IP that I was testing used to work because I dumped an e-commerce site on a previous Commerce Kickstart platform and it just worked.
As previously mentioned, I used the same setup that works for other sites, and there has been more than enough time for propagation.
Now here is the burning question: what do you mean by setting up vhosts?
I don't know how to do that in BOA server, never heard of that, nor ran across any documentation.
Please explain how to do that.
Multiple IPs
Actually I'm not sure what the correct setup is for multiple IP addresses on BOA. By default it listens to *:80 I think, so maybe that should be enough. But see https://github.com/omega8cc/boa/blob/master/docs/SSL.txt for how to configure particular IP addresses per hostname (which would be necessary for SSL).
Thanks for continuing
Thanks for continuing support.
I really appreciate it as critical projects depend on correct resolution of this issue.
I checked if domain was correctly bound to IP and it was not, in spite that I did set correct IP at registrar, so it is a DNS issue right there.
As usual, you troubleshoot first the main bug, the rest might depend on it.
So let me sort that out first, I still did not install an SSL cert on BOA, but I will need to for e-commerce sites.
The doc you linked seems complete but is not user-friendly, so when the time comes I will have to test and figure out, will post findings here.
ar-jan totally right on DNS
The problem was in fact DNS...in my AT&T router, see here:
http://imgur.com/R54tU5W
damn router's DNS service was binding to an IP I never had and which was of course wrong.
There is a typo in between, but when using Google's DNS I got the correct IP and the site.
Really crazy.
So registrar is not to blame, neither webhost or BOA, but damn AT&T.
There is no problem using multiple IPs in a BOA server, it is a very simple setup which I did with webmin, will post a tut on that shortly, with snapshots et al.
Thanks for pointing in the right direction, I will sue AT&T for two sleepless nights, SUXXXX.
Still have a question for ar-jan: where did you get that there are vhosts in BOA?
I never found a setting for that and always thought that vhosts were configured automatically in nginx.
Please correct if I am wrong.
Well I'd checked the SSL docs
Well I'd checked the SSL docs and noticed the basic organization of the virtual host configurations.
They are configured seemingly automatically because BOA has a template for a wildcard vhost. Since I haven't used multiple IPs I wasn't sure if that works out of the box so I mentioned it, but it makes sense that it does. Unless of course you need SSL certificates.
Let's call this issue closed
I will write a tut about multiple IPs in BOA, it is very simple with webmin, it will include webmin installation in BOA and configuration of firewall.
Regarding SSL I will check with you when the time comes.
Thanks for the help, you saved my ...