Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
I’m not certain, but I think I’ve found the problem. I think that: A) There was a problem. B) Chrome cached the problem. C) After the fix, Chrome displayed the cached error page. So the original problem became a local problem. Clearing the cache seemed to fix the problem. Then it came back. I’ve cleared it a second time and seemingly fixed it again. Crazy. Hopefully it’s resolved. Edit: It came back. Even after deleting cache/browsing history, Chrome was autofilling my domain name. I went to myactivity.google.com and sure enough there’s all my browsing history. I had to manually delete each reference to my site. Knock on wood. It may be fixed.
Hi @jonsidener,
I can see both domains are working as expected now. Glad to see you managed to resolve the issue!
Anyway, what I would thought the problem would have been is your Apache configuration files and possibly missing the www versions of your websites inside. Is that correct?