PeaNUT update failed #3937
Replies: 8 comments 8 replies
-
Please try again after clearing the browser cache. 128b076 |
Beta Was this translation helpful? Give feedback.
-
Updating (or re-installing) to 3.0.0 is resulting in an Internal Server Error. The developer is saying a settings.yml is created on first launch, but that doesn't seem to be happening with the lxc |
Beta Was this translation helpful? Give feedback.
-
Temporally removed PeaNUT from the website. |
Beta Was this translation helpful? Give feedback.
-
It tries to open the file that doesn't exist
|
Beta Was this translation helpful? Give feedback.
-
Was able to test this. PR to fix it has been submitted |
Beta Was this translation helpful? Give feedback.
-
Seems to be working now. Also, PeaNUT has updated to 3.1.0, and there is now an option to set the server host from the web interface once the internal server error is detected. |
Beta Was this translation helpful? Give feedback.
-
I tried updating to 3.1.1 and am getting an internal server error as well. Same error as previous user when I run systemctl status peanut. Oct 22 17:32:34 peanut peanut[2067]: errno: -2, |
Beta Was this translation helpful? Give feedback.
-
Confirmed able to update from 3.1.1 to 3.1.2 with update script. setting.yml either persisted, or correctly re-created. Either way, it's working. Thanks all! |
Beta Was this translation helpful? Give feedback.
-
Updating (with
update
) PeaNUT to v2.6.1 fails with the error:[ERROR] in line 68: exit code 0: while executing command pnpm run build &> /dev/null
Beta Was this translation helpful? Give feedback.
All reactions