Visual Studio Code - can't start the addon - help with debug

Same problem

and here.
The problem started with the update to core 2022.11.1
BTW uninstaling the addon and reinstalling doesn’t help either.

1 Like

Having the same issues. Updated everything, problem persists. Anyone have a fix?

Yep, used to work fine and now i moved to SSD from SD with migration. Getting the same logs. Any solutions yet?

OK, thinking of “What would an IT guy say?” I decided to unplug my raspberry pi, count to 10 and put it back. Guess what, it started working again :smiley:

1 Like

I had this problem too after restoring a Home Assistant core backup to fix a different problem. I found that I could not start File Editor either, so I am wondering if something in the file system is corrupted?

See my own posting

I can’t get either File editor or VS Code Server running. Clicking START does nothing.
On 2023.2.4. Both used to work well.

Same:

[2023-03-09T10:49:00.809Z] info Using user-data-dir /data/vscode
[2023-03-09T10:49:00.824Z] info Using config file ~/.config/code-server/config.yaml
[2023-03-09T10:49:00.824Z] info HTTP server listening on http://0.0.0.0:1337/
[2023-03-09T10:49:00.824Z] info - Authentication is disabled
[2023-03-09T10:49:00.825Z] info - Not serving HTTPS
[13:49:06]
[13:49:06] Extension host agent started.
[2023-03-09T10:49:07.299Z] error Forbidden HttpError: Forbidden
at ensureOrigin (/usr/local/lib/code-server/out/node/http.js:288:15)
at wrapped (/usr/local/lib/code-server/out/node/wsRouter.js:64:24)

Exactly the same scenario…migrated to RPI4 and went to ssd from sd card. Studio server won’t start.

1 Like

Same - hasn’t anyone got a fix? Developers?

This exact same issue is happening to me after a power outage at home and the Home Assistant server going down. Now I cannot start the add-on and it’s critical.
Any idea how to fix this?
Thanks in advance.

Same here. It was working this morning, no reboot or power outage and suddenly the add-on stopped and I can’t get it to start again.

add-on log
 Add-on: Studio Code Server
 Fully featured Visual Studio Code (VSCode) experience integrated in the Home Assistant frontend.
-----------------------------------------------------------
 Add-on version: 5.8.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 10.3  (amd64 / generic-x86-64)
 Home Assistant Core: 2023.6.3
 Home Assistant Supervisor: 2023.06.4
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-timezone: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
[12:00:51] INFO: Configuring timezone (Australia/Perth)...
Log level is set to INFO
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service base-addon-timezone successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-user: starting
s6-rc: info: service init-mysql: starting
s6-rc: info: service init-mosquitto: starting
s6-rc: info: service init-code-server: starting
s6-rc: info: service init-code-server successfully started
total 28
drwxr-xr-x 5 root root 4096 Jun 30 12:00 .
drwxr-xr-x 5 root root 4096 Jun 30 12:00 ..
drwxr-xr-x 3 root root 4096 Jun 30 12:00 data
drwx-ws--T 2 root root 4096 Jun 30 12:00 event
-rw-r--r-- 1 root root    2 Jun 30 12:00 notification-fd
-rwxr-xr-x 1 root root  419 Jun 30 12:00 run
srwxrwxrwx 1 root root    0 Jun 30 12:00 s
-rw------- 1 root root    0 Jun 30 12:00 s.lock
drwx------ 2 root root 4096 Jun 30 12:00 supervise
s6-rc: info: service init-user successfully started
s6-rc: info: service code-server: starting
s6-rc: info: service code-server successfully started
[12:00:53] INFO: Starting code-server...
s6-rc: info: service init-mosquitto successfully started
s6-rc: info: service init-mysql successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[2023-06-30T04:00:54.182Z] info  Wrote default config file to ~/.config/code-server/config.yaml
[2023-06-30T04:00:54.973Z] info  code-server 4.14.1 5c199629305a0b935b4388b7db549f77eae82b5a
[2023-06-30T04:00:54.974Z] info  Using user-data-dir /data/vscode
[2023-06-30T04:00:54.995Z] info  Using config file ~/.config/code-server/config.yaml
[2023-06-30T04:00:54.995Z] info  HTTP server listening on http://0.0.0.0:1337/
[2023-06-30T04:00:54.996Z] info    - Authentication is disabled
[2023-06-30T04:00:54.996Z] info    - Not serving HTTPS
[2023-06-30T04:00:54.996Z] info  Session server listening on /data/vscode/code-server-ipc.sock
Supervisor log
23-06-30 11:47:56 WARNING (MainThread) [supervisor.addons.addon] Watchdog found addon Studio Code Server is unhealthy, restarting...
23-06-30 11:47:56 INFO (SyncWorker_0) [supervisor.docker.interface] Stopping addon_a0d7b954_vscode application
23-06-30 11:48:00 INFO (SyncWorker_0) [supervisor.docker.interface] Cleaning addon_a0d7b954_vscode application
23-06-30 11:48:01 INFO (SyncWorker_9) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/vscode/amd64 with version 5.8.0
23-06-30 11:48:11 WARNING (MainThread) [supervisor.addons.addon] a0d7b954_vscode is already running!

EDIT: after multiple attempts to restart it seems to be ok… will see if it stays this way.

1 Like

same here

s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-timezone: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
[15:26:05] INFO: Configuring timezone (America/Santiago)…
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service base-addon-timezone successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-user: starting
s6-rc: info: service init-mysql: starting
s6-rc: info: service init-mosquitto: starting
s6-rc: info: service init-code-server: starting
s6-rc: info: service init-code-server successfully started
s6-rc: info: service init-mysql successfully started
s6-rc: info: service init-user successfully started
s6-rc: info: service code-server: starting
s6-rc: info: service code-server successfully started
[15:26:06] INFO: Starting code-server…
s6-rc: info: service init-mosquitto successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[2023-06-30T19:26:06.723Z] info Wrote default config file to ~/.config/code-server/config.yaml
[2023-06-30T19:26:07.052Z] info code-server 4.14.1 5c199629305a0b935b4388b7db549f77eae82b5a
[2023-06-30T19:26:07.053Z] info Using user-data-dir /data/vscode
[2023-06-30T19:26:07.063Z] info Using config file ~/.config/code-server/config.yaml
[2023-06-30T19:26:07.064Z] info HTTP server listening on http://0.0.0.0:1337/
[2023-06-30T19:26:07.064Z] info - Authentication is disabled
[2023-06-30T19:26:07.064Z] info - Not serving HTTPS
[2023-06-30T19:26:07.064Z] info Session server listening on /data/vscode/code-server-ipc.sock

1 Like

Same problem here.

1 Like

No one found the cause? Mine wasn’t able to start even after restoring from backup

Mine has also just sopped working. I reinstalled it and reboot/restart cant get it to work. Why, whats wrong?

Same here. VS Code Server stopped working, no entries in HA log files, no helpful entries in addon log. Any idea, what happened?

Also here just started to happen,
Do you guys also have Mosquitto broker, Does it function properly?

This is odd, mine was working an hour ago, suddenly stopped and can’t get it back.
Even rebooted HA

Same problem here since yesterday. Seems to be a widespread problem.

What is the most helpful way to report such a problem?

Thanks in advance to anyone working to resolve the problem.