upgrade to prelease version 4.0.0 fails with vscode.html not found
See original GitHub issueOS/Web Information
- Web Browser: Firefox 95.0
- Local OS: Mac OS Monterey 12.1
- Remote OS: Ubuntu 20.04.3
- Remote Architecture: amd64
code-server --version
: 4.0.0
Steps to Reproduce
- downloading deb pkg from https://github.com/cdr/code-server/releases/download/v4.0.0/code-server_4.0.0_amd64.deb
- upgrading from 3.12.0 to 4.0.0 by issuing:
dpkg -i code-server_4.0.0_amd64.deb
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'code-server' instead of '/tmp/code-server_4.0.0_amd64.deb'
The following packages will be upgraded:
code-server
1 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
Need to get 0 B/221 MB of archives.
After this operation, 246 MB of additional disk space will be used.
Get:1 /tmp/code-server_4.0.0_amd64.deb code-server amd64 4.0.0 [221 MB]
(Reading database ... 88122 files and directories currently installed.)
Preparing to unpack .../code-server_4.0.0_amd64.deb ...
Unpacking code-server (4.0.0) over (3.12.0) ...
Setting up code-server (4.0.0) ...
Expected
To work as normally, just like on 3.12.0
Actual
when accessing code-server over the web: I get:
ENOENT: no such file or directory, open '/usr/lib/code-server/src/browser/pages/vscode.html'
These are the only files that I can see here:
ls /usr/lib/code-server/src/browser/pages
error.css error.html global.css login.css login.html
Logs
Once this is done, replicate the issue you’re having then collect logging information from the following places:
1. The most recent files from ~/.local/share/code-server/coder-logs.
Unfortunately there’s no output in the log files, despite running the process with --log debug
as seen in ps aux:
/usr/lib/code-server/lib/node /usr/lib/code-server --log debug
~/.local/share/code-server/coder-logs# tail -f *
==> code-server-stderr.log <==
==> code-server-stdout.log <==
2. The browser console.
Most probably irrelevant, but:
Layout was forced before the page was fully loaded. If stylesheets are not yet loaded this may cause a flash of unstyled content.
3. The browser network tab.
Just the 404 not found error.
Screenshot

Looking forward to any suggestions 😃
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Visual Studio Code Frequently Asked Questions
How do I opt out of VS Code auto-updates? Licensing; Are all VS Code extensions open source? How do I find the version?...
Read more >Troubleshoot Terminal launch failures - Visual Studio Code
Troubleshoot Visual Studio Code Integrated Terminal launch failures. ... To find the latest version of VS Code, go to the VS Code release...
Read more >April 2022 (version 1.67) - Visual Studio Code
Update 1.67.1: The update addresses this security issue. ... Note: The setting is not entirely new and has been available in VS Code...
Read more >May 2022 (version 1.68) - Visual Studio Code
Welcome to the May 2022 release of Visual Studio Code. There are many updates in this version that we hope you'll like, some...
Read more >October 2022 - Visual Studio Code
There are many updates in this version that we hope you'll like, ... or failed, Terminal Quick Fix available. vscode.dev protected branch workflow...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The AUR package should auto restart via sysd (but it doesnt). Just FYI.
@code-asher Sorry, I’m dumb. I hadn’t actually, I thought I did. So the error must have come from the fact that the previous version was still trying to access the what is now removed vscode.html - what you were probably inferring 😃 After restarting, it seems to be working correctly.