Docker Connection Error Desc Transport X509 Certificate
When you get docker connection error desc x509 certificate signed authority issue while you’re configuring docker swarm worker node. This is because there was a server time mismatch. When you face issues related to docker x509 certificate signed by unknown authority.
Another reason can be then we don’t have a trusted certificate which was generated by DTR at the time of installation the docker.
Once you created a self-signed certificate on the machine. This issue would be fixed. you may follow these links to create the certificates.
“Error response from daemon: rpc error: code = 13 desc = connection error: desc = “transport: x509: certificate has expired or is not yet valid“
You can also regenerate certificate on docker-machine using docker-machine regenerate-certs machine-name and where machine-name is the name of the machine with bad certs.
We can also check the certificate location at /etc/docker/certs.d
In my case, there was the timezone difference on both the servers. So, I just change the timezone on both servers using the below commands.
rm -rf /etc/localtime ln -s /usr/share/zoneinfo/Asia/Kolkata /etc/localtime date
So I configured the same timezone on another server then try to join the worker node. it’s worked.
date +%T -s ’07:04:22′
Docker swarm has joined the worker node using the token.
You can try all the solutions if it doesn’t work for you, you can drop us the comment. we will try to solve your issues asap. Most probably you won’t face this issue again.
You’re done docker error desc x509 certificate signed authority issue