Search the Community

Hello, Last night i set up Emby for the first time and had everything working perfect, both local and remote access. After initial server creation and while scanning for library files, my server suddenly shut down and when i closed the browser and relogged into my TerraMaster NAS to access Emby, i received "502 - Bad Gateway", with some nginx version i can't remember. I uninstalled Emby, and reinstalled on the NAS and then it all worked perfectly. Library files got scanned and i got local and remote access working and thought nothing more of it. I woke up this morning and was unable to connect via mobile. Logged onto NAS to check server and the same thing, 502 error. This time, i just restarted the NAS and it is currently working again. What are some troubleshooting options i can take? I don't want to have to restart my NAS each time i want to access my server. I have no idea where to start since it seems to randomly occur. Notes: No logs created at time of event (couldn't identify anything in existing logs. Deleted them. Tried to access again while receiving the 502 error, and no new logs created.) (since it is now working, i have a new set of logs created if you require the hardware detection log at all, but i doubt the main log will be useful) Emby Version - 4.5.2.0 NAS - TerraMaster F2-210 NAS Version - 4.2.08

same issues here on Terramaster Nas not working even plugins doesn't show up , installed VU+ go to live for set up no Vu plugin to see , install reboot server Bad gateway , also when i tried on windows itself only local i give up as it is hours spending for nothing only local i can watch it with much easier plug-ins :-(

Hello, we are having problem that server keeps showing 502 bad gateway. Need to restart docker to resolve this, can u please check our log? emby_log.zip