Remote Access Intermittent

[dalezjc 14]

I'm having intermittent remote access to my Emby server.  Sometimes it works flawlessly, and other times I can't connect at all, and other times it works for about 10 minutes, then drops.  Here's the log. 

 

2022-12-01 00:09:16.279 Error PortMapper: Error in GetSpecificMappingAsync
    *** Error Report ***
    Version: 4.7.10.0
    Command line: C:\Users\xyz\AppData\Roaming\Emby-Server\system\EmbyServer.dll -noautorunwebapp
    Operating system: Microsoft Windows 10.0.19044
    Framework: .NET 6.0.10
    OS/Process: x64/x64
    Runtime: C:/Users/xyx/AppData/Roaming/Emby-Server/system/System.Private.CoreLib.dll
    Processor count: 8
    Data path: C:\Users\xyz\AppData\Roaming\Emby-Server\programdata
    Application path: C:\Users\xyz\AppData\Roaming\Emby-Server\system
    System.Net.Http.HttpRequestException: System.Net.Http.HttpRequestException: An error occurred while sending the request.
     ---> System.IO.IOException: The response ended prematurely.
       at System.Net.Http.HttpConnection.SendAsyncCore(HttpRequestMessage request, Boolean async, CancellationToken cancellationToken)
       --- End of inner exception stack trace ---
       at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsyncInternal(HttpRequestOptions options, String httpMethod)
       at Emby.Server.Implementations.HttpClientManager.CoreHttpClientManager.SendAsync(HttpRequestOptions options, String httpMethod)
       at Mono.Nat.Upnp.UpnpNatDevice.GetSpecificMappingAsync(Protocol protocol, Int32 publicPort, CancellationToken cancellationToken)
       at Mono.Nat.Upnp.UpnpNatDevice.CreatePortMap(Mapping mapping, CancellationToken cancellationToken)
    Source: Emby.Server.Implementations
    TargetSite: Void MoveNext()
    InnerException: System.IO.IOException: The response ended prematurely.
    Source: System.Net.Http
    TargetSite: Void MoveNext()

[rbjtech 5284]

If you are using manual port forwarding on your router,  then make sure you are not using port triggering,  that is not the same as port forwarding and will result in connections being dropped after a defined peroid unless re-requested.

Port forwarding is an unconditional forward.

If that is ok,  then its likely to be your isp or general setup (lan, wifi etc),  as emby as a web server is very stable.

Edited December 2, 2022 by rbjtech

[dalezjc 14]

I'm using Xfinity as my ISP,  and I don't see the option for Port Triggering, so I assume that's not the problem.  I'm also trying to migrate from Plex to Emby because Emby has much more functionality that I need, but to be fair, Plex's remote access is extremely reliable.  It just works, and I've never had a drop-out issue.

[rbjtech 5284]

The setup will be on your own router.  Have a look at the remote access setup guides in the knowledgebase.

But if plex was working reliably, then so should emby - they ultimately use the same delivery method to serve the media.

 

https://support.emby.media/support/solutions/articles/44002137137-remote-setup

Edited December 2, 2022 by rbjtech

[Luke 42078]

Actually Plex has a relay service that they kick in automatically whenever a device can't reach your server directly, they route everything through their own server in order to make things just work.

As we put the emphasis on private media server we don't have any plans to do something like that, so it does that you'll need to be able to configure remote access in your router.

[dalezjc 14]

Xfinity support looked at the router settings, and all looks good.   I'll reboot the router and see if things change.

[rbjtech 5284]

1 hour ago, dalezjc said:

Xfinity support looked at the router settings, and all looks good.   I'll reboot the router and see if things change.

Unless it's configured correctly specifically for emby - then issues may persist.   Assuming they are your ISP - they will just be concerned is data getting to your router - if yes, then they have no interest in what happens to it after that - ie, you wanting it forwarded to your emby server ...

Maybe take a look at the link I posted above - it will give you a guide on what to check / configure etc.

[dalezjc 14]

Yes, I looked at the link, but it's pretty generic, and everything is configured per the directions.

[Happy2Play 9780]

Per the original post the question would be are you depending on Port Mapper or manually configured port forwarding?  As that error is related to automatic port mapping.

 

 

[Luke 42078]

@dalezjc have you configured port forwarding in your router? if so, what exactly did you configure? Thanks !

[dalezjc 14]

10 hours ago, Luke said:

@dalezjc have you configured port forwarding in your router? if so, what exactly did you configure? Thanks !

Yes I did.  After rebooting the router, the intermittent problem persists.

[visproduction 315]

Dal,

Luke was asking what exactly you put in your router port forwarding configuration.  You can configure it wrong.  The info to this is not in your data log above.  

[dalezjc 14]

Here's a screenshot of the port forward info:

 

 

[rbjtech 5284]

