Home Assistant Studio Code Server Not Working? A Guide

Home Assistant Studio Code Server not working usually means either the add-on is unhealthy or the access path is failing. Check the add-on state, Home Assistant host, local connection, reverse proxy, certificate, port, and network path before restoring a backup or resetting the installation.

First, identify what is actually failing

Start by separating a stopped or restarting add-on from an interface that is running but unreachable. Check whether Home Assistant itself remains accessible and whether automations continue running. If they do, the problem may be limited to Studio Code Server or its access path.

A fault domain is the part of a system where the failure is likely occurring. For Studio Code Server, the relevant layers are add-on state, the Home Assistant host, the reverse proxy, the certificate, the port, and the local network path.

Observed symptom	Likely layer	First useful check
Add-on is stopped or repeatedly restarting	Add-on state or Supervisor	Check the add-on state and read the add-on and Supervisor logs
Several add-ons are unavailable after a restore	Home Assistant host or restored add-on state	Check whether Home Assistant restarted successfully, then consider the host state
Local access works but a proxied URL fails	Reverse proxy	Compare proxy forwarding, hostname, certificate, and path behavior
A blank page appears after adding a client certificate	Certificate, browser, or frontend access path	Test the original internal path without the recently added certificate rule
Sidebar works but a direct port connection fails	Port exposure or access path	Check the current add-on documentation and configuration for the supported access method and port
One device cannot connect while another can	Local network path or client	Compare trusted Wi-Fi, guest Wi-Fi, VPN, browser, and device settings

Record whether Studio Code Server is stopped, stuck starting, blank, or reachable only through one path. That distinction narrows the next check. Readers working on a broader self-hosted environment can use these home-lab server ideas for context, but do not change the network layout before identifying the failing layer.

Check the add-on and host state after a restart or restore

Restarting Home Assistant restarts the Home Assistant application and related services. Restarting the host reboots the underlying computer or appliance. They are different actions, and a host restart should not be treated as the automatic answer to every Studio Code Server failure.

Use the least-disruptive order

Confirm that Home Assistant loads and check whether automations and other add-ons remain available.
Open the Studio Code Server add-on page and check whether it is running, stopped, starting, or repeatedly restarting.
Restart the add-on once and wait for its state and logs to settle.
Restart Home Assistant if the add-on state appears stale or several Home Assistant services are affected.
Check the host state and consider a host restart only when add-ons remain unavailable or the broader host state justifies it.
Test local access before changing certificates, proxy rules, or installation settings.

Home Assistant Community users reported that a backup restore left add-ons including File Editor and Studio Code Server unable to load. In one discussion, a host restart was reported as helpful when add-ons did not run after the restore. That report does not prove that a host restart fixes every installation.

Do not infer a specific cause from the restore alone. Treat the unavailable add-on as evidence to check the add-on state, host state, and logs before considering a wider recovery action.

Read the add-on and Supervisor logs

The logs help distinguish a service that did not start from a service that started but cannot be reached through a particular path. A startup line identifying a listening address is evidence that code-server reached a listening state in that installation. A watchdog restart indicates that the Supervisor considered the add-on unhealthy at that point.

One reported Studio Code Server log included code-server listening on http://0.0.0.0:1337/. The same report said authentication was disabled and HTTPS was not being served. Treat those lines as evidence from that reported installation, not as universal behavior for current add-on versions.

0.0.0.0 indicates that the service was listening on available host interfaces in that report. It does not by itself prove that port 1337 is exposed to your network, reachable through a firewall, or intended to be used directly from another device.

A Supervisor message saying the watchdog found Studio Code Server unhealthy and restarted it means the add-on failed a health check at that time. One message may describe a single recovery attempt; repeated watchdog messages show that the health problem is continuing and should be recorded before making several changes.

Record evidence before changing several settings

The Home Assistant release and Studio Code Server add-on version, if shown in the interface.
The exact add-on state: stopped, starting, running, or restarting.
The time of the failure and whether it followed a restore, update, certificate change, or host reboot.
The complete startup and Supervisor lines around the failure.
Whether the sidebar, original internal path, and proxied URL behave differently.
The device, browser, Wi-Fi network, VPN state, and certificate used during the test.

Change one narrow setting at a time and retain the original log evidence. Changing the add-on, proxy, certificate, and firewall together removes the comparison that makes troubleshooting useful.

Test local access before blaming the reverse proxy

Local access is the control test. If Studio Code Server works through the Home Assistant sidebar or original internal path but fails through a proxied URL, investigate the reverse proxy before reinstalling the add-on.

A reverse proxy receives a browser request and forwards it to an internal service. Home Assistant users may place IIS or another proxy in front of Studio Code Server so that a hostname, certificate, or access policy handles the request.

Compare three paths

Home Assistant sidebar: Open Studio Code Server from the Home Assistant interface. A working sidebar launch indicates that this integrated route is responding.
Internal or original path: Test the address used inside the local network, without adding a new proxy or client certificate.
Proxied URL: Test the hostname or URL served by IIS or another reverse proxy after the local path is known to work.

A reported IIS case involved IIS not setting X-FORWARDED-HOST. X-FORWARDED-HOST is an HTTP header that tells the upstream service which host the client originally requested. That detail may matter in a particular IIS configuration, but the reported workaround should not be applied to every reverse proxy or Home Assistant deployment.

If the sidebar and internal path work while the proxied URL fails, compare the proxy’s forwarded-host handling, certificate rules, and path behavior. If the internal path also fails, move back to the add-on, host, port, or local-network checks.

Check certificates, port access, and the browser path

