Repository navigation
4.97.2 Broke Code-Server on all 12 of the boxes I run it on #7211
Copy link
Copy link
Closed
Labels
bugSomething isn't workingSomething isn't workingtriageThis issue needs to be triaged by a maintainerThis issue needs to be triaged by a maintainer
Description
Is there an existing issue for this?
- I have searched the existing issues
OS/Web Information
- Web Browser: Edge, Tried Firefox and Safari as well
- Local OS: MacOS - Tried Windows as well
- Remote OS: Ubuntu 22.04
- Remote Architecture: x64
code-server --version: 4.97.2 34b8d2e with Code 1.97.2
Steps to Reproduce
All I did was update the 12 ubuntu boxes I have running code-server using the code-server_4.97.2_amd64.deb file from the releases page.
Expected
Code-Server should load normally
Actual
After the update, I get a white screen whenever I visit my code-server site. If I visit in a new browser or incognito, it asks me for my password, then displays the white screen. - I've tried reinstalling 4.97.2, downgrading to 4.96.4 (which worked previously), but nothing fixes it. It is affecting all 12 of the servers I have code-server running on.
The devtools console error that pops up is:
Uncaught TypeError: Cannot read properties of undefined (reading 'bind') at uuid.ts:13:61
Logs
February 19, 2025 4:29 AM }
4:29 AM options: { preferUnbuffered: true }
4:29 AM fileOperationResult: 1,
4:29 AM at async s9.s (file:///usr/lib/code-server/lib/vscode/out/server-main.js:55:7847) {
4:29 AM at async s9.H (file:///usr/lib/code-server/lib/vscode/out/server-main.js:55:9952)
4:29 AM at async Bh.scanAllUserExtensions (file:///usr/lib/code-server/lib/vscode/out/server-main.js:55:20151)
4:29 AM at async cl.scanAllUserExtensions (file:///usr/lib/code-server/lib/vscode/out/server-main.js:54:28887)
4:29 AM at async Jc.r (file:///usr/lib/code-server/lib/vscode/out/server-main.js:54:35943)
4:29 AM at async Promise.all (index 14)
4:29 AM at async Jc.scanExtension (file:///usr/lib/code-server/lib/vscode/out/server-main.js:54:37518)
4:29 AM at async Jc.u (file:///usr/lib/code-server/lib/vscode/out/server-main.js:54:38920)
4:29 AM at async Kc.C (file:///usr/lib/code-server/lib/vscode/out/server-main.js:64:12129)
4:29 AM at Kc.D (file:///usr/lib/code-server/lib/vscode/out/server-main.js:64:12757)
4:29 AM at Kc.F (file:///usr/lib/code-server/lib/vscode/out/server-main.js:64:12932)
4:29 AM [04:29:11] Yt [Error]: Unable to read file '/root/.local/share/code-server/extensions/icons/package.json' (Error: Unable to resolve nonexistent file '/root/.local/share/code-server/extensions/icons/package.json')
4:29 AM }
4:29 AM options: { preferUnbuffered: true }
4:29 AM fileOperationResult: 1,
4:29 AM at async Xc.cleanUp (file:///usr/lib/code-server/lib/vscode/out/server-main.js:55:14114) {
4:29 AM at async Bh.cleanUp (file:///usr/lib/code-server/lib/vscode/out/server-main.js:55:19595)
4:29 AM at async Bh.I (file:///usr/lib/code-server/lib/vscode/out/server-main.js:55:25996)
4:29 AM at async cl.scanAllUserExtensions (file:///usr/lib/code-server/lib/vscode/out/server-main.js:54:28887)
4:29 AM at async Jc.r (file:///usr/lib/code-server/lib/vscode/out/server-main.js:54:35943)
4:29 AM at async Promise.all (index 14)
4:29 AM at async Jc.scanExtension (file:///usr/lib/code-server/lib/vscode/out/server-main.js:54:37518)
4:29 AM at async Jc.u (file:///usr/lib/code-server/lib/vscode/out/server-main.js:54:38920)
4:29 AM at async Kc.C (file:///usr/lib/code-server/lib/vscode/out/server-main.js:64:12129)
4:29 AM at Kc.D (file:///usr/lib/code-server/lib/vscode/out/server-main.js:64:12757)
4:29 AM at Kc.F (file:///usr/lib/code-server/lib/vscode/out/server-main.js:64:12932)
4:29 AM [04:29:11] Yt [Error]: Unable to read file '/root/.local/share/code-server/extensions/icons/package.json' (Error: Unable to resolve nonexistent file '/root/.local/share/code-server/extensions/icons/package.json')
4:29 AM[04:29:11] Extension host agent started.
February 18, 2025
8:37 PM[2025-02-19T01:37:46.322Z] info Session server listening on /root/.local/share/code-server/code-server-ipc.sock
8:37 PM [2025-02-19T01:37:46.322Z] info - Not serving HTTPS
8:37 PM [2025-02-19T01:37:46.322Z] info - Using password from /root/.config/code-server/config.yaml
8:37 PM [2025-02-19T01:37:46.322Z] info - Authentication is enabled
8:37 PM [2025-02-19T01:37:46.322Z] info HTTP server listening on http://0.0.0.0:8087/
8:37 PM [2025-02-19T01:37:46.322Z] info Using config file /root/.config/code-server/config.yaml
8:37 PM [2025-02-19T01:37:46.314Z] info Using user-data-dir /root/.local/share/code-server
8:37 PM [2025-02-19T01:37:46.314Z] info code-server 4.97.2 34b8d2ed69811c3315a465f01492e9448c9254aa
8:37 PM Started code-server@root.service - code-server.
8:37 PM Starting code-server@root.service - code-server...
8:37 PM @root.service: Consumed 2.353s CPU time, 98.4M memory peak, 0B memory swap peak.
8:37 PM Stopped code-server@root.service - code-server.
8:37 PM @root.service: Deactivated successfully.
8:37 PM Stopping code-server@root.service - code-server...Screenshot/Video
No response
Does this bug reproduce in native VS Code?
I did not test native VS Code
Does this bug reproduce in GitHub Codespaces?
I did not test GitHub Codespaces
Are you accessing code-server over a secure context?
- I am using a secure context.
Notes
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingtriageThis issue needs to be triaged by a maintainerThis issue needs to be triaged by a maintainer
Activity
vcantrell commentedon Feb 19, 2025
It was because I was accessing them by IP and not through cloudflared (to save time of trafficking through CF...) but apparently insecure connections are now just not supported.
rover5056 commentedon Feb 20, 2025
Same issue,so accessing them by IP would never allowed for future version?
@vcantrell
vcantrell commentedon Feb 20, 2025
I assume it just needs a secure context... so for me I use cloudflared, but you could just use a self-signed cert.
What blows my mind, though, is that downgrading doesn't seem to fix the issue. Not sure what the change was that caused insecure contexts to just break... but a warning would have been nice 🤷🏻♂️
code-asher commentedon Feb 20, 2025
Looks like a regression in VS Code (see #7212 (comment)) but it seems they are planning on fixing it.