after installation, the pangolin dashboard has a self-signed certificate and newt cannot connect #1788

New Issue

MrUnknownDE · 2026-04-05T19:41:53+02:00

MrUnknownDE commented

2026-04-05 19:41:53 +02:00

Originally created by @badbrain79 on 2/12/2025

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 2/12/2025* 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

MrUnknownDE closed this issue

2026-04-05 19:41:53 +02:00

Sign in to join this conversation.

Branches Tags

main

dev

dependabot/npm_and_yarn/dev-minor-updates-b4e5d6b9c5

revert-2766-feature/systemd-install-instructions

dependabot/npm_and_yarn/prod-patch-updates-05702d39f2

dependabot/npm_and_yarn/next-16.2.1

dependabot/npm_and_yarn/recharts-3.8.1

alerting-rules

private-site-ha

dependabot/docker/docker/library/node-25-slim

ssh

delete-account

msg-delivery

org-only-idp

cicd

patch

site-targets-auto-login

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/pangolin#1788