Docker update hangs when checking for new discourse version

Product Support Self-hosting

AI-generated summary

In the thread titled ‘Docker update hangs when checking for new discourse version’, downey reported that the upgrade check on their Discourse instance hangs indefinitely when checking the discourse repository, though it works for plugins. After checking the browser’s dev console, downey found a 502 error on the request to /admin/docker/latest, which triggered a JavaScript error in the Docker manager. zogstrip had asked about JavaScript errors, prompting the investigation. Eventually, downey noted that the issue resolved itself — the system was able to detect the latest version and proceed with the upgrade normally. No permanent fix or root cause was identified, suggesting a transient server or network issue.

1

When I load https://discourse.example.org/admin/upgrade, the upgrade check works for all plugins but hangs indefinitely on the discourse repository itself. Any ideas?

Pasted image610×518 54.4 KB

2

Are there any JavaScript errors in the dev console?

3

Why yes there is:

GET https://discourse.example.org/admin/docker/latest?path=%2Fvar%2Fwww%2Fdiscourse&version=1689f43&branch=origin%2Ftests-passed 502 (OK)
Error: OK
    at o (docker-manager-vendor-f00ab2e603ce2bef5677d6dc04bfa72a.js:11)
    at Object.e.default.trigger (docker-manager-vendor-f00ab2e603ce2bef5677d6dc04bfa72a.js:16)
    at h._onerror (docker-manager-vendor-f00ab2e603ce2bef5677d6dc04bfa72a.js:16)
    at d (docker-manager-vendor-f00ab2e603ce2bef5677d6dc04bfa72a.js:16)
    at docker-manager-vendor-f00ab2e603ce2bef5677d6dc04bfa72a.js:11
    at r.invoke (docker-manager-vendor-f00ab2e603ce2bef5677d6dc04bfa72a.js:4)
    at Object.r.flush (docker-manager-vendor-f00ab2e603ce2bef5677d6dc04bfa72a.js:4)
    at Object.n.flush (docker-manager-vendor-f00ab2e603ce2bef5677d6dc04bfa72a.js:4)
    at Object.a.end (docker-manager-vendor-f00ab2e603ce2bef5677d6dc04bfa72a.js:4)
    at Object.a.run (docker-manager-vendor-f00ab2e603ce2bef5677d6dc04bfa72a.js:4)
4

Whatever it was, it cleared itself up and was able to finally find out what the latest version was. Upgrade proceeded as normal.