Jump to content

Search the Community

Showing results for tags 'ports'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements
    • Emby Premiere Purchase/Subscription Support
    • Feature Requests
    • Tutorials and Guides
  • Emby Server
    • General/Windows
    • Android Server
    • Asustor
    • FreeBSD
    • Linux
    • NetGear ReadyNAS
    • MacOS
    • QNAP
    • Synology
    • TerraMaster NAS
    • Thecus
    • Western Digital
    • DLNA
    • Live TV
  • Emby Apps
    • Amazon Alexa
    • Android Mobile
    • Android TV / Fire TV
    • Emby Theater
    • iOS
    • Apple TV
    • Kodi
    • Raspberry Pi
    • Roku
    • Samsung Smart TV
    • Sony PlayStation
    • LG Smart TV
    • Web App
    • Windows Media Center
    • Plugins
  • Language-specific support
    • Arabic
    • Dutch
    • French
    • German
    • Italian
    • Portuguese
    • Russian
    • Spanish
    • Swedish
  • Community Contributions
    • Ember for Emby
    • Fan Art & Videos
    • Tools and Utilities
    • Web App CSS
  • Other
    • General Discussion
    • Developer API
    • Hardware
    • Media Clubs
    • Legacy Support

Blogs

  • Emby Blog

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Found 15 results

  1. As the title implies , the Remote (WAN) access doesnt work for me .After some searches , i found this article and followed everything mentioned in there - https://support.emby.media/support/solutions/articles/44001849007-connectivity . 1) Firstly the In-Home ( LAN ) access is working fine , no issues there 2) I made sure that the ip address showing up in WAN access is indeed the correct one . wget -qO- ifconfig.me/ip This when ran inside terminal does returns the same ip mentioned in WAN Access so thats fine as far as i can tell. 3) Lastly i did setup port forwarding on my tp link router . In Forwarding - i added a virtual server as follows : Service Port - 8096 Internal Port - 8096 IP Address - "Added my In-Home LAN access IP here" (192.xx.xx.x) Protocol - TCP ( options available - TCP ,UDP and All ) Common Service Port - "left blank" ( options available - DNS, FTP, GOPHER, HTTP, NNTP, POP3, PPTP, SMTP, SOCK, TELNET ) 4) I did checked if port 8096 is opened according to https://canyouseeme.org It outputs the below error : Error: I could not see your service on XXX.XX.XX.XX on port (8096) Reason: Connection timed out The IP address showing in canyouseeme.org is also the very same ip showing alongside in wan access in emby dashboard which again is same with my actual external ip ( I don't think issue is with IP mismatch in any way ) PS / This is my first time using any media server at all so i haven't tried WAN access on any different media server ,to be able to tell if it works with some different service . In my laptop ,i am connected to the internet through my home wifi . I haven't up any proxy , vpn or firewall in my machine locally or at router level . In fact just of curiosity - being connected to the very same wifi network in my android device. I tried emby server for android app and started emby server from there but wan access is still not working OS - Arch Linux ( x86_64) Emby Server v4.4.3.0
  2. So, I've taken the plunge. After years of running Emby on Windows, I've decided to create a Linux VM to be a dedicated Emby server. I chose and successfully installed CentOS 8 on my newly minted ESXi host, and got Emby installed using the instructions on the install page https://emby.media/linux-server.html with limited difficulties. A few maddening hours later fighting with Samba and Windows 10 TLS incompatibilities and after finally getting my remote SMB shares mapped to a local mount point with the appropriate permissions in place, I created my first media library. Success! Amazing! Everything working perfectly. Until I switched from my VM to my main PC's browser. Nothing. Nada. Zip. Zilch. The big zero. Situation is this. I've got default Emby port settings, and using FireFox inside the VM, I can connect to Emby server using IP:8096 or localhost:8096. The correct IP address and port shows up on the Emby Dashboard under "In-Home (LAN) access", but none of my other machines (on the same class c subnet, btw) can see the new CentOS Emby server. Using a port scanner, I do not see 8096 as an open port on that machine. The same scanner does see port 8096 open on my Windows Emby server. Now, I know that port is open, at least on the loopback adapter, because Emby is working just fine using a browser on the Emby Server machine, just can't get to it externally. After multiple attempts at changing settings on the Network page and restarting Emby Server with no luck, I started looking at networking. At one reference, I found the command "netstat -na | grep <port>" to find out of there was anything listening on a port, so I tried, and got this: tcp6 0 0 :::8096 :::* LISTEN tcp6 0 0 ::1:41350 ::1:8096 ESTABLISHED tcp6 0 0 ::1:8096 ::1:41350 ESTABLISHED Now, I'm more of an old-school networking guy, but I *think* this means that Emby has set itself up in the OS to listen to IPv6 ports only? maybe? As I said above, the Emby Dashboard shows the correct IP address and port for internal...the correct IPv4 address. I tried using the IPv6 address in my main machine's browser to verify, but was unable to get that to work. Pinging by IPv6 works, so At this point, I'm at an impasse. Not sure how to proceed from here, so any help/pointers/RTFM would be greatly appreciated.
  3. Ok this is going to be a long post. In this thread I will show you 2 different ways in which I setup a HTTPS connection to my emby server. Both ways require a certificate which again I will show you how i got mine using Lets Encrypt on Windows. I will break the posts up into Sections. Part.1 - Setting up a DDNS (Dynamic DNS host) Only require if you ISP IP is dynamic i.e. changes. Part.1.A - Setting Up DDNS using your own Domain Name Part.2 - Getting a Domain Name (Optional but looks fancier) Part.3 - Getting a SSL Cert from Lets Encrypt the easy way. Part 3a - Using LE.exe to get Certificates (recommended) Part.4 - Setting up HTTPS by changing default port to 443 Part.5 - Setting up HTTPS using reverse proxy
  4. cyphershadow

    ANSWERED TCPWrapper out of no where.

    Afternoon all, I have an unusual issue that just surfaced in the last couple days. Everything on my server was working fine, but all of a sudden this morning the Emby HTTPS port is showing as being tcpwrapped, and is blocking all connection attempts. This is occurring on the internal network, and only for the Emby service. No other services on the underlying QNAP are being affected. No changes to the underlying QNAP TS-451 unit were made, and no changes to the Emby server were made within the last two weeks. The problem persists only on the Emby HTTPS port, and the issue moves to any new HTTPS port that is designated, and persists full reboots of the server and the QNAP. I even rolled the QNAP firmware back to the prior release that was confirmed working, and the issue is persisting. This leads me to believe it may be an issue within the Emby server itself. Were any form of Access Control or tcpwrapping features recently integrated on the back end, and if so is there a way to whitelist? I see in the server logs over the HTTP interface that Dlna, StudioImages, and Port Mapper were updated over the last couple of days, but the problem has remained even after rooming these plugins. So I'm scratching my head here. Any thoughts?
  5. anderbytes

    Emby isn't closing used network ports.

    Hello guys, I guess I've found a nasty bug that can degrade overall Emby performance. Server: v3.0.5821 (latest stable) I accidentaly found that in some cases the ports that Emby use to allow clients connections aren`t closed as it should, after being used. Today by morning I was trying to access the WebClient interface... and it wouldn`t connect at all...at didn't returned any error, either. I confirmed that 8096 and 8920 were been listened by Emby, and both server and client were correctly connected to internal network. So... after some diagnose, I discovered that several connections were estabilished. I used the command netstat -anoe | grep ":8" in my server. While one TV was using the direct streaming, I couldn't confirm it was normal or not (strange, at most). When restarted the server, the open ports cleared, and I could connect again. Now, several hours later, with no TV or AndroidApp or Theater connected. I ran the same command and confirmed my worries: tcp 0 0 0.0.0.0:8096 0.0.0.0:* LISTEN 116 312514 off (0.00/0/0) tcp 0 0 0.0.0.0:8920 0.0.0.0:* LISTEN 116 312515 off (0.00/0/0) tcp 0 0 192.168.0.4:8096 192.168.0.101:60651 ESTABLISHED 116 316922 off (0.00/0/0) tcp 0 0 192.168.0.4:8096 192.168.0.4:53790 ESTABLISHED 116 379329 off (0.00/0/0) tcp 0 0 192.168.0.4:8096 192.168.0.107:36751 ESTABLISHED 116 307935 off (0.00/0/0) tcp 0 0 192.168.0.4:8096 192.168.0.101:43291 ESTABLISHED 116 350878 off (0.00/0/0) tcp 0 0 192.168.0.4:8096 192.168.0.107:36766 ESTABLISHED 116 312806 off (0.00/0/0) tcp 0 0 192.168.0.4:53790 192.168.0.4:8096 ESTABLISHED 116 378719 off (0.00/0/0) Not even IP .101 or .107 are online anymore since 12pm (4 hours agora). But their used ports are still opened and using O.S. resources. Can anyone reproduce this? Are server logs necessary? I'm not fond of distributing logs for every reason, as I'm paranoic about security. UPDATE: I noticed that every time I refresh the webgui (F5 in browser), it opens new ports and doesn`t closed the others, keeping the ESTABILISHED status working 4ever :-(((( UPDATE 2: After closing the browser, all connections get closed. Well... okay for now. But I forgot to tell one thing. IPs .101 and .107 above were respectively an Android Emby App and a Samsung Emby App.
  6. I am having trouble accessing my Emby server from outside my network. I have opened ports on router and Windows firewall. Is it my computer not being up to specs? The computer specs: AMD Vision CPU Toshiba Satellite All Realtek Drivers Please and Thank you!
  7. How to secure Emby using LetsEncrypt and Nginx Reverse Proxy by modifying Docker containers in Openmediavault. https://youtu.be/jYoDyoH2C0A
  8. h1smajesty

    Issues connecting

    Hello, I set up my emby server recently and immediately ran into the "We're unable to connect to the selected server right now" error message. I googled around, made sure my firewall had these ports open. The real problem was what I feared most: my university has all of the incoming ports closed. I can stream between devices on the same network, but can't stream between different networks (e.g. Uni wifi and Uni LAN). They don't allow port forwarding im pretty sure, but what I am really confused about is that it worked when I tried connecting my server/pc to the internet through NordVPN. That was a few days ago, and I have since been unable to reconnect, but I am pretty sure the connection was from Lan to wifi, so cross-network streaming. Why did it work? Weren't the ports still closed within the university network even with the VPN? Did I hallucinate streaming those 3 episodes of 30 rock? If the VPN did allow to bypass my university restriction somehow, do I have to manually check all their servers to find the right one now (they dont support port forwarding I think)? Very new to servers and port forwarding in general, maybe I missed something. Thanks in advance!!
  9. Hi, i just created my server today, got emby installed and it just wont work when putting the ip address in my browser (Mobile) while connected to mobile data. Internal works fine. I have tried unblocking ports on my Asus Router and TalkTalk modem +the ports on the server 2012 firewall but still no connections (I also tried with a friend and he couldn't get in either. Is there something i am missing?
  10. Any ideas why this might be happening? I cant find that Emby even uses this port. I am using defaults. From my server.txt: 2017-01-05 00:42:18.6076 Error PortMapper: Error creating port map: One or more errors occurred. 2017-01-05 00:42:18.6076 Error HttpClient: Error getting response from http://192.168.1.1:5555 *** Error Report *** Version: 3.1.2.0 Command line: C:\Users\media\AppData\Roaming\Emby-Server\System\MediaBrowser.ServerApplication.exe Operating system: Microsoft Windows NT 6.1.7601 Service Pack 1 64-Bit OS: True 64-Bit Process: True Processor count: 12 Program data path: C:\Users\media\AppData\Roaming\Emby-Server Application directory: C:\Users\media\AppData\Roaming\Emby-Server\System System.AggregateException: One or more errors occurred. ---> System.Net.WebException: The remote server returned an error: (500) Internal Server Error. at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization) --- End of inner exception stack trace --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Emby.Common.Implementations.HttpClientManager.HttpClientManager.<SendAsyncInternal>d__20.MoveNext() ---> (Inner Exception #0) System.Net.WebException: The remote server returned an error: (500) Internal Server Error. at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)<--- System.AggregateException at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Emby.Common.Implementations.HttpClientManager.HttpClientManager.<SendAsyncInternal>d__20.MoveNext() InnerException: System.Net.WebException System.Net.WebException: The remote server returned an error: (500) Internal Server Error. at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization) at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization) 2017-01-05 00:42:18.6076 Error PortMapper: Error creating port map: One or more errors occurred.
  11. Hi, Just updated the media/emby-server port to 3.1.0, and the server keeps throwing an unhandled exception when starting (find the logs attached). Reverted back to 3.0.8500 in the meantime as that one works fine (server-63617782744 (8500 old success).txt). 2016-12-19 21:51:42.8663 Error App: LoaderException: Could not resolve type with token 0100005f 2016-12-19 21:51:42.8696 Error App: LoaderException: Could not load file or assembly or one of its dependencies. 2016-12-19 21:51:42.8696 Error App: LoaderException: Could not load file or assembly or one of its dependencies. 2016-12-19 21:51:42.8696 Error App: LoaderException: Could not load file or assembly or one of its dependencies. 2016-12-19 21:51:42.8696 Error App: LoaderException: Could not resolve type with token 01000128 2016-12-19 21:51:42.8696 Error App: LoaderException: Could not load file or assembly or one of its dependencies. 2016-12-19 21:51:44.4754 Error ServerManager: Error starting Http Server *** Error Report *** Version: 3.1.0.0 Command line: /usr/local/lib/emby-server/MediaBrowser.Server.Mono.exe -ffmpeg /usr/local/bin/ffmpeg -ffprobe /usr/local/bin/ffprobe -programdata /var/db/emby-server Operating system: Unix 10.3.0.0 64-Bit OS: True 64-Bit Process: True Mono: 4.6.2 (Stable 4.6.2.7/08fd525 Mon Nov 28 22:44:12 UTC 2016) Processor count: 12 Program data path: /var/db/emby-server Application directory: /usr/local/lib/emby-server System.AggregateException: One or more errors occurred. ---> MediaBrowser.Model.Net.SocketCreateException: ProtocolNotSupported ---> System.Net.Sockets.SocketException: Protocol not supported at System.Net.Sockets.Socket..ctor (System.Net.Sockets.AddressFamily addressFamily, System.Net.Sockets.SocketType socketType, System.Net.Sockets.ProtocolType protocolType) [0x0005d] in <bd46d4d4f7964dfa9beea098499ab597>:0 at Emby.Common.Implementations.Net.SocketFactory.CreateSocket (MediaBrowser.Model.Net.IpAddressFamily family, MediaBrowser.Model.Net.SocketType socketType, MediaBrowser.Model.Net.ProtocolType protocolType, System.Boolean dualMode) [0x00000] in <9922445e90a448f2a17d005b1cc33d56>:0 --- End of inner exception stack trace --- at Emby.Common.Implementations.Net.SocketFactory.CreateSocket (MediaBrowser.Model.Net.IpAddressFamily family, MediaBrowser.Model.Net.SocketType socketType, MediaBrowser.Model.Net.ProtocolType protocolType, System.Boolean dualMode) [0x00047] in <9922445e90a448f2a17d005b1cc33d56>:0 at SocketHttpListener.Net.EndPointListener.CreateSocket () [0x00017] in <5e2146744a844faab36e869c2bc89d0d>:0 --- End of inner exception stack trace --- at System.Threading.Tasks.Task.ThrowIfExceptional (System.Boolean includeTaskCanceledExceptions) [0x00014] in <8f2c484307284b51944a1a13a14c0266>:0 at System.Threading.Tasks.Task`1[TResult].GetResultCore (System.Boolean waitCompletionNotification) [0x00034] in <8f2c484307284b51944a1a13a14c0266>:0 at System.Threading.Tasks.Task`1[TResult].get_Result () [0x0000b] in <8f2c484307284b51944a1a13a14c0266>:0 at SocketHttpListener.Net.EndPointManager.AddPrefixInternal (MediaBrowser.Model.Logging.ILogger logger, System.String p, SocketHttpListener.Net.HttpListener listener) [0x0006a] in <5e2146744a844faab36e869c2bc89d0d>:0 at SocketHttpListener.Net.EndPointManager.AddListener (MediaBrowser.Model.Logging.ILogger logger, SocketHttpListener.Net.HttpListener listener) [0x00030] in <5e2146744a844faab36e869c2bc89d0d>:0 ---> (Inner Exception #0) MediaBrowser.Model.Net.SocketCreateException: ProtocolNotSupported ---> System.Net.Sockets.SocketException: Protocol not supported at System.Net.Sockets.Socket..ctor (System.Net.Sockets.AddressFamily addressFamily, System.Net.Sockets.SocketType socketType, System.Net.Sockets.ProtocolType protocolType) [0x0005d] in <bd46d4d4f7964dfa9beea098499ab597>:0 at Emby.Common.Implementations.Net.SocketFactory.CreateSocket (MediaBrowser.Model.Net.IpAddressFamily family, MediaBrowser.Model.Net.SocketType socketType, MediaBrowser.Model.Net.ProtocolType protocolType, System.Boolean dualMode) [0x00000] in <9922445e90a448f2a17d005b1cc33d56>:0 --- End of inner exception stack trace --- at Emby.Common.Implementations.Net.SocketFactory.CreateSocket (MediaBrowser.Model.Net.IpAddressFamily family, MediaBrowser.Model.Net.SocketType socketType, MediaBrowser.Model.Net.ProtocolType protocolType, System.Boolean dualMode) [0x00047] in <9922445e90a448f2a17d005b1cc33d56>:0 at SocketHttpListener.Net.EndPointListener.CreateSocket () [0x00017] in <5e2146744a844faab36e869c2bc89d0d>:0 <--- Anything I can do to fix this? Is everyone else also experiencing this problem? Thank you server-63617781102.txt unhandled_abcf3070-649e-4189-a769-b1c2efb9e65e.txt server-63617782744 (8500 old success).txt
  12. I've noticed an odd occurence with my emby server. Which is running on Ubuntu server 16.10. It seems fine for days, then suddenly you can't connect to it remotely via the app or web. It says server may be offline. Well, if I log into the server from home, it shows as being active for a week or two weeks, for example. If I try to select the remote link in the manager server window however, it won't come up. But, of course, the service shows up locally no problem. I've tried finding anything in the logs, but nothing seems out of place. I've been into my router and nothing is seemingly blocking those ports. I just am at a loss as to why the remote access decides to drop every so often. I could be watching it on break at work for days, then suddenly, it's unavailable. Any ideas where I can go with this? It seems restarting the service fixes it.
  13. ThermoDust

    [Portable Edition] DLNA Ports

    What ports need to be opened for the DLNA discovery and streaming to work? PS - I guess a secondary question would be work ports in general does Emby need opened to be fully functional?
  14. GurtLushSalmon

    Conection Issue at college

    Connection issues at college Hello everyone I am having some issues with connecting to my emby server running on freenas from college. It works fine through other public networks. I am not sure if the college is blocking the traffic from port 8888, but does anyone have a possible work around. I have tried using the default port (8096) and it does not work form college either. Feel free to test it gurtlushsalmon.ddns.net:8888 I would be grateful for any support Thanks
  15. Hi all, First of all thanks for a fantastic piece of software and also to those of you who have helped develop such excellent plugins. I am having two problems, one of which I suspect is not due my MB3 client or server. Having said that, this is such a helpful forum I was hoping someone with a bit more technical knowledge might be able to steer me in the right direction. My setup is a Windows 8.1 machine plugged into my TV with WMC, ServerWMC, the MB3 server and Media Browser Classic installed on it. I also sometimes access my MB3 content via a web browser or the android app. I have two issues. 1. I am able to access my MB3 server from windows laptops (via web browser) and android devices (via app) on my local wireless network but not remotely. I think this is because I have not managed to open port 8096 correctly. I have run a test on canyouseeme.org and the port appears to be closed. Initially I thought the problem was because I had a netgear r7000 router running behind a billion 7800N router/modem but I have since put the Billion in bridge mode and attempted to open the port in the netgear settings but it doesn't seem to have worked. I have tried to diagnose and solve this with internet searches but I am at a loose end. 2. I am able to watch live TV in WMC but every 4 hours I get a "Refresh Guide failed" message on my dashboard stating "connected host failed to respond 10.0.0.2:9080". I suspect that there is a problem with myLive TV settings as my ServerWMC is not located on the device at 10.0.0.2. However, I have looked in the LIVE TV settings on my WM3 dashboard and can't seem to find a way to change it. I am not very proficient with computers, I just try to educate myself online and muddle my way through. Reinstalling my MB3 server did not help. Any advice would be greatly appreciated. Thanks, Lof
×
×
  • Create New...