#i can't access casaOS anymore after update

9 messages · Page 1 of 1 (latest)

restive vigil Apr 27, 2025, 2:49 PM

Hello folks,

after a update i can't access casaOS anymore with 192.168.178.xx:xx like set. i did remove casaos, install casaos, installed a older version.

updatet my firewall, did many things, but nothing works.

when i'm opening the log of the gateway i'm getting this error :

2025-04-27T16:37:44.917+0200    error   Failed to load routes   {"error": "open /var/run/casaos/routes.json: no such file or directory", "filepath": "/var/run/casaos/routes.json", "func": "service.NewManagementSer>
2025-04-27T16:37:44.917+0200    info    Management service is listening...      {"address": "127.0.0.1:35229", "filepath": "/var/run/casaos/management.url", "func": "main.run.func1.1", "file": "/home/runner/work/C>
2025-04-27T16:37:44.917+0200    info    Checking if port is available...        {"port": "80", "func": "main.run.func2", "file": "/home/runner/work/CasaOS-Gateway/CasaOS-Gateway/main.go", "line": 251}
2025-04-27T16:37:44.917+0200    info    Checking if port is available...        {"port": "81", "func": "main.run.func2", "file": "/home/runner/work/CasaOS-Gateway/CasaOS-Gateway/main.go", "line": 251}
2025-04-27T16:37:44.917+0200    info    Checking if port is available...        {"port": "82", "func": "main.run.func2", "file": "/home/runner/work/CasaOS-Gateway/CasaOS-Gateway/main.go", "line": 251}
2025-04-27T16:37:44.932+0200    info    Checking if service at URL is running...        {"url": "http://[::]:82/ping", "retry": 10, "func": "main.checkURLWithRetry", "file": "/home/runner/work/CasaOS-Gateway/CasaO>
2025-04-27T16:37:44.933+0200    info    New gateway is listening...     {"address": "[::]:82", "func": "main.reloadGateway", "file": "/home/runner/work/CasaOS-Gateway/CasaOS-Gateway/main.go", "line": 358}
2025-04-27T16:37:44.933+0200    info    Notified systemd that gateway is ready  {"func": "main.main.func3", "file": "/home/runner/work/CasaOS-Gateway/CasaOS-Gateway/main.go", "line": 157}
2025-04-27T16:37:44.933+0200    info    Static web service is listening...      {"address": "127.0.0.1:33811", "filepath": "/var/run/casaos/static.url", "func": "main.run.func3", "file": "/home/runner/work/CasaOS->
2025-04-27T16:42:54.399+0200    info    A gateway is stopped    {"address": "[::]:82", "func": "main.reloadGateway.func1", "file": "/home/runner/work/CasaOS-Gateway/CasaOS-Gateway/main.go", "line": 345}
2025-04-27T16:42:54.988+0200    info    Management service is listening...      {"address": "127.0.0.1:43971", "filepath": "/var/run/casaos/management.url", "func": "main.run.func1.1", "file": "/home/runner/work/C>
2025-04-27T16:42:54.988+0200    info    Checking if service at URL is running...        {"url": "http://[::]:132/ping", "retry": 10, "func": "main.checkURLWithRetry", "file": "/home/runner/work/CasaOS-Gateway/Casa>
2025-04-27T16:42:54.989+0200    info    New gateway is listening...     {"address": "[::]:132", "func": "main.reloadGateway", "file": "/home/runner/work/CasaOS-Gateway/CasaOS-Gateway/main.go", "line": 358}
2025-04-27T16:42:54.989+0200    info    Notified systemd that gateway is ready  {"func": "main.main.func3", "file": "/home/runner/work/CasaOS-Gateway/CasaOS-Gateway/main.go", "line": 157}
2025-04-27T16:42:54.989+0200    info    Static web service is listening...      {"address": "127.0.0.1:43303", "filepath": "/var/run/casaos/static.url", "func": "main.run.func3", "file": "/home/runner/work/CasaOS->

anyone a idea ? in the app-management log i'm getting this errors to :

2025-04-27T16:37:56.487+0200    info    failed to parse compose app - contact the contributor of this app to fix it     {"error": "validating : services.jellyseerr.devices must be a list", "composeFile": "/var/lib>
2025-04-27T16:37:56.515+0200    info    failed to parse compose app - contact the contributor of this app to fix it     {"error": "validating : services.medusa.devices must be a list", "composeFile": "/var/lib/cas>
2025-04-27T16:37:56.679+0200    info    failed to parse compose app - contact the contributor of this app to fix it     {"error": "validating : services.trilium.devices must be a list", "composeFile": "/var/lib/ca>
2025-04-27T16:37:56.683+0200    info    failed to parse compose app - contact the contributor of this app to fix it     {"error": "validating : services.twingate-connector.volumes must be a list", "composeFile": ">
2025-04-27T16:37:56.719+0200    info    Notified systemd that casaos main service is ready      {"func": "main.main", "file": "/home/runner/work/CasaOS-AppManagement/CasaOS-AppManagement/main.go", "line": 172}
2025-04-27T16:37:56.719+0200    info    App management service is listening...  {"address": "127.0.0.1:45071", "func": "main.main", "file": "/home/runner/work/CasaOS-AppManagement/CasaOS-AppManagement/main.go", "l>
2025-04-27T16:37:56.818+0200    info    appstore size changed, update app store {"url": "https://casaos.app/store/main.zip", "func": "service.(*appStore).UpdateCatalog", "file": "/home/runner/work/CasaOS-AppManage>
2025-04-27T16:37:57.859+0200    info    appstore size changed, update app store {"url": "https://github.com/bigbeartechworld/big-bear-casaos/archive/refs/heads/master.zip", "func": "service.(*appStore).UpdateCatal>
2025-04-27T16:37:58.791+0200    info    failed to parse compose app - contact the contributor of this app to fix it     {"error": "validating : services.redis.healthcheck.retries must be a number", "composeFile": >
2025-04-27T16:47:56.087+0200    info    appstore size not changed       {"url": "https://casaos.app/store/main.zip", "func": "service.(*appStore).UpdateCatalog", "file": "/home/runner/work/CasaOS-AppManagement/Cas>
2025-04-27T16:47:56.348+0200    info    appstore size not changed       {"url": "https://github.com/bigbeartechworld/big-bear-casaos/archive/refs/heads/master.zip", "func": "service.(*appStore).UpdateCatalog", "fi

real coral May 7, 2025, 8:35 PM

restive vigil anyone a idea ? in the app-management log i'm getting this errors to : ``` 202...

Did you change the default port by any chance?

restive vigil May 7, 2025, 9:06 PM

real coral Did you change the default port by any chance?

Yes I did.

real coral May 7, 2025, 9:10 PM

restive vigil Yes I did.

From what I found and could understnad:
'Failed to load routes ... /var/run/casaos/routes.json: no such file or directory'

The casaos-gateway service is the entry point for all web traffic to your CasaOS dashboard and apps. It needs a routes.json file to know how to direct incoming requests (e.g., when you go to 192.168.178.xx, it tells the gateway to show the CasaOS dashboard).
If this file is missing, the gateway doesn't know what to do, and you won't be able to access the UI.
The directory /var/run/ is typically a temporary filesystem (tmpfs) that is cleared on reboot. Files here are expected to be recreated by services when they start. The fact that it's not being created points to a deeper issue, potentially related to the incorrect system time or a service failing to initialize correctly.

The logs show the gateway trying to listen:
[::]:82 at 16:37:44
Then, after a stop and restart, [::]:132 at 16:42:54
[::] means it's listening on all network interfaces (IPv4 and IPv6). The port change indicates it might be failing to bind to the initial port or is being reconfigured. If you had CasaOS set to a specific port (e.g., port 80 or your custom xx from 192.168.178.xx:xx), and it's now trying 82 or 132, you definitely won't reach it on the old port. You need to figure out which port it's supposed to be using and if it's successfully binding to it.

App Management Log Errors (failed to parse compose app):
Errors like services.jellyseerr.devices must be a list or services.twingate-connector.volumes must be a list indicate that the Docker Compose files for these specific applications have syntax or validation errors according to the version of the parser CasaOS is using.
This could be, a CasaOS update changing how it validates these files, manual edits to the app configurations that introduced errors, the app store definitions being incompatible.
While these errors are bad for the individual apps, the main app-management service still seems to initialize (App management service is listening...). However, if it's encountering too many issues or if the process that generates routes.json is affected by these parsing failures, it could contribute to the gateway problem.

Try accessing CasaOS via http://192.168.178.xx:PORT. Determine the correct port.
The default CasaOS port is 80, although you changed it so try to use that.
SSH into your device and check which ports are being listened on: sudo ss -tulnp | grep casaos or sudo netstat -tulnp | grep casaos. Look for casaos-gateway.
If still inaccessible, SSH in and check the casaos-gateway logs again: sudo docker logs casaos-gateway (or the relevant container name if it's different). See if the routes.json error continues.

restive vigil May 7, 2025, 9:17 PM

Okay I will Check it Tomorrow:)

obtuse veldtBOT May 7, 2025, 9:17 PM

GG @restive vigil, you just advanced to level 2!