mirror of
https://github.com/fosrl/pangolin.git
synced 2026-07-15 21:31:24 -05:00
[GH-ISSUE #1676] Proxmox refresh #29805
Reference in New Issue
Block a user
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?
Originally created by @TacitTactics on GitHub (Oct 16, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1676
Describe the Bug
I do not know where to get the logs for this issue but it is quite frustrating. I love this tool but when running proxmox ve 9 through newt the refresh/migrations make proxmox unusable. I ended up running proxmox through nginx rp over headscale overlay VPN. I think it has something to do with rate limiting but I'm not sure.
Once again I love this application and the work you all put into it.
Environment
To Reproduce
Nothing special
Expected Behavior
Infrequent refreshes and migrations for proxmox
@AstralDestiny commented on GitHub (Oct 19, 2025):
Sorry how is newt deployed currently? Refresh migrations is happening where? If I spin up a proxmox where can I go to replicate this?
@TacitTactics commented on GitHub (Oct 20, 2025):
Thanks for the fast reply. Newt is deployed through docker compose. I have only 1 site with about 7 resources.
The migration is something that proxmox says when it is refreshing tokens I believe. Either way I do not get the migration issue when using basic nginx server block.
To answer your question I have never tried to find any tweaks to the migration of sessions. I have never needed to on nginx. I did have the migration happen when using cloudflare zero trust tunnel but it was not frequent so I was still able to use it.
Do you think it has to do with newt? If so what logs should I check fist?
Thank you again and great tool so far. I am running more than 13 services for my home lab because of this product.
@AstralDestiny commented on GitHub (Nov 3, 2025):
More then one proxmox or just a single proxmox sorry? Also sorry for delay the linear thing went poof.
@TacitTactics commented on GitHub (Nov 4, 2025):
I am running only one proxmox instance.
On Mon, Nov 3, 2025, 5:50 PM AstralDestiny @.***> wrote:
@AstralDestiny commented on GitHub (Nov 5, 2025):
So what do I need to do for the refresh sorry? To test and replicate?
@github-actions[bot] commented on GitHub (Nov 20, 2025):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@TacitTactics commented on GitHub (Nov 21, 2025):
I love this project, but I will just use nginx for proxmox. Just too many refreshes and migrations to make usable. Thanks
@TacitTactics commented on GitHub (Nov 29, 2025):
Oh I do see that newt is disconnecting and then reconnecting due to public mismatch. Is this because version of pangolin and newt are out of sync?
@TacitTactics commented on GitHub (Nov 30, 2025):
So sorry, I found out that my issue was that I was installing too many Newt Docker containers per site. I should have really read the documentation better. Only one installation of Newt per site. One site per VLAN is ideal. Thank you