Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

code-server -r filename results 'error Unexpected status code: 500'

Open
#6,977 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
cli

Research direction

Start by reproducing code-server -r ... with an existing workspace and collect the verbose logs requested in the issue. Done means the specified file opens in an existing window reliably and no Unexpected status code: 500 occurs after the session has been running.

Written by the indexing model from the issue text.

Description

bug triage
Is there an existing issue for this?
  • I have searched the existing issues
OS/Web Information
  • Web Browser: Chrome
  • Local OS: Debian testing
  • Remote OS: Debian testing
  • Remote Architecture: amd64
  • code-server --version: 4.92.2 de65bfc9477f61bc22d0b1a23085d1f18bb25202 with Code 1.92.2
Steps to Reproduce
  1. Open code-server
  2. Open an existing workspace
  3. Open a file from CLI (code-server -r ...)
Expected

code-server opens the specified file in one of the open windows.

Actual

Some cases it works, mostly with fresh sessions, then after a while it breaks and I get only a error Unexpected status code: 500. I just realised that restarting the code-server instance and reloading the client window fixes the problem.

Logs
As an intermittent issue I need to work a bit on the logs, I set verbose now.
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

Dominant language
TypeScript
Stars
79.4k
Forks
6.9k
Avg merge
2d 13h
Merged PRs (30d)
39

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from coder/code-server

All issues in coder/code-server

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.