-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
stats unavailable via https #133
Comments
After Let's Encrypt cert implementation #145 : None of the common names in the certificate match the name that was entered (stats.openstreetmap.org). You may receive an error when accessing this site in a web browser. Common name: acme.openstreetmap.org |
Sorry, where did we say he had implemented letsencrypt for that domain? We didn't. There was a tweet saying we had started rolling it out but there's still a long way to go to get everything switched over, and priority was for services already secured by a certificate that expires in a few weeks. |
I think, commit openstreetmap/chef@2e3b896 has been set default certificate on port 443 to acme.openstreetmap.org. Before there was default page for Chef control panel serverd from another virtual host :) |
The point is that we have never claimed to support https for that domain so anybody choosing to randomly change protocol from http to https gets to pick up the pieces themselves. Yes, changes to other domains hosted on the same machine may result in a change in behaviour, because there is no defined or expected behaviour for https://stats.openstreetmap.org/ because that is not a URL we have ever published or invited anybody to use! |
Fixed in openstreetmap/chef@fa6ed4f. |
Opens fine:
http://stats.openstreetmap.org/cgi-bin/awstats.pl?config=www.openstreetmap.org
Opens into Chef control panel:
https://stats.openstreetmap.org/cgi-bin/awstats.pl?config=www.openstreetmap.org
The text was updated successfully, but these errors were encountered: