My control panel was hitting me with an error 500, so I went through and did some updates. Seems to be working now, but the CSS and JS files in the control panel are all coming back with error 404.
https://x.x.x.x:8083/css/themes/default.min.css?v=1.9.3
https://x.x.x.x:8083/css/themes/custom/dark.css?v=1.9.3
https://x.x.x.x:8083/js/dist/main.min.js?v=1.9.3
https://x.x.x.x:8083/js/dist/alpinejs-collapse.min.js?v=1.9.3
https://x.x.x.x:8083/js/dist/alpinejs.min.js?v=1.9.3
Any help?
How did you upgrade?
And what was the old version if it was 1.7.x or before
run
v-update-sys-hestia-git hestiacp main
Again
It updated automatically to 1.9.0 and went to error 500 on the control panel. I believe this may have failed due to expired sury keys.
Before I realised this I followed this advice I found elsewhere and ran “v-update-sys-hestia-git hestiacp main” but it failed when searching for bubblewrap.
After I used curl to update the keys manually from, I ran apt update and then ran “apt install at bubblewrap” which unexpectedly triggered a hestia update.
This didn’t fix the 500 error anything so I ran “apt upgrade” to bring everything in line, took a while, but the control panel came back with no styling or js.
I noticed in the logs that the update release had switched to “main” which I figured was a bit dangerous, so I switched it back to “release” with “v-change-sys-release release”
Should I still update from the git main branch?
Seems to have sorted it.
It probally didn’t ran the build script we have implemented. That is why
v-update-sys-hestia-git hestiacp release
Will update to the. release branch…
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.