mafia bot issue
Posted: Fri Jan 10, 2025 3:45 pm
Hello everyone.
Chaqa contacted me about the bot not being available. Checked it but it was up. In the log I saw some entries I had not seen before:
=INFO REPORT==== 10-Jan-2025::16:25:05 ===
TLS server: In state certify received CLIENT ALERT: Fatal - Certificate Unknown
I tried it on different browsers. Chrome on android, Safari/Firefox/Chrome on MacOS and I discovered that I most often was not able to connect to [http://]mafia.peterlund.se. But on all browsers I was able to connect when adding an "s". Using https:://mafia.peterlund.se works after you go "advanced" and accept the so called "security risk" by accepting my self signed certificate.
So why "http://" suddenly has stopped working, I do not know. My theory is that the new versions of the web browsers have stopped accepting non-encrypted connections ("http" without the "s"). First time I saw this problem I think was in the middle of December 2024 when I tried to access it from my Chrome/android.
Please let me know if anyone has some more input on this. "http" has been working without problems since the bot was created 2017 and I have not modified it lately in any way either, so it needs to be something else.
regards,
Peter Lund
Chaqa contacted me about the bot not being available. Checked it but it was up. In the log I saw some entries I had not seen before:
=INFO REPORT==== 10-Jan-2025::16:25:05 ===
TLS server: In state certify received CLIENT ALERT: Fatal - Certificate Unknown
I tried it on different browsers. Chrome on android, Safari/Firefox/Chrome on MacOS and I discovered that I most often was not able to connect to [http://]mafia.peterlund.se. But on all browsers I was able to connect when adding an "s". Using https:://mafia.peterlund.se works after you go "advanced" and accept the so called "security risk" by accepting my self signed certificate.
So why "http://" suddenly has stopped working, I do not know. My theory is that the new versions of the web browsers have stopped accepting non-encrypted connections ("http" without the "s"). First time I saw this problem I think was in the middle of December 2024 when I tried to access it from my Chrome/android.
Please let me know if anyone has some more input on this. "http" has been working without problems since the bot was created 2017 and I have not modified it lately in any way either, so it needs to be something else.
regards,
Peter Lund