Connection could not be encrypted

weirdal · Post by **weirdal** » Fri Jan 28, 2022 10:44 am

Hello everyone

Our customer is using the httpServer-Manager.
Whenever Firefox is opened and the service is contacted for the first time, the following log message appears:

WCCOActrl (2), 2022.01.28 10:18:28.086, SYS, SEVERE, 141, Connection to client could not be encrypted:
WCCOActrl (2), 2022.01.28 10:18:28.088, SYS, SEVERE, 141, Connection to client could not be encrypted:

This message appears only for the first time when logging on until Firefox is closed and opened again.
Since there are 2 spaces between the words "client" and "could", I assume there is a missing name or IP address.

Has anyone ever experienced this issue and has an explanation and / or a solution?

€: it's CentOS 8 and WinCC OA 3.17 P012

kilianvp · Post by **kilianvp** » Sat Jan 29, 2022 3:00 pm

Firefox first tries to use http and then switches to https. Firefox remembers this until you close the browser. You can ignore the message.

weirdal · Post by **weirdal** » Mon Jan 31, 2022 9:50 am

Ok, thank you for the quick answer, Kilian.

That explains the log messages and the pattern in which they occur.
The bookmark I am using is stored as "https://..." tho, I would expect Firefox to explicitly not use HTTP in this case.
Is there a setting in Firefox to force it to only use HTTPS? I could not find one.

weirdal · Post by **weirdal** » Tue Feb 01, 2022 10:48 am

I found out that Firefox actually has a HTTPS only mode, but it is available only from version 83.x while CentOS 8 comes with Firefox v78.3.0 by default.
I am assuming, but have not tested, that this might get rid of the mentioned log message.

Bugs / Problems