-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Homeassistant - Problem OPDS and "ValueError: No route found for path '/api/v3/ws'. #416
Comments
do you have this line in your root_path = "/api/hassio_ingress/pEGeoOIlm1tpeAudrHRtnmeGFDavfaQjalwJXvX696Q" |
It occurs to me that the homeassistant installation might be able to automatically configure this for you. And that homeassistant users might be less familiar with configuring their individual docker based applications. |
where i can find this file in my Ha directory ? |
I'm not really sure how HomeAssistant works. The instructions for HomeAssistant and the HomeAssistant config was provided by alexbelgium and I just stuck it in the docs. I get the impression that it's a bunch of preconfigured docker containers and a nice web gui to help you configure and manage them.
services:
codex:
env_file: .env
image: docker.io/ajslater/codex
container_name: codex
volumes:
- /host/path/to/config:/config
-/host/path/to/comics:/comics:ro
ports:
- 9810:9810
restart: on-failure from my docker container documentation. Where exactly HA is mounting this from i'm not sure. If there's an HA directory and something like I can see that he provides an nginx reverse proxy config for HA and a custom Dockerfile, but I'm a little lost as to where the mounting happens in the HA config. I suggest you ask Alex on his github: https://github.com/alexbelgium/hassio-addons/issues |
Hi! I'll look at it Indeed HA is globally an os based on modular docker containers. For example, one for sound, one for supervisor, one for the different add-ons... Ingress is quite tricky : there is a dual layer of nginx that sends (for example) |
After thinking I think the best for you is to use as endpoints To give a bit more details : ingress (and the weird long path) is used to access Codex from your HA app itself. However if a port is configured in the appropriate HA section, you can access it using ip:port without any weird reverse proxy things that break stuff :) Edit : just as reference, all your config files including the hypercorn.toml can be found in |
hello,
i have two problem on CODEX and home Assistant.
I want to use LIbrera and i have error on OPDS V1 and V2. i can't add link.
http://debian.local:8123/api/hassio_ingress/pEGeoOIlm1tpeAudrHRtnmeGFDavfaQjalwJXvX696Q/opds/v2.0/r/0/1
http://debian.local:8123/api/hassio_ingress/pEGeoOIlm1tpeAudrHRtnmeGFDavfaQjalwJXvX696Q/opds/v1.2/r/0/1
On the log i have this error
"ValueError: No route found for path '/api/v3/ws'.
172.30.32.2 - - [22/Jul/2024:13:41:11 +0200] "GET /api/v3/ws HTTP/1.1" 500 0 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:129.0) Gecko/20100101 Firefox/129.0"
2024-07-22 13:45:48 CEST ERROR Error in ASGI Framework
thanks
The text was updated successfully, but these errors were encountered: