Notice some errors with Trakt plugin and check plugin update job

[Luke 42077]

No because our domain requires https

[somy 25]

No because our domain requires https

 

Any possibility to manually update Trakt plugin?

[somy 25]

Things are getting worse. Today when I tried to edit metadata for a video the identify search function also stops working, it is not Emby.media this time:

2018-08-15 07:18:58.276 Error HttpClient: Connection to https://www.thetvdb.com/api/GetSeries.php?seriesname=Blue+planet+II&language=en timed out

MediaBrowser.Model.Net.HttpException: Cancelling connection to https://image.tmdb.org/t/p/original/qbSRu2qcEdKaR4QUv04DoWB61MC.jpg due to a previous timeout

 

Looks like my Emby installation lost connection to internet

Edited August 15, 2018 by somy

[Luke 42077]

@@PenkethBoy can you think of any configuration on the QNAP that could be causing this?

 

I think it is his VPN personally.

[somy 25]

@@PenkethBoy can you think of any configuration on the QNAP that could be causing this?

 

I think it is his VPN personally.

I just downgraded to 3.4.1 and everything works without any issue.

Something related to HTTPS must be changed in 3.5.X. 

 

Edit: I saw in the release notes of 3.5.0 there was a change "Disable older ssl protocols", could this be the cause?

Edited August 15, 2018 by somy

[PenkethBoy 2068]

Ok let's confirm a few things first

 

What QNAP NAS do you have?

What QNAP firmware are you running on? - number and date

 

Can you list ALL the packages you have installed on your NAS

 

Do you have QNAP DLNA enabled?

 

What are you using for your VPN?

 

Have you changed the ssl config at all?

[somy 25]

Ok let's confirm a few things first

 

What QNAP NAS do you have?

What QNAP firmware are you running on? - number and date

 

Can you list ALL the packages you have installed on your NAS

 

Do you have QNAP DLNA enabled?

 

What are you using for your VPN?

 

Have you changed the ssl config at all?

Hi, thanks for helping! Please see my answers below:

1) Qnap TS-453mini with 8G memory

2) Firmware version 4.3.4.0644 (latest)

3) Please see the attached image

4) Yes, I enabled the build-in QNAP media feature

5) VPN is for occasionally access home network from work, in 99% time there is no VPN connection

6) Not manually, the server runs Let's Encrypt certificate 

More info on this:

1) The issue seems to start from July as last trakt update was from July

2) I tried to disable VPN and restart app, it didn't help

3) I tried to downgrade Emby to 3.4.1, which works without problem

4) I had one firmware upgrade recently (can't remember when exactly), not sure if the problem starts with that

 

[PenkethBoy 2068]

Ok

 

1. Shutdown all the "Stations" looks like 7 of them

2. shutdown media-streaming addon

3. shutdown happyget 2

4. shutdown qtransmission

 

If shutdown QVPN does not change things - unistall it and see if 3.5.2 works ok without it installed

 

do you have DLNA enabled on your NAS (not the Emby one)

[somy 25]

Ok

 

1. Shutdown all the "Stations" looks like 7 of them

2. shutdown media-streaming addon

3. shutdown happyget 2

4. shutdown qtransmission

 

If shutdown QVPN does not change things - unistall it and see if 3.5.2 works ok without it installed

 

do you have DLNA enabled on your NAS (not the Emby one)

 

Yes, I do have DLNA enabled, I will disable that as well.

[somy 25]

Ok

 

1. Shutdown all the "Stations" looks like 7 of them

2. shutdown media-streaming addon

3. shutdown happyget 2

4. shutdown qtransmission

 

If shutdown QVPN does not change things - unistall it and see if 3.5.2 works ok without it installed

 

do you have DLNA enabled on your NAS (not the Emby one)

 

Just did the test:

1) Stop all 7 stations

2) Stop media streaming addon

3) Stop happyget 2 and transmission

4) Disable DLNA

5) Uninstall QVPN

6) Stop emby and install EMby 3.5.2

 

Unfortunately same problem. What's next? What change in 3.5.X could potentially cause HTTPS connection issue?

[PenkethBoy 2068]

have you installed your own ssl certificate?

 

you missed video station

[somy 25]

Tried to disable video station as well, same problem. :-(

[PenkethBoy 2068]

have you installed your own ssl certificate?

[somy 25]

 

have you installed your own ssl certificate?

 

 

Hi, I use "QTS SSL Certificate" app which installs Let's Encrypt certificate for NAS. I have a daily job that convert the QNAP format to pfx format which is used in Emby.

I don't think I have anything installed by myself though.

[PenkethBoy 2068]

I wonder if the conversion is the issue and Emby does not like the file produced or its corrupt etc

 

Cant help with that - somebody else will have to chip in

[somy 25]

I wonder if the conversion is the issue and Emby does not like the file produced or its corrupt etc

 

Cant help with that - somebody else will have to chip in

Hi, the conversion doesn't touch the original Let's Encrypt certificate, rather it generates a new pfx file which is then configured in Emby for HTTPS.

Not sure if the cert is used for outgoing ssl connections though. 

[somy 25]

One more test I did: remove Emby, remove the EmbyServer completely, install a fresh version of 3.5.2, same result sadly

[Luke 42077]

Your ssl cert is not used for outgoing connections.

[somy 25]

Your ssl cert is not used for outgoing connections.

 

Ok, for now I will stick to version 3.4.1 until the issue is found and fixed in a later version.

 

Thanks for the help!

[somy 25]

Ok, just want to report I might find the cause.

It seems that it is related to IPv6 address resolved by the DNS server, and that explains why it works for some URL but not others.

Google DNS resolves emby.media to an IPv6 address, but the NAS seems to have problem connecting to IPv6, hence the problem.

Strangely it doesn't explain why 3.4.1 works but 3.5.2 doesn't.

Any suggestion? 

Edited August 23, 2018 by somy

[Luke 42077]

Could be due to some change in the netcore runtime. Well done.

[somy 25]

Unfortunately not able to find a solution, something in the kernel I guess - it is just super unstable, I made it work by recreating the 802.3ad Link aggregation, but now it stops working again.

[somy 25]

Hi there, please attach the emby server log, thanks.

Hi Luke, found this online, what version of .NetCore in 3.5.2:

https://github.com/dotnet/corefx/issues/29716

[Luke 42077]

2.1.2. yes that could be it.

[somy 25]

2.1.2. yes that could be it.

 

Ok, looks like they'll fix it in 3.0. I will have to keep the old version for a while I guess.

It is still unknown the root cause why IPv6 stops working from time to time. Will continue investigating.