[GH-ISSUE #759] pangolin not applying certificates #22904

New Issue

GiteaMirror · 2026-06-05T05:07:43-05:00

GiteaMirror commented

2026-06-05 05:07:43 -05:00

Originally created by @calim20 on GitHub (May 21, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/759

Hi,
I've moved my uptime-kuma setup to another server which is already connected as site. Discourse is working on the server with an localhost port and pangolin serves the site without errors. In the same way I've set up uptime-kuma with 127.0.0.1:3001. I've added it as resource with a new subdomain. Unfortunately pangolin does not serve the site, it not even shows the PIN login site. Firefox shows "PR_END_OF_FILE_ERROR" on https and a nginx welcome page on http.
I've checked the certificates, it shows in acme.json. When I stop pangolin and delete acme.json it gets recreated on startup including all configured subdomains, but still does not work.

Thanks for any hints!
Marco

Originally created by @calim20 on GitHub (May 21, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/759 Hi, I've moved my uptime-kuma setup to another server which is already connected as site. Discourse is working on the server with an localhost port and pangolin serves the site without errors. In the same way I've set up uptime-kuma with 127.0.0.1:3001. I've added it as resource with a new subdomain. Unfortunately pangolin does not serve the site, it not even shows the PIN login site. Firefox shows "PR_END_OF_FILE_ERROR" on https and a nginx welcome page on http. I've checked the certificates, it shows in acme.json. When I stop pangolin and delete acme.json it gets recreated on startup including all configured subdomains, but still does not work. Thanks for any hints! Marco

GiteaMirror closed this issue

2026-06-05 05:07:43 -05:00

GiteaMirror commented

2026-06-05 05:07:44 -05:00

@oschwartz10612 commented on GitHub (May 22, 2025):

Hi Marco,

I am tempted to say that maybe this is just pointing at the wrong port or something? If you are seeing a Nginx welcome page that can not be from Pagnolin itself because Pangolin does not use Nginx. So I think it is getting to your resource and if you have the ssl switch checked then that is probably why it is working on https. Could you give it a check and let me know?

@oschwartz10612 commented on GitHub (May 22, 2025): Hi Marco, I am tempted to say that maybe this is just pointing at the wrong port or something? If you are seeing a Nginx welcome page that can not be from Pagnolin itself because Pangolin does not use Nginx. So I think it is getting to your resource and if you have the ssl switch checked then that is probably why it is working on https. Could you give it a check and let me know?

GiteaMirror commented

2026-06-05 05:07:45 -05:00

@calim20 commented on GitHub (May 22, 2025):

Hi,

Hmm, seems my general understanding of the settings in pangolin is a bit off.

I've got 2 VPS.
VPS1 is running pangolin in docker and pangolin is accessible.
VPS2 has newt running on debian directly via systemd and is connected to pangolin as site "server". It's online.
VPS2 has discourse running (docker) and publishing 127.0.0.1:90->80/tcp
VPS2 has uptime-kuma (docker) running and publishing 127.0.0.1:300->3001/tcp
Discourse is configured as resource in pangolin with a subdomain and "http localhost 90" in the proxy settings. PIN authentication is active. The site is reachable and works.
uptime-kuma is configured as resource in pangolin with a subdomain and "http localhost 300" in the proxy settings. PIN authentication is active. When I try to reach uptime I get either a nginx welcome page with http or a PR_END_OF_FILE_ERROR with https. No PIN authentication beforehand.
Only other service running on VPS2 is dockge which is publishing 127.0.0.1:5001->5001/tcp. I haven't tried to access it via pangolin, yet.

Where did I go wrong? It seems I have blinders on... sorry.

Best,
Marco

PS: I checked for nginx using ps -ef and found serveral processes. There is no nginx installed on os level and no configuration files. When killed the processes are restarted. I guess it's from discourse. I will try shut down discourse and have a look what happens.

@calim20 commented on GitHub (May 22, 2025): Hi, Hmm, seems my general understanding of the settings in pangolin is a bit off. - I've got 2 VPS. - VPS1 is running pangolin in docker and pangolin is accessible. - VPS2 has newt running on debian directly via systemd and is connected to pangolin as site "server". It's online. - VPS2 has discourse running (docker) and publishing 127.0.0.1:90->80/tcp - VPS2 has uptime-kuma (docker) running and publishing 127.0.0.1:300->3001/tcp - Discourse is configured as resource in pangolin with a subdomain and "http localhost 90" in the proxy settings. PIN authentication is active. The site is reachable and works. - uptime-kuma is configured as resource in pangolin with a subdomain and "http localhost 300" in the proxy settings. PIN authentication is active. When I try to reach uptime I get either a nginx welcome page with http or a PR_END_OF_FILE_ERROR with https. No PIN authentication beforehand. - Only other service running on VPS2 is dockge which is publishing 127.0.0.1:5001->5001/tcp. I haven't tried to access it via pangolin, yet. Where did I go wrong? It seems I have blinders on... sorry. Best, Marco PS: I checked for nginx using `ps -ef` and found serveral processes. There is no nginx installed on os level and no configuration files. When killed the processes are restarted. I guess it's from discourse. I will try shut down discourse and have a look what happens.

GiteaMirror commented

2026-06-05 05:07:45 -05:00

@calim20 commented on GitHub (May 22, 2025):

Sorry, sleep deprivation is getting to me. There was a orphaned entry in the hosts file. My fault.

@calim20 commented on GitHub (May 22, 2025): Sorry, sleep deprivation is getting to me. There was a orphaned entry in the hosts file. My fault.

Sign in to join this conversation.

Branches Tags

main

dev

dependabot/npm_and_yarn/npm-dependencies-8b2d4a9f3a

local-connection

dependabot/go_modules/install/go-install-dependencies-3804ca7238

dependabot/docker/docker-dependencies-4faa477378

dependabot/github_actions/github-actions-dependencies-6d79802a48

api-improvements

feat/remember-last-idp-on-smart-login-form

refactor/batch-status-requests

dependabot/npm_and_yarn/multi-5f1280885e

fix/non-semver-version-error

private-resource-page

resource-launcher

backhaul

exit-node-reconnect

feat/command-palette

ssh

delete-account

msg-delivery

org-only-idp

cicd

patch

site-targets-auto-login

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/pangolin#22904