You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have just wiresharked on the remote docker environment (which exposed its docker socket at address-of-remote-docker-host:9007 with TLS enabled) and run the Steps to Reproduce again, then I got this:
Please be notice that:
It is a HTTP request to a TLS-enabled docker daemon socket, while a TLS handshake is expected in the packet capture.
/_ping in the URL of HTTP request is also occured in the Portainer log, indicates this request is send by Portainer.
It seems the problem is, Portainer is talking to a TLS-enabled docker daemon in plaintext HTTP, despite toggling on TLS switch in the new environment wizard.
Besides, I could confirm that there is no issue with certificates, since I tried connect to address-of-remote-docker-host:9007 on my computer with same certificates and keys:
Before you start please confirm the following.
Problem Description
Could not add docker standalone environment via API if TLS is enabled. Probably because incorrect handling of URL.
Expected Behavior
Environment added to Portainer, without any issue.
Actual Behavior
Portainer failed to establish connection to the environment. Emitting the log pasted in Portainer logs or screenshots.
Steps to Reproduce
Portainer logs or screenshots
Portainer version
2.20.1
Portainer Edition
Business Edition (BE/EE) with 5NF / 3NF license
Platform and Version
Docker 26.0.2
OS and Architecture
Arch Linux, AMD64
Browser
Firefox 125.0.2
What command did you use to deploy Portainer?
Additional Information
No response
The text was updated successfully, but these errors were encountered: