Description of problem: After the update of Firefox, at the 1st launch, it trys to connect to start.mageia.org. Unfortunately, as I have configured Firefox with HTTPS only, it cannot find the https of start.mageia.org Message displayed (in French) "Avertissement du mode « HTTPS uniquement » Site sécurisé non disponible Vous avez activé le mode « HTTPS uniquement » pour une sécurité renforcée, mais il n’existe aucune version HTTPS du site start.mageia.org." Version-Release number of selected component (if applicable): How reproducible: Every update of Firefox since I have set https only. Steps to Reproduce: 1.Update FF 2.Start or restart it 3.
Reposting from the forum thread: That is because the SSL certificate is expired since 2021, and because it points to http://start.mageia.org/ Also the welcome page is contained in the package indextml and points to file:///usr/share/indexhtml/index.html (which forwards to http://start.mageia.org/) Cf. https://gitweb.mageia.org/software/indexhtml/tree/HTML/index.html Maybe someone should take a look at the webserver for start.mageia.org / neru.mageia.org - certificate was only valid until 01.12.21 ...
CC: (none) => doktor5000
(In reply to Florian Hubold from comment #1) > Reposting from the forum thread: > > That is because the SSL certificate is expired since 2021, and because it > points to http://start.mageia.org/ > > Also the welcome page is contained in the package indextml and points to > file:///usr/share/indexhtml/index.html (which forwards to > http://start.mageia.org/) > Cf. https://gitweb.mageia.org/software/indexhtml/tree/HTML/index.html > > > Maybe someone should take a look at the webserver for start.mageia.org / > neru.mageia.org - certificate was only valid until 01.12.21 ... I think is under maintenance, currently the page show It works!
CC: (none) => sysadmin-bugs
Dear sysadmins, what happen with this?
start.mageia.org uses a self-signed certificate, which is also expired. There's no reason we couldn't use our wildcard certificate for this site. I'll look into doing that.
CC: (none) => dan
Assignee: atelier-bugs => dan
commit 85dd260a85daddbf223290a4570abf93e36478f1 Author: Dan Fandrich <danf@...> Date: Fri Mar 1 16:19:29 2024 -0800 Enable https on start.mageia.org (mga#32903) --- Commit Link: https://gitweb.mageia.org/infrastructure/puppet/commit/?id=85dd260a85daddbf223290a4570abf93e36478f1
https://start.mageia.org/ now works. I've also updated the indexhtml links to use https: but that will take a new release to take effect.
Assignee: dan => atelier-bugs
commit db905c74b31c76477b097b1a6185206526228ee5 Author: Dan Fandrich <danf@...> Date: Fri Mar 1 17:03:55 2024 -0800 Enable https: versions of all http: redirects (mga#32903) Also, reinstate the http://start.mageia.org/ redirect that was accidentally deleted in the previous commit. --- Commit Link: https://gitweb.mageia.org/infrastructure/puppet/commit/?id=db905c74b31c76477b097b1a6185206526228ee5
Still just show: It works!
commit 05545dde3f9b7fada9e606f8875b890d4656212c Author: Dan Fandrich <danf@...> Date: Fri Mar 1 18:12:26 2024 -0800 Fix vhost names for the new https: redirects (mga#32903) The puppet object names are used otherwise which isn't correct. --- Commit Link: https://gitweb.mageia.org/infrastructure/puppet/commit/?id=05545dde3f9b7fada9e606f8875b890d4656212c
Yes, I messed up a subsquent commit but it should all be working now.
(In reply to Dan Fandrich from comment #10) > Yes, I messed up a subsquent commit but it should all be working now. Not sure if must work like this, but I was expecting that loads the French version due the parameter l=fr in the URL field of the bug, instead I get the detected language, in my case Spanish (I get https://www.mageia.org/es/community/ instead https://www.mageia.org/fr/community/)
The redirect always drops the parameters, via http: or https: I assume the parameters are there only for gathering statistics on start.mageia.org and people always end up on the same destination page.
(In reply to Dan Fandrich from comment #12) > The redirect always drops the parameters, via http: or https: I assume the > parameters are there only for gathering statistics on start.mageia.org and > people always end up on the same destination page. Then this bug could be closed
Resolution: (none) => FIXEDStatus: NEW => RESOLVED