# X509: certificate signed by unknown authority for https://tardigrade.io/trusted-satellites **URL:** \ **Category:** troubleshooting\ **Created:** [December 5, 2020, 3:36pm UTC](https://forum.storj.io/t/x509-certificate-signed-by-unknown-authority-for-https-tardigrade-io-trusted-satellites/10569 "2020-12-05T15:36:13Z")\ **Posts on this page:** 20\ **Page:** 5
**Author:** ![baker](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/baker/32/6110_2.png) [@baker](https://forum.storj.io/u/baker)\ **Post date:** [December 17, 2020, 3:49pm UTC](https://forum.storj.io/t/x509-certificate-signed-by-unknown-authority-for-https-tardigrade-io-trusted-satellites/10569/81 "2020-12-17T15:49:33Z")
I also get that same error in my nodes on start up, but it doesn’t prevent them from running. Have you tried copying the `trust-cache.json` file from one of your running nodes to the directory where you are trying to create a new node? Is that the cache you are referring to? ---
**Author:** ![Arkina](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/arkina/32/6137_2.png) [@Arkina](https://forum.storj.io/u/Arkina)\ **Post date:** [December 17, 2020, 3:51pm UTC](https://forum.storj.io/t/x509-certificate-signed-by-unknown-authority-for-https-tardigrade-io-trusted-satellites/10569/82 "2020-12-17T15:51:50Z")
Hmm good idea, maybe it is that file, as far as i understand its just a list of trusted satellites. If they are in there that could be a workaround! ---
**Author:** ![baker](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/baker/32/6110_2.png) [@baker](https://forum.storj.io/u/baker)\ **Post date:** [December 17, 2020, 3:57pm UTC](https://forum.storj.io/t/x509-certificate-signed-by-unknown-authority-for-https-tardigrade-io-trusted-satellites/10569/83 "2020-12-17T15:57:05Z")
Yes, it’s just a plain text file. > **trust-cache.json** > > ```json > { > "entries": { > "https://tardigrade.io/trusted-satellites": [ > { > "SatelliteURL": { > "id": "12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S", > "host": "us-central-1.tardigrade.io", > "port": 7777 > }, > "authoritative": true > }, > { > "SatelliteURL": { > "id": "12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs", > "host": "europe-west-1.tardigrade.io", > "port": 7777 > }, > "authoritative": true > }, > { > "SatelliteURL": { > "id": "121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6", > "host": "asia-east-1.tardigrade.io", > "port": 7777 > }, > "authoritative": true > }, > { > "SatelliteURL": { > "id": "1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE", > "host": "saltlake.tardigrade.io", > "port": 7777 > }, > "authoritative": true > }, > { > "SatelliteURL": { > "id": "12rfG3sh9NCWiX3ivPjq2HtdLmbqCrvHVEzJubnzFzosMuawymB", > "host": "europe-north-1.tardigrade.io", > "port": 7777 > }, > "authoritative": true > } > ] > } > } > > ``` ---
**Author:** ![crossplatformdev](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/crossplatformdev/32/6083_2.png) [@crossplatformdev](https://forum.storj.io/u/crossplatformdev)\ **Post date:** [December 20, 2020, 3:03pm UTC](https://forum.storj.io/t/x509-certificate-signed-by-unknown-authority-for-https-tardigrade-io-trusted-satellites/10569/84 "2020-12-20T15:03:08Z")
Nope, -p 192.168.x.x:14002:14002 -p 28967:28967 -e ADDRESS=“[ddnsdomain.net:28967](http://ddnsdomain.net:28967)” as I enter the console from inside the same LAN. The place where the domain is at is only at address, and that is OK. ---
**Author:** ![crossplatformdev](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/crossplatformdev/32/6083_2.png) [@crossplatformdev](https://forum.storj.io/u/crossplatformdev)\ **Post date:** [December 20, 2020, 3:05pm UTC](https://forum.storj.io/t/x509-certificate-signed-by-unknown-authority-for-https-tardigrade-io-trusted-satellites/10569/85 "2020-12-20T15:05:15Z")
It took around 4 hours. Yes it was signed correctly. I repeated the process listed above three times. Seems a problem with letsencrypt certificate. I believe CA-Authorities on the container does not have LetsEncrypt root cert. 2020-12-17T04:18:20.714Z ERROR trust Failed to fetch URLs from source {“source”: “[https://tardigrade.io/trusted-satellites”](https://tardigrade.io/trusted-satellites%E2%80%9D), “error”: “HTTP source: Get “[https://tardigrade.io/trusted-satellites”:](https://tardigrade.io/trusted-satellites%E2%80%9D:) x509: certificate signed by unknown authority”, “errorVerbose”: “HTTP source: Get “[https://tardigrade.io/trusted-satellites”:](https://tardigrade.io/trusted-satellites%E2%80%9D:) x509: certificate signed by unknown authority\n[[tstorj.io/storj/storagenode/trust.](http://tstorj.io/storj/storagenode/trust.(\*HTTPSource)](http://tstorj.io/storj/storagenode/trust.%5D(http://tstorj.io/storj/storagenode/trust.(*HTTPSource)) ---
**Author:** ![crossplatformdev](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/crossplatformdev/32/6083_2.png) [@crossplatformdev](https://forum.storj.io/u/crossplatformdev)\ **Post date:** [December 20, 2020, 3:07pm UTC](https://forum.storj.io/t/x509-certificate-signed-by-unknown-authority-for-https-tardigrade-io-trusted-satellites/10569/86 "2020-12-20T15:07:42Z")
Thank you stefan. At the moment I am running the node as listed in this other post thread: > [@How to set up a non-Docker node using systemd services with the official native storagenode binary](https://forum.storj.io/t/how-to-set-up-a-non-docker-node-using-systemd-services-with-the-official-native-storagenode-binary/10107): > > Following the [Tech Preview] post below, here’s my method for standing up the Linux-native storagenode and storagenode-updater services on Ubuntu 20.04. Prerequisites Create and authorize a Storj identity as per [Storj Documentation](https://documentation.storj.io/dependencies/identity). Install Ubuntu 20.04 server. Set up a static IP and configure port forwarding Set up an appropriate storage medium and mount to /mnt/storagenode. Create a storj-storagenode system user: adduser --system --group --home /mnt/storagenode --no-create-home storj-stora… Works like a charm, no need for docker, no need for root privileges, integrated in os as standalone, just perfect. What are you waiting for to develop a .deb package? I could do it by myself and share it =) ---
**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\ **Post date:** [December 20, 2020, 3:11pm UTC](https://forum.storj.io/t/x509-certificate-signed-by-unknown-authority-for-https-tardigrade-io-trusted-satellites/10569/87 "2020-12-20T15:11:51Z")
> [@crossplatformdev](#): > > Seems a problem with letsencrypt certificate. I believe CA-Authorities on the container does not have LetsEncrypt root cert. The problem with aarch64 image. Please, use the arm32v6 instead ---
**Author:** ![crossplatformdev](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/crossplatformdev/32/6083_2.png) [@crossplatformdev](https://forum.storj.io/u/crossplatformdev)\ **Post date:** [December 20, 2020, 3:18pm UTC](https://forum.storj.io/t/x509-certificate-signed-by-unknown-authority-for-https-tardigrade-io-trusted-satellites/10569/88 "2020-12-20T15:18:56Z")
Yeah this bug does not affect arm32 image. But as I stated, I am using native binaries mounted as services at OS level. I really prefer this way: - Less overhead - Lack of docker knowledge - I can pack the whole node up inside a drive, in case of OS reinstall, as it where some days ago… - Friendly use for debianists and ubuntu users. Just telling some. ---
**Author:** ![Odmin](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/odmin/32/92_2.png) [@Odmin](https://forum.storj.io/u/Odmin)\ **Post date:** [December 23, 2020, 7:49am UTC](https://forum.storj.io/t/x509-certificate-signed-by-unknown-authority-for-https-tardigrade-io-trusted-satellites/10569/89 "2020-12-23T07:49:35Z")
The same [issue here](https://forum.storj.io/t/my-node-does-not-start-properly/10842/9). ---
**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\ **Post date:** [December 23, 2020, 9:07am UTC](https://forum.storj.io/t/x509-certificate-signed-by-unknown-authority-for-https-tardigrade-io-trusted-satellites/10569/90 "2020-12-23T09:07:08Z")
The same workaround here: > [@X509: certificate signed by unknown authority for https://tardigrade.io/trusted-satellites](https://forum.storj.io/t/x509-certificate-signed-by-unknown-authority-for-https-tardigrade-io-trusted-satellites/10569/70): > > You can pull the 32 bit image, by specifying the --platform arm32v6, but the docker should be configured to use experimental features for that. Or use the explicit tag for the 1.18.1 arm image: docker pull storjlabs/storagenode:2413a9a0d-v1.18.1-go1.15.5-arm32v6 Also, please use a full volume binding command instead of simple in the docker-compose: [https://docs.docker.com/compose/compose-file/#long-syntax-3](https://docs.docker.com/compose/compose-file/#long-syntax-3) Use the type bind, otherwise you risking to get a disqualification if your drive woul… The next version should have a fix and we will need to pull the image manually and change the `docker run` back to the `latest` ---
**Author:** ![jjj](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/jjj/32/1129_2.png) [@jjj](https://forum.storj.io/u/jjj)\ **Post date:** [December 23, 2020, 2:01am UTC](https://forum.storj.io/t/x509-certificate-signed-by-unknown-authority-for-https-tardigrade-io-trusted-satellites/10569/91 "2020-12-23T02:01:42Z")
Get this error in the tail of my logs. Checked and the server can resolve anything plus it is downloading and uploading within the docket container. Not sure if I should be concerned about this on? 2020-12-23T00:44:27.808Z WARN trust Failed to fetch URLs from source; used cache {“source”: “[https://tardigrade.io/trusted-satellites](https://tardigrade.io/trusted-satellites)”, “error”: “HTTP source: Get “[https://tardigrade.io/trusted-satellites](https://tardigrade.io/trusted-satellites)”: x509: certificate signed by unknown authority”, “errorVerbose”: “HTTP source: Get “[https://tardigrade.io/trusted-satellites](https://tardigrade.io/trusted-satellites)”: x509: certificate signed by unknown authority\n\[tstorj.io/storj/storagenode/trust.(\*HTTPSource](http://tstorj.io/storj/storagenode/trust.(*HTTPSource)).FetchEntries:63\n\[tstorj.io/storj/storagenode/trust.(\*List](http://tstorj.io/storj/storagenode/trust.(*List)).fetchEntries:90\n\[tstorj.io/storj/storagenode/trust.(\*List](http://tstorj.io/storj/storagenode/trust.(*List)).FetchURLs:49\n\[tstorj.io/storj/storagenode/trust.(\*Pool](http://tstorj.io/storj/storagenode/trust.(*Pool)).fetchURLs:240\n\[tstorj.io/storj/storagenode/trust.(\*Pool](http://tstorj.io/storj/storagenode/trust.(*Pool)).Refresh:177\n\[tstorj.io/storj/storagenode/trust.(\*Pool](http://tstorj.io/storj/storagenode/trust.(*Pool)).Run:114\n\[tstorj.io/storj/private/lifecycle.(\*Group](http://tstorj.io/storj/private/lifecycle.(*Group)).Run.func1:57\n\[tgolang.org/x/sync/errgroup.(\*Group](http://tgolang.org/x/sync/errgroup.(*Group)).Go.func1:57”} ---
**Author:** ![jjj](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/jjj/32/1129_2.png) [@jjj](https://forum.storj.io/u/jjj)\ **Post date:** [December 23, 2020, 2:06am UTC](https://forum.storj.io/t/x509-certificate-signed-by-unknown-authority-for-https-tardigrade-io-trusted-satellites/10569/92 "2020-12-23T02:06:54Z")
PING [tardigrade.io](http://tardigrade.io) (104.198.14.52) 56(84) bytes of data. 64 bytes from [52.14.198.104.bc.googleusercontent.com](http://52.14.198.104.bc.googleusercontent.com) (104.198.14.52): icmp\_seq=1 ttl=106 time=149 ms 64 bytes from Looks like it can be resolved as well ---
**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\ **Post date:** [December 23, 2020, 9:24am UTC](https://forum.storj.io/t/x509-certificate-signed-by-unknown-authority-for-https-tardigrade-io-trusted-satellites/10569/93 "2020-12-23T09:24:03Z")
Have you running your node on FreeNAS? If so the solution is > [@X509: certificate signed by unknown authority](https://forum.storj.io/t/x509-certificate-signed-by-unknown-authority/6926/8): > > I had to use pkg install ca\_root\_nss, that got it working. You want to add this to the FreeNAS instructions, for others, after the FreeNAS instructions become available. ---
**Author:** ![jjj](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/jjj/32/1129_2.png) [@jjj](https://forum.storj.io/u/jjj)\ **Post date:** [December 23, 2020, 10:44pm UTC](https://forum.storj.io/t/x509-certificate-signed-by-unknown-authority-for-https-tardigrade-io-trusted-satellites/10569/94 "2020-12-23T22:44:57Z")
I run a synology. The Cert on the machine and from lookup is ok. This message seems to indicate a Cert problem outside my network does it not? ---
**Author:** ![Odmin](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/odmin/32/92_2.png) [@Odmin](https://forum.storj.io/u/Odmin)\ **Post date:** [December 23, 2020, 11:03pm UTC](https://forum.storj.io/t/x509-certificate-signed-by-unknown-authority-for-https-tardigrade-io-trusted-satellites/10569/95 "2020-12-23T23:03:47Z")
@Alexey @stefanbenten looks like the root cause on the [server-side](https://www.ssllabs.com/ssltest/analyze.html?d=tardigrade.io): Certificate #1: is OK but Certificate #2: ![image](https://storj-s3.bcdn.literatehosting.net/original/2X/e/e28829bade7b5e15b3ffd72af49f61b472e2e729.png) Please inform your responsible person about it because it definitely **a big issue** and **security breach.** ---
**Author:** ![Odmin](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/odmin/32/92_2.png) [@Odmin](https://forum.storj.io/u/Odmin)\ **Post date:** [December 23, 2020, 11:08pm UTC](https://forum.storj.io/t/x509-certificate-signed-by-unknown-authority-for-https-tardigrade-io-trusted-satellites/10569/96 "2020-12-23T23:08:57Z")
The [same issue on storj.io](https://www.ssllabs.com/ssltest/analyze.html?d=storj.io) site: ![image](https://storj-s3.bcdn.literatehosting.net/original/2X/1/1ff4f520fa88911c7231b2a4ad42d32b59ddad8a.png) ---
**Author:** ![deathlessdd](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/deathlessdd/32/6067_2.png) [@deathlessdd](https://forum.storj.io/u/deathlessdd)\ **Post date:** [December 23, 2020, 11:34pm UTC](https://forum.storj.io/t/x509-certificate-signed-by-unknown-authority-for-https-tardigrade-io-trusted-satellites/10569/97 "2020-12-23T23:34:03Z")
Unless these were just fixed I dont see the same errors. Nevermind I didn’t see the second one to expand. I to see the second one. ---
**Author:** ![Odmin](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/odmin/32/92_2.png) [@Odmin](https://forum.storj.io/u/Odmin)\ **Post date:** [December 23, 2020, 11:37pm UTC](https://forum.storj.io/t/x509-certificate-signed-by-unknown-authority-for-https-tardigrade-io-trusted-satellites/10569/98 "2020-12-23T23:37:17Z")
no, it not fixed, you can check it with [ssllabs](https://www.ssllabs.com/ssltest/analyze.html?d=tardigrade.io) and compare for example with [github.com](http://github.com). Certificate #2 - is a big issue. ![image](https://storj-s3.bcdn.literatehosting.net/original/2X/5/5d1910152e8d1799a6c89375d8539439b62a5475.png) ![image](https://storj-s3.bcdn.literatehosting.net/original/2X/9/983e22bc025f54045e6858cfeba496583b9ee4fa.png) ---
**Author:** ![deathlessdd](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/deathlessdd/32/6067_2.png) [@deathlessdd](https://forum.storj.io/u/deathlessdd)\ **Post date:** [December 23, 2020, 11:39pm UTC](https://forum.storj.io/t/x509-certificate-signed-by-unknown-authority-for-https-tardigrade-io-trusted-satellites/10569/99 "2020-12-23T23:39:16Z")
Yeah your right, but it doesnt even look related to storj at all, Both are using the same one though. ---
**Author:** ![Odmin](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/odmin/32/92_2.png) [@Odmin](https://forum.storj.io/u/Odmin)\ **Post date:** [December 23, 2020, 11:41pm UTC](https://forum.storj.io/t/x509-certificate-signed-by-unknown-authority-for-https-tardigrade-io-trusted-satellites/10569/100 "2020-12-23T23:41:27Z")
It a wrong configuration on the server side, and Certificate #2 should NOT be here. [Previous page](https://forum.storj.io/t/x509-certificate-signed-by-unknown-authority-for-https-tardigrade-io-trusted-satellites/10569.md?page=4) [Next page](https://forum.storj.io/t/x509-certificate-signed-by-unknown-authority-for-https-tardigrade-io-trusted-satellites/10569.md?page=6)