Search the Community
Showing results for tags '8920'.
hello, i've been using emby for a little while on my QNAP TS-251B, but recently noticed that my devices (browsers, an nvidia shield) only connect via unsecured http on the default port 8096. when trying to bring up the page (from within my lan) on the default https port of 8920, chrome gives me ERR_CONNECTION_REFUSED. in Emby Configuration > Server > Network, i do see that the port number is indeed set to 8920. however, when i run nmap against the device to scan for open ports, 8920 appears closed. i'm using Emby server version 22.214.171.124
Hello Guys, facts: installed emby on a debian vps. allow 8096 and 8920 in ufw buy a Domain at namecheap. create A Record for the VPS IP. create a letsencrypt cert (https://emby.media/community/index.php?/topic/42315-creating-a-letsencrypt-ssl-certificate-for-emby/ Emby config: add certfolder to /opt/emby-server/ssl/ssl.pfx Emby config: add external Domain "https://xxx.xxx" Problem: I got emby over "http://xxx.xxx:8096"but on "https://xxx.xxx:8920" I got "ERR_TUNNEL_CONNECTION_FAILED" can you help me with this issue? thanks
Good evening guys, is from about 1 week that the ssl connection on port 8920, does not work anymore. I try to restart emby, and it works for about half an hour, then do not work anymore. I have the latest version of emby installed. It works via http. Using the certificate of let'sencrypt from 6 months is it always worked. Can someone help me? The only mistake that I find in the log is this. Thank you 2016-09-15 14:30:14.1333 Error ServiceStackHost: Error occured while Processing Request: Access token is required. *** Error Report *** Version: 3.0.7100.0 Command line: /usr/lib