I’m running Coronium on an Ubuntu server and it’s been going great. But today I’ve set up another virtual host on my server and I’m finding that when I try to access any subdirectory on the new host, I get asked to log in using my Coronium admin login. I went hunting for .htaccess files, but found the Coronium auth info in the conf folder of the ubuntu user. I can’t see how these details are controlling directories outside the Coronium world, but they are.
Any ideas on how I can fix this?
Further playing around shows that the folders I get asked to authenticate are the ones that have the same name as folders in coronium. For example, my other virtual host has a “settings” folder, as does coronium. So my problem might be beyond the scope of this forum 
Hi,
That seems kind of strange that there would be overlap of folder names, unless the host is doing something unusual.
Just to double check, you are using Ubuntu 14.04 LTS?
Yeh, using 14.04LTS. The second site is an ownCloud installation. I’ve managed a workaround; enforce https with the owncloud installation which has fixed the problem. Probably a good solution anyway!
After re-reading your post, it sounds like you are installing Coronium along with other sites/services? If that is the case, then you are bound to run into issues. Coronium is meant to be its own stack.
But, if you got it working for your needs, then congrats! 
Cheers
Further playing around shows that the folders I get asked to authenticate are the ones that have the same name as folders in coronium. For example, my other virtual host has a “settings” folder, as does coronium. So my problem might be beyond the scope of this forum
Hi,
That seems kind of strange that there would be overlap of folder names, unless the host is doing something unusual.
Just to double check, you are using Ubuntu 14.04 LTS?
Yeh, using 14.04LTS. The second site is an ownCloud installation. I’ve managed a workaround; enforce https with the owncloud installation which has fixed the problem. Probably a good solution anyway!
After re-reading your post, it sounds like you are installing Coronium along with other sites/services? If that is the case, then you are bound to run into issues. Coronium is meant to be its own stack.
But, if you got it working for your needs, then congrats!
Cheers