Alsterschiffer 1 Posted June 18, 2022 Share Posted June 18, 2022 20 hours ago, inFusion said: Good Day everyone! First time user of Emby server, and running in to a few problems(I've seen a few posts here, but still can't seem to figure out what my next steps are.) NAS Model - QNAP TS-220 Device Firmware - 4.3.3.1945 (20220303) Emby Server Version - emby-server-qnap-mono_4.7.2.0_arm-x19 Emby Server installed no issue. I'm able to access the NAS no issue using it's Web address(192.168.xxx.xxx:8080) When I try to open the Emby Server app(Either using the app itself on the QNAP or through an PC web browser at address 192.168.xxx.xxx:8096) I get the connection refused error message. I have done no port forwarding on my router for port 8096, as I'm only wanting to use it on my external network for the time being. I saw that one of the users @Luke had mentioned something about the Emby Server and the Qnap fighting over SSL, and I need to go into the Emby app and change it, but if I can't open the app, how do I go about doing that. Any insight is greatly appreciated! I have the same issue. Either Emby server isn't running at all or port 8096 is not answering....please help. No problems to access QNAP on port 8080 though.... Link to comment Share on other sites More sharing options...
Luke 37233 Posted June 18, 2022 Share Posted June 18, 2022 Hi there @Alsterschifferdid you follow the install instructions on our website? Link to comment Share on other sites More sharing options...
Alsterschiffer 1 Posted June 19, 2022 Author Share Posted June 19, 2022 Hi Luke, I am actually experiencing exactly the same issues as InFusion does, same hardware, same QNAP firmware, same emby version. I followed the instructions on your website: Download one of the following packages depending on your QNAP NAS model (emby-server-qnap-mono_4.7.2.0_arm-x19.qpkg) Install Emby Server using the QNAP Web interface. Start Emby Server using the QNAP Web interface. Open a web browser to http://localhost:8096 I did a port scan. Port 8096 is not open/listening. Any idea? Thanks for your help. Link to comment Share on other sites More sharing options...
Luke 37233 Posted June 19, 2022 Share Posted June 19, 2022 8 hours ago, Alsterschiffer said: Hi Luke, I am actually experiencing exactly the same issues as InFusion does, same hardware, same QNAP firmware, same emby version. I followed the instructions on your website: Download one of the following packages depending on your QNAP NAS model (emby-server-qnap-mono_4.7.2.0_arm-x19.qpkg) Install Emby Server using the QNAP Web interface. Start Emby Server using the QNAP Web interface. Open a web browser to http://localhost:8096 I did a port scan. Port 8096 is not open/listening. Any idea? Thanks for your help. @Alsterschiffer Did you make sure to do the first step listed at the top of the qnap instructions? Link to comment Share on other sites More sharing options...
Alsterschiffer 1 Posted June 19, 2022 Author Share Posted June 19, 2022 3 hours ago, Luke said: @Alsterschiffer Did you make sure to do the first step listed at the top of the qnap instructions? Well, yes. According to the emby website, that's the file to download and to install. I also tried version 4.8.0.2...both files install and start without errors, but port 8096 is not listening. Link to comment Share on other sites More sharing options...
Luke 37233 Posted June 19, 2022 Share Posted June 19, 2022 Did you do this part? Quote Before installing Emby on QNAP, you must have "Allow installation and execution of applications without a digital signature" selected and applied on the QNAP server at this location: App Center / Settings [gear wheel] / General. (This will produce a warning.) You must leave this setting on in order to avoid having Emby Server app shut down every day or so by the QNAP system (which would then require a manual restart of the Emby Server app). Link to comment Share on other sites More sharing options...
Alsterschiffer 1 Posted June 19, 2022 Author Share Posted June 19, 2022 3 minutes ago, Luke said: Did you do this part? Yes, as mentioned, the installation and start of the process worked without errors, but port 8096 is not listening. Shutting down the process and starting it manually again doesn't help either. Link to comment Share on other sites More sharing options...
keithsrobertson 4 Posted June 19, 2022 Share Posted June 19, 2022 Check the Qnap control panel->Security->Allow/Deny list to make sure local lan can access the qnap. Otherwise check your QuFirewall for the same if you have that installed. Enable access from local lan devices: 192.168.1.1-192.168.1.254, 127.0.0.1 and any other ones like geographic region and ddns domains if applicable. Link to comment Share on other sites More sharing options...
Alsterschiffer 1 Posted June 20, 2022 Author Share Posted June 20, 2022 10 hours ago, keithsrobertson said: Check the Qnap control panel->Security->Allow/Deny list to make sure local lan can access the qnap. Otherwise check your QuFirewall for the same if you have that installed. Enable access from local lan devices: 192.168.1.1-192.168.1.254, 127.0.0.1 and any other ones like geographic region and ddns domains if applicable. Hi Keith, on QNAP, "Allow all connections" is ticked. I don't have QuFirewall or any other Firewall installed on QNAP. On QNAP I did a telnet to port 8096, I got "connection refused". I have other apps installed, e.g. UPNP server or PLEX, which uses other ports....they work without problems. Any log files I can look at to help you? Thanks for your help, Michael Link to comment Share on other sites More sharing options...
Tamsy 1 Posted June 20, 2022 Share Posted June 20, 2022 (edited) Registered myself to add to Alsterschiffer's problem: I am experiencing *exactly* the same problem with 4.7.3.0 and 4.8.0.2 on a QNAP TVS-473. Rolling back to 4.7.2.0 (and below) makes the problem go away. I am on Emby Premium since 2018 and had never experienced any issues before. Emby Server is indeed running (active) on the NAS with v.4.7.3.0 but inaccessible through the web interface and all devices connecting to the Emby Server. NAS Firmware-Version: 5.0.0.2055 Emby Server variant: emby-server-qnap_4.7.3.0_x86_64 & emby-server-qnap_4.8.0.2_x86_64 Edited June 20, 2022 by Tamsy Added firmware version. Link to comment Share on other sites More sharing options...
keithsrobertson 4 Posted June 20, 2022 Share Posted June 20, 2022 Could maybe try and use WinSCP to login to the Qnap NAS and browse to /share/CACHEDEV1_DATA/.qpkg/EmbyServer/programdata/logs folder to see if any logs are there, and copy them to local pc folder somewhere for upload. Probably have to make sure that the Allow SSH and Enable SFTP options are ticked in the Control Panel->Network & File Services->Telnet / SSH to allow you to use WinSCP - Think the Qnap Finder application for Windows will allow you to enable/disable those settings remotely as needed - ideally you only have it on when you need to use it and off for security reasons. Link to comment Share on other sites More sharing options...
Alsterschiffer 1 Posted June 20, 2022 Author Share Posted June 20, 2022 1 hour ago, keithsrobertson said: Could maybe try and use WinSCP to login to the Qnap NAS and browse to /share/CACHEDEV1_DATA/.qpkg/EmbyServer/programdata/logs folder to see if any logs are there, and copy them to local pc folder somewhere for upload. Probably have to make sure that the Allow SSH and Enable SFTP options are ticked in the Control Panel->Network & File Services->Telnet / SSH to allow you to use WinSCP - Think the Qnap Finder application for Windows will allow you to enable/disable those settings remotely as needed - ideally you only have it on when you need to use it and off for security reasons. Got the logfile. Don't see any errors.....can I mail it to you via PM? Link to comment Share on other sites More sharing options...
keithsrobertson 4 Posted June 20, 2022 Share Posted June 20, 2022 Quote emby-server-qnap-mono_{version}_arm-x19.qpkg I think for some reason its trying to use an arm version, whereas your Nas is x86-64. I would uninstall everything tbh, make sure all the folder are gone (verify they are removed by using WinSCP) and then get the https://github.com/MediaBrowser/Emby.Releases/releases/download/4.8.0.2/emby-server-qnap_4.8.0.2_x86_64.qpkg one. Here are my logs for comparison: 2022-06-20 12:09:15.521 Info Main: Application path: /share/CACHEDEV1_DATA/.qpkg/EmbyServer/system/EmbyServer.dll 2022-06-20 12:09:17.106 Info Main: Emby Command line: /share/CACHEDEV1_DATA/.qpkg/EmbyServer/system/EmbyServer.dll -programdata /share/CACHEDEV1_DATA/.qpkg/EmbyServer/programdata -ffdetect /share/CACHEDEV1_DATA/.qpkg/EmbyServer/bin/ffdetect -ffmpeg /share/CACHEDEV1_DATA/.qpkg/EmbyServer/bin/ffmpeg -ffprobe /share/CACHEDEV1_DATA/.qpkg/EmbyServer/bin/ffprobe -defaultdirectory /share/CACHEDEV1_DATA/Public -updatepackage emby-server-qnap_{version}_x86_64.qpkg Operating system: Linux version 5.10.60-qnap (root@U16BuildServer172) (x86_64-QNAP-linux-gnu-gcc (toolchain config: [gcc-4.9.2 binutils-2.25 glibc-2.21]) 4.9.2, GNU ld Framework: .NET 6.0.2 OS/Process: x64/x64 Runtime: share/CACHEDEV1_DATA/.qpkg/EmbyServer/system/System.Private.CoreLib.dll Processor count: 4 Data path: /share/CACHEDEV1_DATA/.qpkg/EmbyServer/programdata Application path: /share/CACHEDEV1_DATA/.qpkg/EmbyServer/system 2022-06-20 12:09:17.106 Info Main: Logs path: /share/CACHEDEV1_DATA/.qpkg/EmbyServer/programdata/logs 2022-06-20 12:09:17.106 Info Main: Cache path: /share/CACHEDEV1_DATA/.qpkg/EmbyServer/programdata/cache 2022-06-20 12:09:17.107 Info Main: Internal metadata path: /share/CACHEDEV1_DATA/.qpkg/EmbyServer/programdata/metadata 2022-06-20 12:09:17.108 Info Main: Transcoding temporary files path: /share/CACHEDEV1_DATA/.qpkg/EmbyServer/programdata/transcoding-temp 2022-06-20 12:09:17.300 Info App: Application version: 4.8.0.2 and yours: 2022-06-20 17:51:49.709 Info Main: Application path: /share/MD0_DATA/.qpkg/EmbyServer/system/EmbyServer.exe 2022-06-20 17:52:02.582 Debug App: AddMonoUriWorkaround 2022-06-20 17:52:02.739 Info Main: Emby Command line: /share/MD0_DATA/.qpkg/EmbyServer/system/EmbyServer.exe -programdata /share/MD0_DATA/.qpkg/EmbyServer/programdata -ffdetect /share/MD0_DATA/.qpkg/EmbyServer/bin/ffdetect -ffmpeg /share/MD0_DATA/.qpkg/EmbyServer/bin/ffmpeg -ffprobe /share/MD0_DATA/.qpkg/EmbyServer/bin/ffprobe -defaultdirectory /share/CACHEDEV1_DATA/Public -updatepackage emby-server-qnap-mono_{version}_arm-x19.qpkg Operating system: Linux version 3.4.6 (root@U16BuildServer105) (gcc version 4.2.1) #1 Tue Oct 6 02:13:52 CST 2020 Framework: Mono: 6.12.0.122 (tarball Wed Oct 6 07:53:52 PM UTC 2021) OS/Process: X86/X86 Runtime: share/MD0_DATA/.qpkg/EmbyServer/lib/mono/4.5/mscorlib.dll Processor count: 1 Data path: /share/MD0_DATA/.qpkg/EmbyServer/programdata Application path: /share/MD0_DATA/.qpkg/EmbyServer/system 2022-06-20 17:52:02.750 Info Main: Logs path: /share/MD0_DATA/.qpkg/EmbyServer/programdata/logs 2022-06-20 17:52:02.750 Info Main: Cache path: /share/MD0_DATA/.qpkg/EmbyServer/programdata/cache 2022-06-20 17:52:02.751 Info Main: Internal metadata path: /share/MD0_DATA/.qpkg/EmbyServer/programdata/metadata 2022-06-20 17:52:02.755 Info Main: Transcoding temporary files path: /share/MD0_DATA/.qpkg/EmbyServer/programdata/transcoding-temp 2022-06-20 17:52:04.144 Info App: Application version: 4.7.2.0 Link to comment Share on other sites More sharing options...
Alsterschiffer 1 Posted June 20, 2022 Author Share Posted June 20, 2022 12 minutes ago, keithsrobertson said: I think for some reason its trying to use an arm version, whereas your Nas is x86-64. I would uninstall everything tbh, make sure all the folder are gone (verify they are removed by using WinSCP) and then get the https://github.com/MediaBrowser/Emby.Releases/releases/download/4.8.0.2/emby-server-qnap_4.8.0.2_x86_64.qpkg one. Here are my logs for comparison: 2022-06-20 12:09:15.521 Info Main: Application path: /share/CACHEDEV1_DATA/.qpkg/EmbyServer/system/EmbyServer.dll 2022-06-20 12:09:17.106 Info Main: Emby Command line: /share/CACHEDEV1_DATA/.qpkg/EmbyServer/system/EmbyServer.dll -programdata /share/CACHEDEV1_DATA/.qpkg/EmbyServer/programdata -ffdetect /share/CACHEDEV1_DATA/.qpkg/EmbyServer/bin/ffdetect -ffmpeg /share/CACHEDEV1_DATA/.qpkg/EmbyServer/bin/ffmpeg -ffprobe /share/CACHEDEV1_DATA/.qpkg/EmbyServer/bin/ffprobe -defaultdirectory /share/CACHEDEV1_DATA/Public -updatepackage emby-server-qnap_{version}_x86_64.qpkg Operating system: Linux version 5.10.60-qnap (root@U16BuildServer172) (x86_64-QNAP-linux-gnu-gcc (toolchain config: [gcc-4.9.2 binutils-2.25 glibc-2.21]) 4.9.2, GNU ld Framework: .NET 6.0.2 OS/Process: x64/x64 Runtime: share/CACHEDEV1_DATA/.qpkg/EmbyServer/system/System.Private.CoreLib.dll Processor count: 4 Data path: /share/CACHEDEV1_DATA/.qpkg/EmbyServer/programdata Application path: /share/CACHEDEV1_DATA/.qpkg/EmbyServer/system 2022-06-20 12:09:17.106 Info Main: Logs path: /share/CACHEDEV1_DATA/.qpkg/EmbyServer/programdata/logs 2022-06-20 12:09:17.106 Info Main: Cache path: /share/CACHEDEV1_DATA/.qpkg/EmbyServer/programdata/cache 2022-06-20 12:09:17.107 Info Main: Internal metadata path: /share/CACHEDEV1_DATA/.qpkg/EmbyServer/programdata/metadata 2022-06-20 12:09:17.108 Info Main: Transcoding temporary files path: /share/CACHEDEV1_DATA/.qpkg/EmbyServer/programdata/transcoding-temp 2022-06-20 12:09:17.300 Info App: Application version: 4.8.0.2 and yours: 2022-06-20 17:51:49.709 Info Main: Application path: /share/MD0_DATA/.qpkg/EmbyServer/system/EmbyServer.exe 2022-06-20 17:52:02.582 Debug App: AddMonoUriWorkaround 2022-06-20 17:52:02.739 Info Main: Emby Command line: /share/MD0_DATA/.qpkg/EmbyServer/system/EmbyServer.exe -programdata /share/MD0_DATA/.qpkg/EmbyServer/programdata -ffdetect /share/MD0_DATA/.qpkg/EmbyServer/bin/ffdetect -ffmpeg /share/MD0_DATA/.qpkg/EmbyServer/bin/ffmpeg -ffprobe /share/MD0_DATA/.qpkg/EmbyServer/bin/ffprobe -defaultdirectory /share/CACHEDEV1_DATA/Public -updatepackage emby-server-qnap-mono_{version}_arm-x19.qpkg Operating system: Linux version 3.4.6 (root@U16BuildServer105) (gcc version 4.2.1) #1 Tue Oct 6 02:13:52 CST 2020 Framework: Mono: 6.12.0.122 (tarball Wed Oct 6 07:53:52 PM UTC 2021) OS/Process: X86/X86 Runtime: share/MD0_DATA/.qpkg/EmbyServer/lib/mono/4.5/mscorlib.dll Processor count: 1 Data path: /share/MD0_DATA/.qpkg/EmbyServer/programdata Application path: /share/MD0_DATA/.qpkg/EmbyServer/system 2022-06-20 17:52:02.750 Info Main: Logs path: /share/MD0_DATA/.qpkg/EmbyServer/programdata/logs 2022-06-20 17:52:02.750 Info Main: Cache path: /share/MD0_DATA/.qpkg/EmbyServer/programdata/cache 2022-06-20 17:52:02.751 Info Main: Internal metadata path: /share/MD0_DATA/.qpkg/EmbyServer/programdata/metadata 2022-06-20 17:52:02.755 Info Main: Transcoding temporary files path: /share/MD0_DATA/.qpkg/EmbyServer/programdata/transcoding-temp 2022-06-20 17:52:04.144 Info App: Application version: 4.7.2.0 emby-server-qnap_4.8.0.2_x86_64.qpkg doesn't install. My QNAP is TS-220 and has a Marvell 1.6GHz CPU. According to the emby website, ARM19 is the right file. ARM X12, X19, X20, X21 - Supported models (not an exhaustive list): TS-112P, TS-120, TS-121, TS-212-E, TS-212P, TS-220, TS-221, TS-412, TS-420, TS-420U, TS-421, TS-421U Link to comment Share on other sites More sharing options...
keithsrobertson 4 Posted June 20, 2022 Share Posted June 20, 2022 Ah yes, sorry I was looking at the other users qnap the TVS-473. My bad Link to comment Share on other sites More sharing options...
Alsterschiffer 1 Posted June 20, 2022 Author Share Posted June 20, 2022 1 hour ago, keithsrobertson said: Ah yes, sorry I was looking at the other users qnap the TVS-473. My bad No problem....any idea for the QNAP hardware I use....? Link to comment Share on other sites More sharing options...
Luke 37233 Posted June 20, 2022 Share Posted June 20, 2022 4 hours ago, Alsterschiffer said: emby-server-qnap_4.8.0.2_x86_64.qpkg doesn't install. My QNAP is TS-220 and has a Marvell 1.6GHz CPU. According to the emby website, ARM19 is the right file. ARM X12, X19, X20, X21 - Supported models (not an exhaustive list): TS-112P, TS-120, TS-121, TS-212-E, TS-212P, TS-220, TS-221, TS-412, TS-420, TS-420U, TS-421, TS-421U OK I think there's an issue specific to your model that needs looking into. Thanks. Link to comment Share on other sites More sharing options...
Tamsy 1 Posted June 21, 2022 Share Posted June 21, 2022 5 hours ago, Luke said: OK I think there's an issue specific to your model that needs looking into. Thanks. And please also for the TVS-473 (X86_64) since I am having the same experience as Alsterschiffer with the latest 4.7.3.0 (Emby Server starts and is active on the NAS, no access to it though). I will do another upgrade later today and post the logfile here). Link to comment Share on other sites More sharing options...
Tamsy 1 Posted June 21, 2022 Share Posted June 21, 2022 (edited) It seems to be indeed that "glibc errors on certain NAS devices" which triggered the unaccessible error on certain QNAP systems. A manual update to 4.7.3.0 from CLI brought-up: [/share/CACHEDEV1_DATA/Public] # ./emby-server-qnap_4.7.3.0_x86_64.qpkg Install QNAP package on TS-NAS... ./ ./built_info ./qinstall.sh ./qpkg.cfg ./package_routines 6575+1 records in 6575+1 records out 162912026 bytes (155.4MB) copied, 0.788365 seconds, 197.1MB/s 159093+1 records in 159093+1 records out 162912026 bytes (155.4MB) copied, 0.793730 seconds, 195.7MB/s EmbyServer 4.7.2.0 is already installed. Setup will now perform package upgrading. Firmware check is fine. EmbyServer is not running. Link service start/stop script: emby-server.sh Set QPKG information in /etc/config/qpkg.conf /share/CACHEDEV1_DATA/.qpkg/EmbyServer/system/EmbyServer: /share/CACHEDEV1_DATA/.qpkg/EmbyServer/lib/libc.so.6: version `GLIBC_2.18' not found (required by /share/CACHEDEV1_DATA/.qpkg/EmbyServer/lib/libstdc++.so.6) While doing the upgrade to 4.7.3.0 version 4.7.4.0 popped-up on GitHub. I upgraded to 4.7.4.0 and the upgrade process went smooth without any errors. The Emby Server is accessible again through web browser and from my devices (SmartTV etc.). At least for the QNAP TVS-473 (x86_64) the problem seems to be solved. Thank you for the swift upgrade to 4.7.4.0 Edited June 21, 2022 by Tamsy Extend logfile output to stdoud 1 Link to comment Share on other sites More sharing options...
Alsterschiffer 1 Posted June 21, 2022 Author Share Posted June 21, 2022 18 hours ago, Luke said: OK I think there's an issue specific to your model that needs looking into. Thanks. Hi Luke, I tried 4.7.4.0 too, but no change on my side. For a short moment I saw a message in the browser: "Emby Server is loading. Please try again shortly". But then, I wasn't able to connect to 8096 anymore. Will send the log file to you via PM. 1 Link to comment Share on other sites More sharing options...
Alsterschiffer 1 Posted June 22, 2022 Author Share Posted June 22, 2022 Hi @Luke & @keithrobertson any idea how to proceed? Thanks for your help. Michael Link to comment Share on other sites More sharing options...
Luke 37233 Posted June 22, 2022 Share Posted June 22, 2022 Just now, Alsterschiffer said: Hi @Luke & @keithrobertson any idea how to proceed? Thanks for your help. Michael I think there is an issue specific to the TS-220 model and we'll need time to look into it. Given that it's a 9 year old NAS it might be a tough one for us to support. Link to comment Share on other sites More sharing options...
Alsterschiffer 1 Posted June 22, 2022 Author Share Posted June 22, 2022 1 hour ago, Luke said: I think there is an issue specific to the TS-220 model and we'll need time to look into it. Given that it's a 9 year old NAS it might be a tough one for us to support. Yes, I agree I tried older versions as well, 4.4.1.0, 4.5.1.0 and 4.6.1.0...all show the same behaviour....can you confirm that .....-mono_...._arm-x19.qpkg is the right install file for TS-220? Link to comment Share on other sites More sharing options...
Luke 37233 Posted June 22, 2022 Share Posted June 22, 2022 36 minutes ago, Alsterschiffer said: Yes, I agree I tried older versions as well, 4.4.1.0, 4.5.1.0 and 4.6.1.0...all show the same behaviour....can you confirm that .....-mono_...._arm-x19.qpkg is the right install file for TS-220? I believe so yes. Link to comment Share on other sites More sharing options...
Alsterschiffer 1 Posted June 23, 2022 Author Share Posted June 23, 2022 23 hours ago, Luke said: I believe so yes. So, what's the next step/solution...if any? Link to comment Share on other sites More sharing options...
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