-
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 2 replies
-
The error shows from the very first time it loads? Presumably the api is in fact unreachable once you’re using your vpn, but since the requests are proxied through the homepage backend it is a little surprising. You can hide errors but I’m just pretty curious what the heck is going on here. see https://gethomepage.dev/configs/settings/#hide-widget-error-messages |
Beta Was this translation helpful? Give feedback.
-
Hi Shamoon, Yes the error is the first thats showing when the page is loaded. The part in the services.yaml looks like this;
I'm on a long vacation, so for the time being I only have my tablet and my phone. I will try the option to show no errors. Greetings Henk |
Beta Was this translation helpful? Give feedback.
-
This discussion has been automatically closed because it was marked as answered. See our contributing guidelines for more details. |
Beta Was this translation helpful? Give feedback.
-
This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details. |
Beta Was this translation helpful? Give feedback.
Found the error.
The services.yaml was looking for the wrong name of the container.
I changed the name from Logitech Media Server to Lyrion Media Server.
Thats because the developers also changed the name.
Sorry to bother you with my own mistakes.