Skip to content
This repository has been archived by the owner on Sep 25, 2022. It is now read-only.

Forked-daapd: 502 Bad Gateway #23

Closed
Plobli opened this issue Feb 14, 2021 · 1 comment
Closed

Forked-daapd: 502 Bad Gateway #23

Plobli opened this issue Feb 14, 2021 · 1 comment

Comments

@Plobli
Copy link

Plobli commented Feb 14, 2021

Hey, I installed the forked-daapd in HA but I can't open the WebUI over http://homeassistant.local:8123/e4ac757a_forked-daapd or connect over the integration. I get only a 502: Bad Gateway.
In the supervisor log I found this issues:

21-02-14 11:07:30 ERROR (MainThread) [supervisor.api.security] Invalid token for access /host/info
21-02-14 11:09:32 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
21-02-14 11:09:36 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.32.1:1337 ssl:default [Connect call failed ('172.30.32.1', 1337

What can I do?

@Ulrar
Copy link
Owner

Ulrar commented Feb 14, 2021

Hi,

Unfortunately that's because of issue #22, which I haven't managed to fix yet.

@Ulrar Ulrar closed this as completed Feb 14, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants