Details
-
Type:
Bug
-
Status: Done
-
Priority:
(None)
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 3.2.0, 3.2.0-report
-
Labels:
-
Sprint:MEN Sprint 152
-
Backlog:yes
-
Days in progress:4
Description
When mender client is configured to use a custom Server Certificate, the websocket connection cannot be established.
Most likely introduced at MEN-5216
time="2021-12-07T09:05:57Z" level=error msg="couldn't dial to remote backend url tls: first record does not look like a TLS handshake" time="2021-12-07T09:05:57Z" level=error msg="connection manager failed to connect to http://localhost:38355/api/devices/v1/deviceconnect/connect: websocket: bad handshake; reconnecting in 5s (try 2/0); len(token)=1024"
The bug does only affect master
Acceptance criteria:
- Bug is fixed
- Test for mender-connect when using custom certificate