petizz 1 Posted November 18, 2024 Posted November 18, 2024 hi everyone, I'm using an emby-server on an ubuntu-system, which is connected via VPN to an vserver. The vserver is providing an nginx-webhost which is a relay to the emby-server. The internal communication over VPN is http, the external communication is HTTPS. Unfortunately this does not work anymore properly after the last ubuntu-update. I can login, open the interface and see all videos, i also can go the the settings, but i cannot open any video or change any settings in the admin-interface. I always get an "bad gateway" error now. The direct access to emby-server is still working fine. I tried to find something useful in the logs, but their are now clear errors in the emby-log. The nginx-log on the webserver however includes the following error: Quote 2024/11/18 17:29:00 [error] 298027#298027: *1578 upstream timed out (110: Unknown error) while reading response header from upstream, client: 95.223.107.100, server: ****.****, request: "POST /emby/System/Configuration?X-Emby-Client=Emby+Web&X-Emby-Device-Name=Google+Chrome+Linux&X-Emby-Device-Id=4d79be67-df55-4ea9-a2f5-c57660811a36&X-Emby-Client-Version=4.8.10.0&X-Emby-Token=7029e268c03e4591ad7f16f6b852cbca&X-Emby-Language=de&reqformat=json HTTP/1.1", upstream: "http://10.8.0.2:8098/emby/System/Configuration?X-Emby-Client=Emby+Web&X-Emby-Device-Name=Google+Chrome+Linux&X-Emby-Device-Id=4d79be67-df55-4ea9-a2f5-c57660811a36&X-Emby-Client-Version=4.8.10.0&X-Emby-Token=7029e268c03e4591ad7f16f6b852cbca&X-Emby-Language=de&reqformat=json", host: "****.****", referrer: "https://****.****/web/index.html" I did mask the URL of the external emby-webinterface with ****.**** http://10.8.0.2:8098/emby/System/Configuration?X-Emby-.... is the internal relay-request to the emby-server over the VPN ChatGPT told me that maybe something changed in the protocoll of ubuntu/emby after the updates and this is why the nginx-relay get back faulty responses. Does someone have an idea how to proceed with the debugging or maybe know whats the reason for this problem? Thanks in advance & best Regards Peter
Solution Luke 42077 Posted November 19, 2024 Solution Posted November 19, 2024 Hi @petizzhave you compared your nginx setup to this?
petizz 1 Posted December 1, 2024 Author Posted December 1, 2024 Hi @Luke: I just had the time to reinstall the complete relay-server and used the exact configuration in your link. I don't know what was the cause for the problems, but now it's working again. Thank you a lot! 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now