You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the issue
I've configured the skill and docker container so that the intent request comes through but it gets stuck at a 502 error. There's also a an issue connecting to Navidrome at the start of the logs after an initial successful connection.
I'm using Caddy and both navidrome and asknavidrome are running on my pi on the same docker network. I was initially having issues with SSL/TLS encryption so I had to force 1.2 TLS for the handshake not to error.
I fear my caddy config is wrong as the documentation is a bit light on what settings to use and I'm not so familiar with it - so here's a sanitised version of my caddy config for asknavidrome:
It looks like you have a couple of issues, firstly the AskNavidrome skill cannot connect to your Navidrome instance, for this you'll need to double check your configuration file and the physical connectivity between the AskNavidrome container.
In your caddy config it looks like the container names may be duplicated:
Describe the issue
I've configured the skill and docker container so that the intent request comes through but it gets stuck at a 502 error. There's also a an issue connecting to Navidrome at the start of the logs after an initial successful connection.
I'm using Caddy and both navidrome and asknavidrome are running on my pi on the same docker network. I was initially having issues with SSL/TLS encryption so I had to force 1.2 TLS for the handshake not to error.
I fear my caddy config is wrong as the documentation is a bit light on what settings to use and I'm not so familiar with it - so here's a sanitised version of my caddy config for asknavidrome:
Operating System
Raspberry Pi 5 running Debian [bookworm]. Docker image was rebuilt using
FROM arm64v8/alpine:3.15.0 as build
To Reproduce
Running any command, simulated or otherwise
Logs
The text was updated successfully, but these errors were encountered: