-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
automatic update from 3.1.0 to 3.1.1 failed #1532
Comments
I'm getting the same error trying to update mine. |
Hmm, I've been trying to replicate using the steps in #1513 (comment) (except I used 3.1.0 instead of 3.0.2) but it always works for me so far. Do you see any output from code-server after applying the update? (If you're using systemd I imagine it'll be in the journal by default.) According to that other issue you installed code-server in |
thank you for the quick answer. My user is "gregoryweb" and my Home folder is "/var/www"
I install "code-server 3-1-0" with "gregoryweb" user (download version and unzip) in "code-server" folder :
here is the content of the folder "code-server-3.1.0-linux-x86_64":
I change the permissions to the code-server : chmod -R 777 ~/code-server the content of this file is :
special attention to the path of "ExecStart" = /var/www/code-server/code-server-3.1.0-linux-x86_64/code-server Finally I change the config in Nginx to make a reverse proxy:
@code-asher where is my mistake? |
Hi, thank you |
Ahhhh, |
I'm still having getting 'update failed'. Have |
Are you updating from 3.1.0 or a different version? |
I'm not sure. I'm using a docker build and in Help -> About it shows: Version: 1.43.2 |
In the Docker container code-server is installed in 3.0.2 has a bug where it'll say |
Can confirm ran |
See #1532 for more context. - Errored JSON requests will get back the error in JSON instead of using the status text. This seems better to me because it seems more correct to utilize the response body over hijacking the status text. The caller is expecting JSON anyway. Worst of all I never actually set the status text like I thought I did so it wasn't working to begin with. - Allow the update error to propagate for JSON update requests. It was caught to show the error inline instead of an error page when using the update page but for JSON requests it meant there was no error and no error code so it looked like it succeeded. - Make errors for failed requests to GitHub less incomprehensible. Previously they would just be the code which is no context at all.
Hello
After the "update to 3.1.1" message if I check my code-server version:
3.1.0 5aded14
if a restart the sytemctl service for code-server the version is the same (3.1.0) and I continue to receive the message "apply update to 3.1.1"
could you help me?
@code-asher
Thank you
The text was updated successfully, but these errors were encountered: