[GH-ISSUE #192] after installation, the pangolin dashboard has a self-signed certificate and newt cannot connect #3276

New Issue

GiteaMirror · 2026-04-20T07:12:08-05:00

GiteaMirror commented

2026-04-20 07:12:08 -05:00

Originally created by @badbrain79 on GitHub (Feb 12, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/192

Hello,
First of all, thank you for your work on the project.
I have installed pangolin on a cloud server with ubuntu 24.04 and then open the dashboard and started the newt container with the id and the secret at my home.
In the logs of newt you can see that it cannot connect because pangolin uses a self-signed certificate:

ERROR: 2025/02/12 06:24:15 Failed to connect: failed to get token: failed to request new token: Post "https://..nas64.de/api/v1/auth/newt/get-token": tls: failed to verify certificate: x509: certificate is valid for 0f16e4fb9bddcc8a8c8b8e757a886c86.2e01c1244bc60517e1a094928d7dc56e.traefik.default, not ..nas64.de. Retrying in 10s...
ERROR: 2025/02/12 06:24:25 Failed to connect: failed to get token: failed to request new token: Post "https://..nas64.de/api/v1/auth/newt/get-token": tls: failed to verify certificate: x509: certificate is valid for

(I have replaced the domain name with *)

but the DNS entry for the domain points to the cloud server with A and AAAA record

i'm not sure if pangolin creates a let's encrypt certificate itself or if i have to do it manually

Originally created by @badbrain79 on GitHub (Feb 12, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/192 Hello, First of all, thank you for your work on the project. I have installed pangolin on a cloud server with ubuntu 24.04 and then open the dashboard and started the newt container with the id and the secret at my home. In the logs of newt you can see that it cannot connect because pangolin uses a self-signed certificate: ERROR: 2025/02/12 06:24:15 Failed to connect: failed to get token: failed to request new token: Post "https://***.***.nas64.de/api/v1/auth/newt/get-token": tls: failed to verify certificate: x509: certificate is valid for 0f16e4fb9bddcc8a8c8b8e757a886c86.2e01c1244bc60517e1a094928d7dc56e.traefik.default, not ***.***.nas64.de. Retrying in 10s... ERROR: 2025/02/12 06:24:25 Failed to connect: failed to get token: failed to request new token: Post "https://***.***.nas64.de/api/v1/auth/newt/get-token": tls: failed to verify certificate: x509: certificate is valid for (I have replaced the domain name with *) but the DNS entry for the domain points to the cloud server with A and AAAA record i'm not sure if pangolin creates a let's encrypt certificate itself or if i have to do it manually

GiteaMirror closed this issue

2026-04-20 07:12:09 -05:00

GiteaMirror commented

2026-04-20 07:12:10 -05:00

@wkennedy commented on GitHub (Feb 13, 2025):

I'm seeing this as well, how did you resolve this?

EDIT: Just for anyone else that might run into this, I resolved it by configuring Traefik for DNS challenge:

https://docs.fossorial.io/Pangolin/Configuration/wildcard-certs#wildcard-config-for-dns-01-challenge

@wkennedy commented on GitHub (Feb 13, 2025): I'm seeing this as well, how did you resolve this? EDIT: Just for anyone else that might run into this, I resolved it by configuring Traefik for DNS challenge: https://docs.fossorial.io/Pangolin/Configuration/wildcard-certs#wildcard-config-for-dns-01-challenge

GiteaMirror referenced this issue

2026-06-15 10:58:17 -05:00

[PR #3276] [MERGED] Rewrite headers #33564

GiteaMirror referenced this issue

2026-06-18 22:11:11 -05:00

[PR #3276] [MERGED] Rewrite headers #36924

Sign in to join this conversation.