Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Missing files issue in code-server after a clean installation #7046

Closed Unanswered
LeandroGFC asked this question in Q&A
Discussion options

Hello community,

I am experiencing a recurring problem with my code-server installation. It was previously working without issues, but at some point, when accessing it, the screen to enter the password appeared, and after logging in, it only showed a blank screen. Checking the service status, I found several errors indicating that certain essential .js files were missing. The errors are the following:

image

I installed code-server using the following commands:

VERSION=4.93.1
curl -fOL https://github.com/coder/code-server/releases/download/v$VERSION/code-server_${VERSION}_amd64.deb
sudo apt install ./code-server_${VERSION}_amd64.deb -y

I have already tried several things without success, including:

  • Performing a clean installation of code-server.
  • Verifying the permissions of the folders.
  • Ensuring that all dependencies are correctly installed.

My current setup includes code-server installed in /usr/lib/code-server. However, it still cannot find these files after installation.

Actions already taken:

  1. Clean installation of code-server.
  2. Verified permissions (chown and chmod on the corresponding paths).
  3. Checked paths in the configuration file (~/.config/code-server/config.yaml).

Questions:

  1. Could it be an issue with incorrect paths in some additional configuration?
  2. Is there a specific way to reinstall code-server to avoid missing files?
  3. Has anyone faced a similar problem and has any recommendations?

Any suggestions or help would be greatly appreciated.

Thanks in advance!

You must be logged in to vote

Replies: 1 comment

Comment options

Looks like a case of #2407, which probably needs to be fixed upstream. It seems that if the main workbench file takes too long to load, it falls back to trying to load development files, which obviously will not exist.

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet

AltStyle によって変換されたページ (->オリジナル) /