Also, after doing that, I had to open dev tools and delete the main node for the modal that was covering the page. After that I could take the test.
> it tries to connect to api.musiclab.org through CORS. This fails due to the same certificate issue
Thanks for the hint! It works now that I visited the api subdomain separately, accepted the warning, and go back to the test. The test sound now plays (though you might need to give it a second).
Re:Tone-Deafness Test
by leobakerhytch on Thursday October 22, 2020 @06:36AM
(#24856606)
I couldn’t get this to work, but setting back my clock to October 20th did the trick (along with deleting the modal’s element via dev tools as jonahx mentions).
Re:Tone-Deafness Test
by jiveturkey on Wednesday October 21, 2020 @08:28PM
(#24853790)
> Bad luck I guess that it expires right when it gets viral on hn.
This right here is the problem with privacy and security. low expectations.
It isn't bad luck, it's below baseline level secops/SRE. I mean, sure, it's probably a low effort, low investment toy site, but this is very baseline stuff. If you aren't going to manage a cert properly, just don't use TLS at all!
Re:Tone-Deafness Test
by chrisfosterelli on Wednesday October 21, 2020 @09:32PM
(#24854088)
It's an engineering mistake that it expired, but bad luck that it expired today.
(That said, everyone makes mistakes now and again)
Even if you click on the "I know the risk, I accept" button, it tries to connect to api.musiclab.org through CORS. This fails due to the same certificate issue and gives the error you report. Bad luck I guess that it expires right when it gets viral on hn.
[0]: https://crt.sh/?id=2886689176
[1]: https://crt.sh/?id=882377045