A blank page after adding a client certificate suggests that the browser, certificate, proxy, or frontend path needs investigation when the original internal address still works. A failed connection to port 1337 needs separate testing because a sidebar route and a directly exposed host port are not necessarily the same access method.

A client certificate is a certificate presented by the client device to help a server authenticate that device or browser. In one reported case, adding a client certificate produced a blank page, while connecting internally through the original port without the client certificate worked.

Test a private browser window, another browser, or another device to see whether the blank page follows the certificate or the browser session. Change only the recently added certificate rule in the test path, and do not weaken security controls across the installation merely to make one page load.

Port 1337 appeared in a reported code-server listening message, and another user reported that the add-on worked from the sidebar but could not be reached on port 1337. That user also could not see a port setting in the add-on panel. These reports show why the visible port, integrated sidebar route, and current add-on configuration must be checked together.

Open the current Studio Code Server add-on documentation and configuration for your installation. Check the documented access method, any Network or Ports section, the configured protocol and address, and whether port 1337 is listed for your version. If no port setting is shown, do not treat that absence as proof that the add-on failed to start. Check the add-on logs and use the access method documented for the current installation.

Test any documented port from the same local network as the Home Assistant host, then from the device that fails. Check the address, protocol, firewall or router rules, and whether the service is actually listening. If Home Assistant loads but Studio Code Server alone is blank, treat the issue as an access-path problem until the add-on logs show otherwise.

Rule out a local network or client problem

A guest Wi-Fi connection can make Home Assistant appear inaccessible because guest isolation may block devices from reaching local hosts. Test from another device or a trusted local network before changing the Home Assistant installation.

One reported access problem was caused by a phone connecting to guest Wi-Fi while the user initially believed the Home Assistant system was unavailable. That reported case shows why the client network must be checked separately from the host and add-on.

Use a controlled comparison

Test from a device on the same trusted Wi-Fi or wired LAN as the Home Assistant host.
Test the same URL from a second device to separate client problems from service problems.
Check whether a VPN, private DNS setting, browser extension, or captive portal changes the result.
Compare the Home Assistant dashboard and Studio Code Server from the same device and network.
Do not assume that access to one Home Assistant system proves access to another system on the same broader home-lab setup.

A local network path is the route between the client and the host, including Wi-Fi association, guest isolation, routing, and firewall policy. A failure in that path can look like a stopped add-on, especially when the browser shows only a timeout. The broader self-hosted network context may help when separating host, network, and service roles.

Home Assistant Studio Code Server Not Working: Use the Decision Tree

Use this sequence to choose the narrowest next test:

If the add-on is stopped or repeatedly restarting: read the Studio Code Server and Supervisor logs, restart the add-on once, and record whether the state stabilizes. If the watchdog keeps restarting it, investigate the continuing health failure before testing proxy or certificate changes.
If the sidebar works but a direct or original path fails: compare the documented access method and current add-on configuration. Do not assume that port 1337 is a required direct-access port for the current installation.
If the internal path fails too: return to the add-on state, host state, logs, and trusted local-network test. A proxy change is not the first response when the internal path is also unavailable.
If only the proxied URL fails: compare the proxy’s forwarding and hostname behavior with the working local path. In the reported IIS case, missing X-FORWARDED-HOST was relevant to that configuration, not a universal reverse-proxy fix.
If the failure began after adding a client certificate: test the original internal path without that certificate path, using another browser or device where possible. A reported blank-page case worked internally without the client certificate.
If only a guest-network device fails: test from trusted Wi-Fi or a wired LAN and from a second device before changing Home Assistant. A reported phone-access problem was caused by guest Wi-Fi.
If several add-ons became unavailable after a restore: check Home Assistant and host state, collect logs, and consider a host restart only as a broader troubleshooting step. A restore or factory reset is a last resort, not the first response to a blank page or failed browser connection.

When asking for further support, include the exact symptom, Home Assistant and add-on versions, whether the issue followed a restore, the access path used, the client network, and the relevant add-on and Supervisor log lines. State whether the sidebar works, whether the documented port is reachable in your installation, and whether a watchdog is restarting the add-on.

Keep the original backup and configuration evidence until the issue is resolved. For readers planning the surrounding self-hosted setup, the home-lab layout guide provides relevant context, but a restore or factory reset should remain a documented recovery decision rather than the first troubleshooting step.

Frequently asked questions

Why is Home Assistant Studio Code Server not starting?

Check the add-on state and both the Studio Code Server and Supervisor logs first. A stopped add-on or repeated watchdog restarts points toward an add-on, Supervisor, or host problem. If the add-on appears to run but the browser is blank, compare the sidebar, internal path, proxy, certificate, port, and network path.

What is the difference between restarting Home Assistant and restarting the host?

Restarting Home Assistant restarts the Home Assistant application and related services. Restarting the host reboots the underlying computer or appliance, so it is a broader action that should follow narrower add-on, application, host, and log checks.

Why does Studio Code Server show a blank page behind a reverse proxy?

Compare the working internal path with the proxied URL and check proxy forwarding, hostname handling, certificate rules, and browser state. A reported IIS case involved IIS not setting X-FORWARDED-HOST, but that detail is not a universal fix for every reverse proxy.

Why can I access Home Assistant but not Studio Code Server?

Home Assistant and Studio Code Server can use different routes, ports, certificates, or proxy rules. Check whether the add-on is running, read its logs, and compare the sidebar, original internal path, and proxied URL from a trusted network.

Can a backup restore affect Studio Code Server and File Editor?

Home Assistant Community users reported that both add-ons became unavailable after a backup restore. In one discussion, a host restart was reported as helpful, but that report does not guarantee that a host restart will fix every restored installation.

Last updated: 02 November 2026