Hi, ive looked around and dont seem to have found an answer to this, so heres the question, im sure its something simple, but its baffled me a little. Ok, so a fresh install of ISPConfig on Ubuntu Server. There are three domains on this host, two running HTTP and one on HTTPS. Problem ive got is now; is that ive switched to SSL with Authoritive Cert, only on one domain, and now stats do not load across all the domains, it shows a grey screen with the date at the top of the logs, though in a duller grey it shows a sad face and says " example.domain refused to connect, shows this as you hover over the middle part of the browser window. Tried switching from GoAccess to Awstats for a fresh stat output - Same problem. Stats do not load on HTTP & HTTPS now. Im guessing its something to do with trying to serve the stats over SSL, though HTTP is broken too now. Websites work perfectly on HTTP and HTTPS Any ideas?
It is best not to mix http and https in one server as default for any web server will only show the https in such case. Since LE is free and supported fully by ISPConfig the solution is to enable https for all web sites.
The two domains on HTTP have to stay HTTP, i wont go into detail why. I also do not want to setup an additional host either.
It is either or as there is no other known way to solve it, so it is up to you to choose whether this web server is all for http or all for https.
You need a separate IP address for the websites that shall be HTTP only. Otherwise Apache or Nginx will try to server https from default vhost for these domains. Regarding statistics, they get generated nightly. You have to wait up to 24 hours until they get generated. Also, when you switch to a different statistics program, you have to wait 24 hours until you can access them. Plus the website must get traffic to generate the stats.
I have an issue that my HTTP websites show the content of a random HTTPS website that is on the same server with the same IP. Do I understand it correctly that I need a secondary IP for the HTTP only websites? I don't want to enable HTTPS for those websites. Is there a workaround apart from this secondary IP?
Either use a separate IP or use a (eventually self signed) certificate (why the hell would you want a http only site in 2024...)