if your emby server is 10.0.0.136 - then that should be ok.
Plex is on 10.0.0.83 - either a different machine or different IP yes ?

 

[dalezjc 14]

Yes, my Emby server is .136.

[rbjtech 5284]

ok - can you use canyouseeme.org from a mobile/4g signal (not wifi - turn that off) to check to see if the emby server is listening?

If not, then temporarily disable the windows/os firewall and try again.

[dalezjc 14]

I can see it's listening from canyouseeme.org, plus here's the output from a netstat command:

 

netstat -ano | find ":8096"
  TCP    0.0.0.0:8096           0.0.0.0:0              LISTENING       17060
  TCP    127.0.0.1:8096         127.0.0.1:51597        ESTABLISHED     17060
  TCP    127.0.0.1:8096         127.0.0.1:62030        ESTABLISHED     17060
  TCP    127.0.0.1:8096         127.0.0.1:62074        ESTABLISHED     17060
  TCP    127.0.0.1:8096         127.0.0.1:62075        ESTABLISHED     17060
  TCP    127.0.0.1:51597        127.0.0.1:8096         ESTABLISHED     5380
  TCP    127.0.0.1:62030        127.0.0.1:8096         ESTABLISHED     5380
  TCP    127.0.0.1:62031        127.0.0.1:8096         TIME_WAIT       0
  TCP    127.0.0.1:62074        127.0.0.1:8096         ESTABLISHED     5380
  TCP    127.0.0.1:62075        127.0.0.1:8096         ESTABLISHED     5380
  TCP    127.0.0.1:62076        127.0.0.1:8096         TIME_WAIT       0
  TCP    [::]:8096              [::]:0                 LISTENING       17060

 

[rbjtech 5284]

ok - so connectivity looks fine to me.

Unfortunately, I'm out of ideas - all that is left is your ISP provider ..

[pwhodges 2012]

Can you confirm that local connectivity is completely reliable?

Paul

[dalezjc 14]

56 minutes ago, pwhodges said:

Can you confirm that local connectivity is completely reliable?

Paul

Not sure what else to do.  As I said above, Plex works flawlessly remotely, so there's that.  Also, I *really* like the functionality of Emby, and I use it exclusively at home, and would love to make it my primary media server. 

I tried it again on the drive to work yesterday,  which takes about 20 minutes.  Emby worked initially for about 10 minutes, then dropped.  It took about 2 minutes, then reconnected again, and then worked for about 5 minutes, then dropped.  Reconnected again after about a minute or so, then worked for about a minute or so.  Completely frustrating.

[rbjtech 5284]

6 minutes ago, dalezjc said:

Not sure what else to do.  As I said above, Plex works flawlessly remotely, so there's that.  Also, I *really* like the functionality of Emby, and I use it exclusively at home, and would love to make it my primary media server. 

I tried it again on the drive to work yesterday,  which takes about 20 minutes.  Emby worked initially for about 10 minutes, then dropped.  It took about 2 minutes, then reconnected again, and then worked for about 5 minutes, then dropped.  Reconnected again after about a minute or so, then worked for about a minute or so.  Completely frustrating.

Presumably this is over a 4G/5G remote connection ?

If yes, then as Emby does not currently do adaptive streaming (I didn't think Plex did that either tbh..) then maybe try lowering the Emby Client/App down to it's lowest acceptable quality setting (likely 1Mbit/sec) and then start raising it to see at what point it 'breaks'.  Once you have the max/min - then try something in the middle and see if it maintains a reliable connection ?

Edited December 7, 2022 by rbjtech

[dalezjc 14]

37 minutes ago, rbjtech said:

Presumably this is over a 4G/5G remote connection ?

If yes, then as Emby does not currently do adaptive streaming (I didn't think Plex did that either tbh..) then maybe try lowering the Emby Client/App down to it's lowest acceptable quality setting (likely 1Mbit/sec) and then start raising it to see at what point it 'breaks'.  Once you have the max/min - then try something in the middle and see if it maintains a reliable connection ?

Thanks for the suggestion.  I'll start at 1Mbit/sec.  BTW, what is the default setting?

[rbjtech 5284]

1 hour ago, dalezjc said:

Thanks for the suggestion.  I'll start at 1Mbit/sec.  BTW, what is the default setting?

It will default to Auto - and use whatever the connection is when you start the stream - it is a one off operation. It does not analyse the connection again during that playback session (ie it does not do adaptive streaming).  The issue with this of course is if you are in a high signal area when it first does this - the bitrate gets set high and as you move into a low signal area, the bitrate cannot keep up with demand.   But if you set it at the lowest across the typical journey - then it maintains the buffer and thus works as intended.

Edited December 7, 2022 by rbjtech

[Luke 42078]

On 12/5/2022 at 3:47 PM, dalezjc said:

Yes, my Emby server is .136.

Is this a different machine then Plex?

[dalezjc 14]

No, they're on the same machine.