What is port 2189 used for?

[brando56894 6]

What does Emby use port 2189 for? I keep getting errors in the server log that says "error getting response from 192.168.1.1:2189". I'm running pfSense as my router, it's IP is 192.168.1.1, and I have UPNP enabled and it works because it setups up the mapping for Emby's HTTP and HTTPS ports so I have no idea what 2189 is used for. Videos play correctly and the web interface works so it seems like it's nothing essential. I have report https as external address set, left the ports at their default and bound my IP (192.168.1.7) to it, I also set the external domain to emby.brandon.us, since I'm running Nginx on the same machine and I'm using it to serve sites and using it as a reverse proxy for Emby, among other things. It doesn't seem to be working with Emby Connect since whenever I login from within one of the Emby apps the first time it says "No Servers Found" and I have to enter in the FQDN for it and set the port to 443, then it lets me right in.

 

The reason why I decided to use a reverse proxy instead of changing the external ports is because when I set the external port to 443 I believe it would no longer let me access the GUI and I ended up having to reinstall it because everything seemed to be FUBAR, so on the next install I left the ports as they were and just piped it though Nginx.

 

Here's the config:

 

server {

 

    listen 443 ssl;

    server_name emby.brandon.us;

 

    error_log /var/log/nginx/emby/ssl-error.log info;

    access_log /var/log/nginx/emby/ssl-access.log;

 

    ssl_certificate /etc/letsencrypt/live/brandon.us/fullchain.pem;

    ssl_certificate_key /etc/letsencrypt/live/brandon.us/privkey.pem;

 

    location / {

 

        proxy_pass http://192.168.1.7:8096;

        proxy_set_header Host $host;

        proxy_set_header X-Real-IP $remote_addr;

        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;

    }

 

}

 

server {

 

    listen 80;

    server_name stats.brandon.us;

    return 301 https://$host$request_uri;

}

 

Also it seems that the redirect from 80 to 443 doesn't work sometimes, and you have to specify HTTPS to get it to work, IDK if that's an issue with Emby or Nginx.

 

Here's the backtrace

