pascalheister 1 Posted December 30, 2020 Posted December 30, 2020 (edited) Hi, i'm running Emby (premiere) on my Odroidxu4 nas server (linuxserver) with Openmediavault version 4.1.36-1 Arrakis and using it with Docker version 19.03.14. Since a few days I can no longer reach the emby server. I have tried different ways but cannot connect. My nas server and the files are still accessible. With docker I have already removed and reinstalled Emby once but the problem remains. Could this be related to the latest update? I was able to use Emby for that. I hope you can help me further Kind Regards Pascal Heister Edited December 30, 2020 by pascalheister
Q-Droid 989 Posted December 30, 2020 Posted December 30, 2020 Check to see if Emby is running and what IP/port the server process is binding, then try to connect to those. Do you have other apps/services running on OMV and are those reachable? If not then you might have a networking issue. sudo netstat -lnp|grep -i emby
pascalheister 1 Posted December 30, 2020 Author Posted December 30, 2020 Yes, i have running NZBGet on OMV and it works fine. I can just see the server in the network, i can also access the files on it
Q-Droid 989 Posted December 30, 2020 Posted December 30, 2020 Check to make sure the Emby is actually running. Check the emby server log for errors, attach it if you wish.
Luke 42077 Posted December 31, 2020 Posted December 31, 2020 Hi, yes are you sure that Emby Server is actually started and running? Are you able to reach the web interface on the local machine?
pascalheister 1 Posted December 31, 2020 Author Posted December 31, 2020 This is the latest log in the Emby log map (22-12-2020) embyserver.txt
MRobi 161 Posted December 31, 2020 Posted December 31, 2020 If your latest log is Dec. 22nd, I'm putting my money on Emby isn't running. Start the docker container.
pascalheister 1 Posted December 31, 2020 Author Posted December 31, 2020 1 minute ago, MRobi said: If your latest log is Dec. 22nd, I'm putting my money on Emby isn't running. Start the docker container. Docker says it's running ?? see image
Q-Droid 989 Posted December 31, 2020 Posted December 31, 2020 (edited) Can you restart your Emby server/container and post the new embyserver log? Also, in my first post I showed how you can check if Emby is listening for connections. Edited December 31, 2020 by Q-Droid
MRobi 161 Posted December 31, 2020 Posted December 31, 2020 12 minutes ago, pascalheister said: Docker says it's running ?? see image I'm still learning docker, and not familiar with OMV at all, so I may not be the best to help you yet. But I'm not seeing a port binded from the host to the container. See how NZBGet has port 6789? The linuxserver.io emby container needs -p 8096:8096. Could you possibly have missed this step?
pascalheister 1 Posted December 31, 2020 Author Posted December 31, 2020 (edited) 1 hour ago, MRobi said: I'm still learning docker, and not familiar with OMV at all, so I may not be the best to help you yet. But I'm not seeing a port binded from the host to the container. See how NZBGet has port 6789? The linuxserver.io emby container needs -p 8096:8096. Could you possibly have missed this step? It it always been on host (and worked perfect), not with a special port. Maby i will give it a try > to bad no effect Edited December 31, 2020 by pascalheister
pascalheister 1 Posted January 1, 2021 Author Posted January 1, 2021 change te host did not have any effect
Q-Droid 989 Posted January 1, 2021 Posted January 1, 2021 12 minutes ago, pascalheister said: change te host did not have any effect What does this mean? What did you do?
pascalheister 1 Posted January 1, 2021 Author Posted January 1, 2021 3 hours ago, Q-Droid said: What does this mean? What did you do? I tried your option.. change it from host to port setting, but that didn't work. Remains a mystery to me why it doesn't work. Didn't change anything in the OMV, Docker or Router settings either.
Q-Droid 989 Posted January 1, 2021 Posted January 1, 2021 While that wasn't my suggestion it is good to try different things. The container status above showed no port mappings which is why that was mentioned. What we've asked for is confirmation that the emby server is actually running. The server process itself, not the container. You have not posted current logs that include the server startup and runtime activity. The posted log was old, did not include server startup (rotated log) and appeared to have shutdown at the end. After you restart emby check to see if it's responding on the standard port from the host command line, upper case letter "O" below: wget -O- http://localhost:8096
pascalheister 1 Posted January 2, 2021 Author Posted January 2, 2021 15 hours ago, Q-Droid said: While that wasn't my suggestion it is good to try different things. The container status above showed no port mappings which is why that was mentioned. What we've asked for is confirmation that the emby server is actually running. The server process itself, not the container. You have not posted current logs that include the server startup and runtime activity. The posted log was old, did not include server startup (rotated log) and appeared to have shutdown at the end. After you restart emby check to see if it's responding on the standard port from the host command line, upper case letter "O" below: wget -O- http://localhost:8096 Hi, That won't work i can nog reach it local, how can i see that Emby is running without Docker container (it has no effect i restart it in Docker container)
Q-Droid 989 Posted January 2, 2021 Posted January 2, 2021 If you can't reach it local then it's not servicing requests. Emby doesn't bind to a specific address and the same goes for the docker-proxy. How do you see if Emby is running? ps -ef | grep -i emby If the process is running and not responding then the emby server log we keep asking for might have some clues. At this point I would reboot the host to start fresh, check Emby and grab the log.
MRobi 161 Posted January 3, 2021 Posted January 3, 2021 I'm the one asking about the ports. The linuxserver emby image maps ports in bridge mode. -p 8096:8096 \ -p 8920:8920 `#optional` \ From your screenshot, you don't have these ports mapped. So when you removed and re-installed did you miss this step or did you configure your network differently? If you missed this step, when you navigate to 192.168.X.XXX:8096 there's nothing that tells it to direct the request to that container which would make it inaccessible.
pascalheister 1 Posted January 5, 2021 Author Posted January 5, 2021 (edited) this topic can be closed problem solved, i tried different installations conclusion the arm32v7 version is the right one Edited January 5, 2021 by pascalheister 1
Luke 42077 Posted January 6, 2021 Posted January 6, 2021 4 hours ago, pascalheister said: this topic can be closed problem solved, i tried different installations conclusion the arm32v7 version is the right one Hi, are you saying you were running the wrong architecture package for your machine?
shad0wxax 6 Posted December 31, 2022 Posted December 31, 2022 (edited) On 1/2/2021 at 8:28 AM, Q-Droid said: If you can't reach it local then it's not servicing requests. Emby doesn't bind to a specific address and the same goes for the docker-proxy. How do you see if Emby is running? ps -ef | grep -i emby If the process is running and not responding then the emby server log we keep asking for might have some clues. At this point I would reboot the host to start fresh, check Emby and grab the log. So i am also having this issue. servers been running fine for weeks and the just the other day stopped responding. ive reset the local machine running openmediavault6 and ive restarted the portainer container as well as tried to redo the container. nothign works. my other containers work fine. im unsure where to get the log file yall requested in this thread but i did try the commands and can post my results. doing the same commands on my other containers result in connection where emby isnt. Edit: also i cannot access the web client locally either. troubleshooting emby.txt Edited December 31, 2022 by shad0wxax
Q-Droid 989 Posted December 31, 2022 Posted December 31, 2022 The logs are in the path/volume you mapped to /config for the Emby container (<path to config>/logs). Best if you restart the Emby container before getting and posting the log since it will have more useful startup related info.
shad0wxax 6 Posted December 31, 2022 Posted December 31, 2022 (edited) ok so i figured it out. somehow the system was syncing something in a folder in the appdata and filled my harddrive to 100%. deleted that folder and it good now. but i dont know why/how it was syncing or what it was syncing and how to turn that off so i dont have that issue in the future. unless allowing downloads from my server will go to the sync folder first while its being downloaded? Edited December 31, 2022 by shad0wxax 1
Luke 42077 Posted January 2, 2023 Posted January 2, 2023 On 12/31/2022 at 2:56 PM, shad0wxax said: ok so i figured it out. somehow the system was syncing something in a folder in the appdata and filled my harddrive to 100%. deleted that folder and it good now. but i dont know why/how it was syncing or what it was syncing and how to turn that off so i dont have that issue in the future. unless allowing downloads from my server will go to the sync folder first while its being downloaded? HI, if the downloads require conversion, then yes, the converted output will be stored there until it gets downloaded by the app.
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