[GH-ISSUE #1076] 1.7.0 broke all resources except pangolin #1750

Closed
opened 2026-04-16 08:33:35 -05:00 by GiteaMirror · 15 comments
Owner

Originally created by @C8opmBM on GitHub (Jul 17, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1076

I updated to latest, but now all my sites are 404.

Logs read: No exit node found in the database

The pangolin site does work though.
I don't use gerbil, it's a local site only.
Thanks!

Originally created by @C8opmBM on GitHub (Jul 17, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/1076 I updated to latest, but now all my sites are 404. Logs read: `No exit node found in the database` The pangolin site does work though. I don't use gerbil, it's a local site only. Thanks!
Author
Owner

@saufdermaur commented on GitHub (Jul 17, 2025):

Same problem here.

<!-- gh-comment-id:3085504536 --> @saufdermaur commented on GitHub (Jul 17, 2025): Same problem here.
Author
Owner

@nesalkiN commented on GitHub (Jul 17, 2025):

Same here. I use gerbil, and Newt and so on.

pangolin  | 2025-07-17T21:26:56.394Z [error]: No valid exit nodes available
pangolin  | 2025-07-17T21:26:56.396Z [warn]: No suitable exit node found based on ping results

And btw, this does not look right? Not affecting me as I upgraded:
e8793c5d8d/install/config/config.yml (L33)

<!-- gh-comment-id:3085537739 --> @nesalkiN commented on GitHub (Jul 17, 2025): Same here. I use gerbil, and Newt and so on. ```pangolin | 2025-07-17T21:26:56.393Z [info]: Handling register newt message! pangolin | 2025-07-17T21:26:56.394Z [error]: No valid exit nodes available pangolin | 2025-07-17T21:26:56.396Z [warn]: No suitable exit node found based on ping results ``` And btw, this does not look right? Not affecting me as I upgraded: https://github.com/fosrl/pangolin/blob/e8793c5d8dc189a5a65b2735dc12cc7ba748325f/install/config/config.yml#L33
Author
Owner

@miloschwartz commented on GitHub (Jul 17, 2025):

Looking into it

<!-- gh-comment-id:3085541481 --> @miloschwartz commented on GitHub (Jul 17, 2025): Looking into it
Author
Owner

@nesalkiN commented on GitHub (Jul 17, 2025):

No domain(s) in the list when trying to add or edit resources either but I can see the domain under Domains.
I have 1 local site, the others via Newt. All down.

<!-- gh-comment-id:3085630693 --> @nesalkiN commented on GitHub (Jul 17, 2025): No domain(s) in the list when trying to add or edit resources either but I can see the domain under Domains. I have 1 local site, the others via Newt. All down.
Author
Owner

@miloschwartz commented on GitHub (Jul 17, 2025):

@nesalkiN You have to type in the full intended domain of the resource now for the domains to pop up

<!-- gh-comment-id:3085645881 --> @miloschwartz commented on GitHub (Jul 17, 2025): @nesalkiN You have to type in the full intended domain of the resource now for the domains to pop up
Author
Owner

@miloschwartz commented on GitHub (Jul 17, 2025):

For Newt, to immediately fix it, downgrade Newt. We're releasing a patch to Newt and Pangolin here shortly

<!-- gh-comment-id:3085647391 --> @miloschwartz commented on GitHub (Jul 17, 2025): For Newt, to immediately fix it, downgrade Newt. We're releasing a patch to Newt and Pangolin here shortly
Author
Owner

@nesalkiN commented on GitHub (Jul 17, 2025):

@nesalkiN You have to type in the full intended domain of the resource now for the domains to pop up

I see. I was expecting the list to populate with something. Thanks.

<!-- gh-comment-id:3085648161 --> @nesalkiN commented on GitHub (Jul 17, 2025): > [@nesalkiN](https://github.com/nesalkiN) You have to type in the full intended domain of the resource now for the domains to pop up I see. I was expecting the list to populate with something. Thanks.
Author
Owner

@miloschwartz commented on GitHub (Jul 17, 2025):

I see. Thanks. I was expecting the list to populate with something. Thanks.

We'll improve this UX. The domain picker is ported from the Cloud version

<!-- gh-comment-id:3085657412 --> @miloschwartz commented on GitHub (Jul 17, 2025): > I see. Thanks. I was expecting the list to populate with something. Thanks. We'll improve this UX. The domain picker is ported from the Cloud version
Author
Owner

@afunworm commented on GitHub (Jul 17, 2025):

Following. I have the same problems. However, no error log from traefik, gerbil or pangolin. Only local sites. I have to do a fresh installation on 1.6.2 again.

<!-- gh-comment-id:3085725121 --> @afunworm commented on GitHub (Jul 17, 2025): Following. I have the same problems. However, no error log from traefik, gerbil or pangolin. Only local sites. I have to do a fresh installation on 1.6.2 again.
Author
Owner

@darkcloud784 commented on GitHub (Jul 17, 2025):

Same issue, can't roll back due to the db changes and it being sqlite.

<!-- gh-comment-id:3085731355 --> @darkcloud784 commented on GitHub (Jul 17, 2025): Same issue, can't roll back due to the db changes and it being sqlite.
Author
Owner

@nesalkiN commented on GitHub (Jul 17, 2025):

Same issue, can't roll back due to the db changes and it being sqlite.

There are db backups in /config/db/backups

Up and running again after updating Newt and Pangolin. Thanks!

<!-- gh-comment-id:3085734265 --> @nesalkiN commented on GitHub (Jul 17, 2025): > Same issue, can't roll back due to the db changes and it being sqlite. There are db backups in /config/db/backups Up and running again after updating Newt and Pangolin. Thanks!
Author
Owner

@miloschwartz commented on GitHub (Jul 17, 2025):

1.7.1 is out!

<!-- gh-comment-id:3085734969 --> @miloschwartz commented on GitHub (Jul 17, 2025): 1.7.1 is out!
Author
Owner

@darkcloud784 commented on GitHub (Jul 17, 2025):

1.7.1 is out!

Thank you sir, this fixed everything for me.

<!-- gh-comment-id:3085740832 --> @darkcloud784 commented on GitHub (Jul 17, 2025): > 1.7.1 is out! Thank you sir, this fixed everything for me.
Author
Owner

@afunworm commented on GitHub (Jul 17, 2025):

1.7.1 is out!

Noob question, but when you say incremental backup, do you mean I have to go from 1.6.2 -> 1.7.0 first, then 1.7.1? Or can I just jump from 1.6.2 -> 1.7.1?

<!-- gh-comment-id:3085860534 --> @afunworm commented on GitHub (Jul 17, 2025): > 1.7.1 is out! Noob question, but when you say incremental backup, do you mean I have to go from 1.6.2 -> 1.7.0 first, then 1.7.1? Or can I just jump from 1.6.2 -> 1.7.1?
Author
Owner

@miloschwartz commented on GitHub (Jul 18, 2025):

Safest thing is to do 1.6.2 -> 1.7.0 -> 1.7.1

<!-- gh-comment-id:3086117257 --> @miloschwartz commented on GitHub (Jul 18, 2025): Safest thing is to do 1.6.2 -> 1.7.0 -> 1.7.1
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#1750