2016-12-27 19:54:42.0102 Error HttpClient: Error getting response from http://192.168.1.1:2189    *** Error Report ***
    Version: 3.1.1.0
    Command line: /usr/lib/emby-server/MediaBrowser.Server.Mono.exe -programdata /var/lib/emby -ffmpeg /usr/bin/ffmpeg -ffprobe /usr/bin/ffprobe
    Operating system: Unix 4.4.39.1
    64-Bit OS: True
    64-Bit Process: True
    Mono: 4.6.1 (Stable 4.6.1.3/abb06f1 Mon Oct 3 07:51:42 UTC 2016)
    Processor count: 16
    Program data path: /var/lib/emby
    Application directory: /usr/lib/emby-server
    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 (System.IAsyncResult asyncResult) [0x00064] in <6c7c03f48a9747c8a644da4f63a34480>:0
     at System.Threading.Tasks.TaskFactory`1[TResult].FromAsyncCoreLogic (System.IAsyncResult iar, System.Func`2[T,TResult] endFunction, System.Action`1[T] endAction, System.Threading.Tasks.Task`1[TResult] promise, System.Boolean requiresSynchronization) [0x00014] in <dca3b561b8ad4f9fb10141d81b39ff45>:0
     --- End of inner exception stack trace ---
     at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <dca3b561b8ad4f9fb10141d81b39ff45>:0
     at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in <dca3b561b8ad4f9fb10141d81b39ff45>:0
     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in <dca3b561b8ad4f9fb10141d81b39ff45>:0
     at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in <dca3b561b8ad4f9fb10141d81b39ff45>:0
     at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in <dca3b561b8ad4f9fb10141d81b39ff45>:0
     at Emby.Common.Implementations.HttpClientManager.HttpClientManager+<SendAsyncInternal>d__20.MoveNext () [0x003ff] in <9922445e90a448f2a17d005b1cc33d56>:0
    ---> (Inner Exception #0) System.Net.WebException: The remote server returned an error: (500) Internal Server Error.
     at System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) [0x00064] in <6c7c03f48a9747c8a644da4f63a34480>:0
     at System.Threading.Tasks.TaskFactory`1[TResult].FromAsyncCoreLogic (System.IAsyncResult iar, System.Func`2[T,TResult] endFunction, System.Action`1[T] endAction, System.Threading.Tasks.Task`1[TResult] promise, System.Boolean requiresSynchronization) [0x00014] in <dca3b561b8ad4f9fb10141d81b39ff45>:0 <---
    
    System.AggregateException
     at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x0000c] in <dca3b561b8ad4f9fb10141d81b39ff45>:0
     at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Threading.Tasks.Task task) [0x0004e] in <dca3b561b8ad4f9fb10141d81b39ff45>:0
     at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Threading.Tasks.Task task) [0x0002e] in <dca3b561b8ad4f9fb10141d81b39ff45>:0
     at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd (System.Threading.Tasks.Task task) [0x0000b] in <dca3b561b8ad4f9fb10141d81b39ff45>:0
     at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1+ConfiguredTaskAwaiter[TResult].GetResult () [0x00000] in <dca3b561b8ad4f9fb10141d81b39ff45>:0
     at Emby.Common.Implementations.HttpClientManager.HttpClientManager+<SendAsyncInternal>d__20.MoveNext () [0x003ff] in <9922445e90a448f2a17d005b1cc33d56>:0
    InnerException: System.Net.WebException
    System.Net.WebException: The remote server returned an error: (500) Internal Server Error.
     at System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) [0x00064] in <6c7c03f48a9747c8a644da4f63a34480>:0
     at System.Threading.Tasks.TaskFactory`1[TResult].FromAsyncCoreLogic (System.IAsyncResult iar, System.Func`2[T,TResult] endFunction, System.Action`1[T] endAction, System.Threading.Tasks.Task`1[TResult] promise, System.Boolean requiresSynchronization) [0x00014] in <dca3b561b8ad4f9fb10141d81b39ff45>:0
     at System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) [0x00064] in <6c7c03f48a9747c8a644da4f63a34480>:0
     at System.Threading.Tasks.TaskFactory`1[TResult].FromAsyncCoreLogic (System.IAsyncResult iar, System.Func`2[T,TResult] endFunction, System.Action`1[T] endAction, System.Threading.Tasks.Task`1[TResult] promise, System.Boolean requiresSynchronization) [0x00014] in <dca3b561b8ad4f9fb10141d81b39ff45>:0

I've also attached the full logs. 

 

Edit: I just did a port test in pfSense and it came back successful so IDK what the issue is

 

 

Port test to host: 192.168.1.1 Port: 2189 successful.

server-63618464771.txt

server-63618465277.txt

Edited December 28, 2016 by brando56894

[Luke 37272]

Hi, we don't use port 2189. This is coming from another device or upnp software on the machine. The server's dlna features and/or automatic port mapper discovered the device via upnp discovery and then proceeded to try and communicate with it.

[mastrmind11 717]

I noticed my logs getting spammed with the same error as of 3.1.0 but with port 45255.  I have DLNA disabled in Emby server, and nothing else installed on the box.  I do have automatic port mapping enabled.  This is new as of 3.1.  @@Luke, any idea how to suppress the error messages?  Just as OP stated, everything seems to function fine, I just don't like to see errors in my log.  Thanks

[Luke 37272]

The next release will reduce some of the log messages.

[brando56894 6]

I had DLNA enabled, but then I disabled it and the messages stopped for a few days but now they're back even though DLNA is disabled.

Edited January 2, 2017 by brando56894

[Luke 37272]

i think that might have been the automatic port mapper so you'd need to disable that as well under Advanced -> hosting. Please note that doing that may result in loss of connectivity when away from home. So you may need to configure your router to handle what the port mapper was doing for you.