Automatic Site Updates

Describe the Bug

Automatic Site Updates don't seem to be working for my binary cli site installations. I'm still on v0.20.0 after three days since release of v0.21.0.

Environment

Latest hosted Pangolin with site cli installed on Ubuntu 24.04 LTS and 26.04 LTS.

To Reproduce

running sites with Pangolin CLI and not updating after a new release.

AI Disclosure

none

Expected Behavior

sites update to latest version automatically.

Ahh okay. Yes please reach out to support@pangolin.net and reference this issue. I am going to close this here now but we will get this resolved. /close

Do you see anything in the logs or can you provide a log output from the site? If it is failing to update for some reason we would see it in there. Otherwise, do you have the global updates enabled on the org and does the site also show the updates are enabled?

Thanks. I first had just local site updates enabled, and then added the global update feature as well, hoping it might trigger something. Again, this is happening on four site servers. The logs for one don't reveal much, except an old entry that was due to another issue.

Oct 22 15:05:06 bridge1 pangolin[849]: ERROR: 2026/10/22 15:05:06 Auto-update check failed: server returned status 500: {"data":null,"success":false,"error":true,"mess>

**update - I did just find the same issue for today on other servers:
2026/11/09 16:36:57 Auto-update check failed: server returned status 500

Can you tell me the URL it's checking for updates to I can look at DNS/Firewall? Although, I'm able to update manually which I assume is the same URL.

~~I think I found the issue. I wasn't look at the entire log entry. These servers used to use newt and I moved to the cli for sites. Here's the log:~~

Nov 09 16:37:10 newt1 pangolin[710]: ERROR: 2026/11/09 16:37:10 Auto-update check failed: server returned status 500: {"data":null,"success":false,"error":true,"message":"Unable to determine latest Newt version","status":500,"stack":null}

newt1 is just the name of the server.

@Stunt0265 That seems like a good clue! Would you be able to check if there are any server side errors as well in the Pangolin container? Perhaps it cant reach the versions api or something else is going on?

Sorry, not sure what you're asking here. All the Docker sites are updating fine. Just the sites based on the pangolin-cli are having issues. And I did a complete uninstall and reinstall when I moved from newt to cli on all these servers.

~~Just to be clear, I'm using the Pangolin hosted under a plan. Maybe I should just work with you via a support channel?~~

~~Ahh okay. Yes please reach out to support@pangolin.net and reference this issue. I am going to close this here now but we will get this resolved. /close~~

~~The conversion of newt to CLI is interesting, as Im facing issues of sites not auto updating either; and all of my cli sites were previously newt sites.~~

However, I do believe I had these sites auto update previously before maybe 0.19?

What logs would you like for this? Cli or pangolin container logs?

Edit: Im self hosted

I'm getting the same error in systemctl for cli Auto-update check failed: server returned status 500: {"data":null,"success":false,"error":true,"message":"Unable to determine latest Newt version","status":500,"stack":null}

~~I suspect you might see it failing to contact GitHub in the Pangolin server container logs because of rate limits. Is this correct?~~

~~Checking the pangolin.log file and docker logs pangolin shows nothing for rate limits or anything with the word github.~~

The only error I'm seeing in there is 2026-11-10T11:47:57+11:00 [�[31merror�[39m]: Unhandled Rejection: {"reason":{"errno":-13,"code":"EACCES","syscall":"mkdir","path":"/app/.next/cache"}} which is now something else I need to work out

Edit: Which I think is because I'm running the pangolin container as a user, and not root (oops, but didn't realise there was an issue. I'm sure this is new). Regardless, this is an alternate issue

Update the cli based on the cli version

Upon further investigation, it appears that the system is operating as expected, though the current behavior has been causing confusion. Currently, the CLI only auto-updates when the embedded Newt version is updated. Because the latest release did not include a Newt version update, it did not trigger an auto-update. Users typically expect the site to update whenever a new release is published. We have updated the logic so that the site will now update whenever either a CLI or Newt release is published, depending on which one is running. This change will be included in the next release. Additionally, the cloud platform will update today, which will trigger the pending updates.

~~So will I need to manually update all instances of cli to 0.22.0 when the next release comes out, or will there be an updated newt at the same time to allow these to auto update?~~

~~The next time you update the server or we push a CLI update that requires an update they will update.~~

Navigation Menu

Repository navigation

Automatic Site Updates #179

Describe the Bug

Environment

To Reproduce

AI Disclosure

Expected Behavior

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Automatic Site Updates #179

Description

Describe the Bug

Environment

To Reproduce

AI Disclosure

Expected Behavior

Activity

oschwartz10612 commented on Nov 9, 2026

Stunt0265 commented on Nov 9, 2026

Stunt0265 commented on Nov 9, 2026

oschwartz10612 commented on Nov 9, 2026

Stunt0265 commented on Nov 9, 2026

Stunt0265 commented on Nov 9, 2026

oschwartz10612 commented on Nov 9, 2026

Vyerni commented on Nov 10, 2026

oschwartz10612 commented on Nov 10, 2026

Vyerni commented on Nov 10, 2026

oschwartz10612 commented on Nov 10, 2026

Vyerni commented on Nov 11, 2026

oschwartz10612 commented on Nov 11, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions