# Remote error: tls: bad certificate

**URL:** <https://www.thethingsnetwork.org/forum/t/remote-error-tls-bad-certificate/35445>\
**Category:** The Things Stack v3\
**Created:** [March 17, 2020, 9:29pm UTC](https://www.thethingsnetwork.org/forum/t/remote-error-tls-bad-certificate/35445 "2020-03-17T21:29:29Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![cyclops](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/cyclops/32/25844_2.png) [@cyclops](https://www.thethingsnetwork.org/forum/u/cyclops)\
**Post date:** [March 17, 2020, 9:29pm UTC](https://www.thethingsnetwork.org/forum/t/remote-error-tls-bad-certificate/35445/1 "2020-03-17T21:29:29Z")

</div>

Hi,

I’m trying to setup TTN Stack v3.6.0 via the getting started guide.

In the console i see this:  
stack\_1 | INFO Request handled duration=1.244971616s location=/console/oauth/callback?code=MF2XI.PCMSOLRBS7BTTXFCSUF4YOCBFMOFVM4BQSS3NEA.LN72OCLQT3PZME3MFF3CTMGNDXYSDYAREHHJOLXYD5TK752CNV6A&state=2o078ynjIQChSMZQ method=GET namespace=web remote\_addr=192.168.1.1:59578 request\_id=01E3N66R2H5D1Y17XEQDXZE93G response\_size=0 status=302 url=/oauth/authorize?client\_id=console&redirect\_uri=%2Fconsole%2Foauth%2Fcallback&response\_type=code&state=2o078ynjIQChSMZQ  
stack\_1 | 2020/03/17 21:25:47 http: TLS handshake error from 172.19.0.1:45398: remote error: tls: bad certificate

I’ve used a self-signed certificate. I created the root CA myself which i use on my network.  
i’ve [read that i should have the container trust the certificate as well](https://www.thethingsnetwork.org/forum/t/ttn-stack-v3-with-private-certificate-internal-server-error/32177/2), but i’ve got no clue how to do that (As i’m a docker n00b).

So, how do i configure the docker compose to accept my self-signed certificate by trusting the root CA?

---

<div class="post-metadata">

**Author:** ![htdvisser](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/htdvisser/32/45312_2.png) [@htdvisser](https://www.thethingsnetwork.org/forum/u/htdvisser)\
**Post date:** [March 18, 2020, 10:38am UTC](https://www.thethingsnetwork.org/forum/t/remote-error-tls-bad-certificate/35445/2 "2020-03-18T10:38:14Z")

</div>

The Getting Started guide intentionally does not cover self-signed certificates. You should really consider setting up your deployment in the cloud, and use the Let’s Encrypt support that is already built into The Things Stack.

---

<div class="post-metadata">

**Author:** ![cyclops](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/cyclops/32/25844_2.png) [@cyclops](https://www.thethingsnetwork.org/forum/u/cyclops)\
**Post date:** [March 18, 2020, 1:26pm UTC](https://www.thethingsnetwork.org/forum/t/remote-error-tls-bad-certificate/35445/3 "2020-03-18T13:26:43Z")

</div>

Thanks for helping!

I know what you mean, and don’t disagree at all.

The problem is, i’m testing on a local network. I don’t want to host this thing so that external people can access it (which is what you need to do with letencrypt for it’s verification).  
Next to that, i have a self signed CA anyway, i had my certs generated with a script that i use for all my internal services. So i would like to just re-use that.

Alternatively, i’m also happy to just disable SSL completely. I mean - it’s local and a test, i don’t need this encryption at the moment 🙂

---

<div class="post-metadata">

**Author:** ![system](https://www.thethingsnetwork.org/forum/uploads/default/original/3X/6/2/6250ea44fd2b0d6259489e1a92748df681e1f970.png) [@system](https://www.thethingsnetwork.org/forum/u/system)\
**Post date:** [April 16, 2020, 9:29pm UTC](https://www.thethingsnetwork.org/forum/t/remote-error-tls-bad-certificate/35445/4 "2020-04-16T21:29:30Z")

</div>

This topic was automatically closed after 30 days. New replies are no longer allowed.
