Several issues with Emby server Live TV on Linux Mint

[loveridgem 1]

Hi,

I have installed the server using the Ubuntu instructions since Mint is an offshoot of Ubuntu.  I have purchased Emby Premiere in order to use my TV tuner which was setup with NextPVR and Kodi.  I have been wanting to move from Kodi since it seems to struggle with loading my library in a timely manner.  My install of Emby has working functionality of my movies, TV shows, home videos, photos, and music.  My issues arise with Live TV.

In trying to install the NextPVR plugin, I have issues loading the plugin catalog.  If I look in the logs, it's timing out.  Occasionally the catalog will load and I try to install the plugin.  It will come back every time with a timeout.  I know my Premiere is valid because it shows my end date for subscription and the logs show success.  The timeout is coming from: "GET https://www.mb3admin.com/admin/service/EmbyPackages.json".

So, I then try instead to use an m3u for my live TV and this works and I can see live TV.  In trying to set up the Emby Guide, I get a timeout there as well.  "There was an error downloading tv lineups"

in the logs: Connection to https://mb3admin.com/admin/service/registration/validate timed out

Going back to Emby Premeire and then look at the logs I see POST https://mb3admin.com/admin/service/registration/validate

This succeeds.  I want to get either NextPVR or m3u with Emby Guide to work.

What else do I need to provide to help with troubleshooting this issue?

Thanks, Mike

[Luke 42078]

HI there, can you please attach the emby server log?

How to Report a Problem

Thanks !

[loveridgem 1]

Hi,

I've attached my log file.  Many errors are happening.  What I tried to do was: 

1) Checked Emby Premiere status

2) Tried to set up Emby Guide data.

3) Tried to access the plugin Catalog

All failed.  The other errors in the log may all be due to the same issue I'm facing.

Thanks!

Mike

EDIT: Sorry, All did not fail.  #1 succeeds.

embyserver.txt

Edited March 9, 2023 by loveridgem
Error in statement

[Luke 42078]

OK yes all outgoing communications are timing out and failing, not just to our servers, but metadata providers as well. Typical causes of this are firewall, security software or VPN. Can you look into those?

[loveridgem 1]

OK, I have looked into this and I'm baffled and a bit confused.  I might need a bit of direction so I'm tackling the right problem the right way.  I disabled the firewall on the computer hosting the server.  No change.  I played around with adding a few port forwards on my router with no luck.  What confuses me is that on occasion, the plugin catalog will load.  If there was anything blocking it, it should always fail.  I've checked my router firewall logs to see if anything is getting blocked, and there is nothing incoming or outgoing getting blocked.

I do believe this to be a networking issue, but I'm unable to identify what's happening or who is preventing communication.  I did some looking for ports needing forwarding for Emby and I'm confused there too.  Port forwarding is to allow access in.  My router has a rule to allow all outward traffic so I should only need to create inward rules.  I created both LAN and WAN rules for 8096, 8920, and 8945.  It didn't help either.

Any guidance or direction where I should be focusing would really help me at this time.

Thanks!

Mike

[Luke 42078]

Quote

 I played around with adding a few port forwards on my router with no luck. 

In this case we're talking about outgoing requests from the server, not incoming, so the port forwarding doesn't come into play here.

You could also try disabling ipv6 in your router. I've seen a few reports of that helping in this situation.

[loveridgem 1]

Well that worked!  Turning off IPv6.  Now the question is: Why does that fix this and will there be work on this within Emby?  Mostly out of curiosity.

Thanks for your help!

Mike

[Luke 42078]

It seems to be an issue in the .NET networking layer. The next release of the server will update to a new .NET version and hopefully this workaround won't be needed anymore.