x509: certificate signed by unknown authority #9931
Replies: 8 comments 2 replies
-
Please complete the rest of the fields in the bug template - this helps us to get a better picture of the issue you're experiencing so we can attempt to help. |
Beta Was this translation helpful? Give feedback.
-
Hello, everything is updated accordingly. |
Beta Was this translation helpful? Give feedback.
-
Hello, |
Beta Was this translation helpful? Give feedback.
-
I have exactly the same problem when I try to add my personal registry. I started the docker with: Version: Portainer Business Edition 2.18.3 |
Beta Was this translation helpful? Give feedback.
-
I have the same problem on Portaine Community Edition 2.18.3. |
Beta Was this translation helpful? Give feedback.
-
It is a really stupid situation. Just CA verification is missing but no way to configure it inside the container. I can understand that for community...it is a bug and we need to wait...but @pasger is paying enterprise so...I don't see any benefit of paying for it. |
Beta Was this translation helpful? Give feedback.
-
At present our app templates functionality doesn't support self-signed certs or custom CAs. I've flagged this with the team to be looked at in a future release. |
Beta Was this translation helpful? Give feedback.
-
Adding a workaround here for anyone that stumbles on this thread—I was trying to get the edge agent to trust my private PKI and I was getting this same error. The I personally used a Docker Swarm secret to accomplish this but you could also just use a volume to mount your own file in place of the container's version of the file. Hope this helps. |
Beta Was this translation helpful? Give feedback.
-
Bug description
When I configure a template repositoty using my enterprise github repository I get an error saying: x509: certificate signed by unknown authority
Expected behavior
I should be able to see my catalogue.
Portainer Logs
Provide the logs of your Portainer container or Service.
You can see how here
Steps to reproduce the issue:
Technical details:
docker run -p 9443:9443 portainer/portainer
):docker run -p 9443:9443 portainer/portainer-ce:latest
Additional context
Add any other context about the problem here.
Beta Was this translation helpful? Give feedback.
All reactions