Need help?

Our experts have had an average response time of 11.7 minutes in August 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

Docker Error x509 – How to fix

by | Jul 1, 2021

Wondering how to fix Docker Error x509? We can help you.

Often our customers using Docker report to us that they get this error while trying to log into their docker registry.

Here at Bobcares, we often handle requests from our customers to fix similar errors as a part of our Server Management Services.

Today we will see how our Support Engineers fix this for our customers.

How to fix Docker Error x509

Before going into the steps for fixing this error we will see what causes this error.

When we try to login into the Docker registry in the following way:

docker login -u admin -p Passw0rd

We may at times end up with the following error:

Get x509: certificate signed by unknown authority

This happens when we are using a self-signed certificate for the docker registry instead of the certificate issued by the trusted certificate authority (CA).

Furthermore, the docker daemon does not trust the self-signed certificate which causes the x509 error.

Steps to fix this error:

We can make the docker trust the self-signed certificate by copying the self-signed certificate to /etc/docker/certs.d/<your_registry_host_name>:<your_registry_host_port>/ca.crt on the machine where we run the docker login command.

We can do this with the following steps:

1. First, we must create the following directory on the server using the following command:

mkdir -p /etc/docker/certs.d/<your_registry_host_name>:<your_registry_host_port>

2. Then copy the docker registry certificate file from our docker registry host to the cluster where we are running docker login.

3. After that we can rename the docker registry certificate file to the following:


This can be done with the following command:

scp <your_registry_host_name>:/opt/registry/certs/domain.crt /etc/docker/certs.d/<your_registry_host_name>:<your_registry_host_port>/ca.crt

For example:

mkdir -p /etc/docker/certs.d/
scp /etc/docker/certs.d/

Finally, we can try to log in to the docker registry again.

[Need assistance? We can help you]


To conclude, we saw the steps that our Support Techs follow to fix Docker Error x509 for our customers.


Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.


var google_conversion_label = "owonCMyG5nEQ0aD71QM";


Submit a Comment

Your email address will not be published. Required fields are marked *



Privacy Preference Center


Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]


Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid


Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie


These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.