github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-07-16 14:47:04 -05:00
Code Issues 1.6k Packages Projects Releases 79 Wiki Activity

[GH-ISSUE #2601] Dashboard works for a few minutes then throws ERR_SSL_PROTOCOL_ERROR #27815

New Issue
Closed
opened 2026-06-10 23:17:19 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-06-10 23:17:19 -05:00
Owner
Copy Link

Originally created by @shusterrooster on GitHub (Mar 5, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2601

Describe the Bug

My dashboard randomly stopped working. I went to install Pangolin fresh because the instance wasn't working. I have been able to create the admin user but then after that, all I get is a ERR_SSL_PROTOCOL_ERROR response.

The SSL certificate seems to be valid and the IP seems to be pointing to the right location. The Docker containers are also running healthily.

Environment

  • OS Type & Version: 24.04
  • Pangolin Version: 1.16.2
  • Gerbil Version: 1.3.0
  • Traefik Version: 3.6
  • Newt Version:
  • Olm Version: (if applicable)

To Reproduce

I haven't been able to test a reproduction as I don't have a port exposed to test SSL certs with (or maybe I can do it locally but I am unsure)

Fresh install of Ubuntu, use quick installer. Set up normally. After auth token is entered, the SSL error will persist.

Expected Behavior

You are supposed to see the dashboard normally.

Originally created by @shusterrooster on GitHub (Mar 5, 2026). Original GitHub issue: https://github.com/fosrl/pangolin/issues/2601 ### Describe the Bug My dashboard randomly stopped working. I went to install Pangolin fresh because the instance wasn't working. I have been able to create the admin user but then after that, all I get is a ERR_SSL_PROTOCOL_ERROR response. The SSL certificate seems to be valid and the IP seems to be pointing to the right location. The Docker containers are also running healthily. ### Environment - OS Type & Version: 24.04 - Pangolin Version: 1.16.2 - Gerbil Version: 1.3.0 - Traefik Version: 3.6 - Newt Version: - Olm Version: (if applicable) ### To Reproduce I haven't been able to test a reproduction as I don't have a port exposed to test SSL certs with (or maybe I can do it locally but I am unsure) Fresh install of Ubuntu, use quick installer. Set up normally. After auth token is entered, the SSL error will persist. ### Expected Behavior You are supposed to see the dashboard normally.
GiteaMirror commented 2026-06-10 23:17:20 -05:00
Author
Owner
Copy Link

@plagor44-ux commented on GitHub (Mar 5, 2026):

What kind of certificate provider are you using? Let's encrypt or something else? For http challenge port 80 needs to be open.

Sounds like a traefik issue to me. You might want to check those logs.

<!-- gh-comment-id:4002292107 --> @plagor44-ux commented on GitHub (Mar 5, 2026): What kind of certificate provider are you using? Let's encrypt or something else? For http challenge port 80 needs to be open. Sounds like a traefik issue to me. You might want to check those logs.
GiteaMirror commented 2026-06-10 23:17:20 -05:00
Author
Owner
Copy Link

@shusterrooster commented on GitHub (Mar 5, 2026):

I checked the traefik logs and it looks like I submitted too many requests for new SSL certs with Let's Encrypt. I generated a new one after the restriction was lifted and now I am getting errors from the Pangolin container.

Here's what the Pangolin container returned:

2026-03-05T17:55:45+00:00 [info]: API server is running on http://localhost:3000
2026-03-05T17:55:45+00:00 [info]: Internal server is running on http://localhost:3001
2026-03-05T17:55:48+00:00 [info]: Next.js server is running on http://localhost:3002
2026-03-05T17:55:48+00:00 [info]: Updated exit node reachableAt to http://gerbil:3004
2026-03-05T18:05:11+00:00 [info]: Updated exit node reachableAt to http://gerbil:3004
npm error path /app
npm error command failed
npm error signal SIGTERM
npm error command sh -c ENVIRONMENT=prod node dist/migrations.mjs && ENVIRONMENT=prod NODE_ENV=development node --enable-source-maps dist/server.mjs
npm error A complete log of this run can be found in: /root/.npm/_logs/2026-03-05T17_55_37_294Z-debug-0.log

> @fosrl/pangolin@0.0.0 start
> ENVIRONMENT=prod node dist/migrations.mjs && ENVIRONMENT=prod NODE_ENV=development node --enable-source-maps dist/server.mjs

Here's the log file it points to:

1 info using npm@11.9.0
2 info using node@v24.14.0
3 silly config load:file:/usr/local/lib/node_modules/npm/npmrc
4 silly config load:file:/app/.npmrc
5 silly config load:file:/root/.npmrc
6 silly config load:file:/usr/local/etc/npmrc
7 verbose title npm run start
8 verbose argv "run" "start"
9 verbose logfile logs-max:10 dir:/root/.npm/_logs/2026-03-05T18_05_22_299Z-
10 verbose logfile /root/.npm/_logs/2026-03-05T18_05_22_299Z-debug-0.log
11 silly logfile done cleaning log files
12 verbose stack Error: command failed
12 verbose stack     at promiseSpawn (/usr/local/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/lib/index.js:22:22)
12 verbose stack     at spawnWithShell (/usr/local/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/lib/index.js:124:10)
12 verbose stack     at promiseSpawn (/usr/local/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/lib/index.js:12:12)
12 verbose stack     at runScriptPkg (/usr/local/lib/node_modules/npm/node_modules/@npmcli/run-script/lib/run-script-pkg.js:79:13)
12 verbose stack     at runScript (/usr/local/lib/node_modules/npm/node_modules/@npmcli/run-script/lib/run-script.js:9:12)
12 verbose stack     at #run (/usr/local/lib/node_modules/npm/lib/commands/run.js:135:13)
12 verbose stack     at async RunScript.exec (/usr/local/lib/node_modules/npm/lib/commands/run.js:44:7)
12 verbose stack     at async Npm.exec (/usr/local/lib/node_modules/npm/lib/npm.js:208:9)
12 verbose stack     at async module.exports (/usr/local/lib/node_modules/npm/lib/cli/entry.js:67:5)
13 verbose pkgid @fosrl/pangolin@0.0.0
14 error path /app
15 error command failed
16 error signal SIGTERM
17 error command sh -c ENVIRONMENT=prod node dist/migrations.mjs && ENVIRONMENT=prod NODE_ENV=development node --enable-source-maps dist/server.mjs
18 verbose cwd /app
19 verbose os Linux 6.8.0-101-generic
20 verbose node v24.14.0
21 verbose npm  v11.9.0
22 verbose exit 1
23 verbose code 1
24 error A complete log of this run can be found in: /root/.npm/_logs/2026-03-05T18_05_22_299Z-debug-0.log

However, it doesn't seem like the other containers can communicate with each other despite saying they are running healthily. Any thoughts?

<!-- gh-comment-id:4006816828 --> @shusterrooster commented on GitHub (Mar 5, 2026): I checked the traefik logs and it looks like I submitted too many requests for new SSL certs with Let's Encrypt. I generated a new one after the restriction was lifted and now I am getting errors from the Pangolin container. Here's what the Pangolin container returned: ``` 2026-03-05T17:55:45+00:00 [info]: API server is running on http://localhost:3000 2026-03-05T17:55:45+00:00 [info]: Internal server is running on http://localhost:3001 2026-03-05T17:55:48+00:00 [info]: Next.js server is running on http://localhost:3002 2026-03-05T17:55:48+00:00 [info]: Updated exit node reachableAt to http://gerbil:3004 2026-03-05T18:05:11+00:00 [info]: Updated exit node reachableAt to http://gerbil:3004 npm error path /app npm error command failed npm error signal SIGTERM npm error command sh -c ENVIRONMENT=prod node dist/migrations.mjs && ENVIRONMENT=prod NODE_ENV=development node --enable-source-maps dist/server.mjs npm error A complete log of this run can be found in: /root/.npm/_logs/2026-03-05T17_55_37_294Z-debug-0.log > @fosrl/pangolin@0.0.0 start > ENVIRONMENT=prod node dist/migrations.mjs && ENVIRONMENT=prod NODE_ENV=development node --enable-source-maps dist/server.mjs ``` Here's the log file it points to: ```0 verbose cli /usr/local/bin/node /usr/local/bin/npm 1 info using npm@11.9.0 2 info using node@v24.14.0 3 silly config load:file:/usr/local/lib/node_modules/npm/npmrc 4 silly config load:file:/app/.npmrc 5 silly config load:file:/root/.npmrc 6 silly config load:file:/usr/local/etc/npmrc 7 verbose title npm run start 8 verbose argv "run" "start" 9 verbose logfile logs-max:10 dir:/root/.npm/_logs/2026-03-05T18_05_22_299Z- 10 verbose logfile /root/.npm/_logs/2026-03-05T18_05_22_299Z-debug-0.log 11 silly logfile done cleaning log files 12 verbose stack Error: command failed 12 verbose stack at promiseSpawn (/usr/local/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/lib/index.js:22:22) 12 verbose stack at spawnWithShell (/usr/local/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/lib/index.js:124:10) 12 verbose stack at promiseSpawn (/usr/local/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/lib/index.js:12:12) 12 verbose stack at runScriptPkg (/usr/local/lib/node_modules/npm/node_modules/@npmcli/run-script/lib/run-script-pkg.js:79:13) 12 verbose stack at runScript (/usr/local/lib/node_modules/npm/node_modules/@npmcli/run-script/lib/run-script.js:9:12) 12 verbose stack at #run (/usr/local/lib/node_modules/npm/lib/commands/run.js:135:13) 12 verbose stack at async RunScript.exec (/usr/local/lib/node_modules/npm/lib/commands/run.js:44:7) 12 verbose stack at async Npm.exec (/usr/local/lib/node_modules/npm/lib/npm.js:208:9) 12 verbose stack at async module.exports (/usr/local/lib/node_modules/npm/lib/cli/entry.js:67:5) 13 verbose pkgid @fosrl/pangolin@0.0.0 14 error path /app 15 error command failed 16 error signal SIGTERM 17 error command sh -c ENVIRONMENT=prod node dist/migrations.mjs && ENVIRONMENT=prod NODE_ENV=development node --enable-source-maps dist/server.mjs 18 verbose cwd /app 19 verbose os Linux 6.8.0-101-generic 20 verbose node v24.14.0 21 verbose npm v11.9.0 22 verbose exit 1 23 verbose code 1 24 error A complete log of this run can be found in: /root/.npm/_logs/2026-03-05T18_05_22_299Z-debug-0.log ``` However, it doesn't seem like the other containers can communicate with each other despite saying they are running healthily. Any thoughts?
GiteaMirror commented 2026-06-10 23:17:21 -05:00
Author
Owner
Copy Link

@shusterrooster commented on GitHub (Mar 5, 2026):

Here is what I am getting from Traefik:

2026-03-05T18:07:10Z ERR Provider error, retrying in 425.540171ms error="cannot fetch configuration data: do fetch request: Get \"http://pangolin:3001/api/v1/traefik-config\": dial tcp 172.18.0.3:3001: connect: connection refused" providerName=http
<!-- gh-comment-id:4006839097 --> @shusterrooster commented on GitHub (Mar 5, 2026): Here is what I am getting from Traefik: ``` 2026-03-05T18:07:10Z ERR Provider error, retrying in 425.540171ms error="cannot fetch configuration data: do fetch request: Get \"http://pangolin:3001/api/v1/traefik-config\": dial tcp 172.18.0.3:3001: connect: connection refused" providerName=http ```
GiteaMirror commented 2026-06-10 23:17:22 -05:00
Author
Owner
Copy Link

@shusterrooster commented on GitHub (Mar 5, 2026):

FIGURED IT OUT!!!! my ISP was blocking my connection to the Pangolin instance for whatever reason. Using a VPN and it works fine lol

<!-- gh-comment-id:4006972575 --> @shusterrooster commented on GitHub (Mar 5, 2026): FIGURED IT OUT!!!! my ISP was blocking my connection to the Pangolin instance for whatever reason. Using a VPN and it works fine lol
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#27815
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?