Jump to content

Recommended Posts

moviefan
Posted

After upgrading to 4.7.0.60 I was unable to connect over HTTPS to my system.  Received browser warning that session was not encrypted.  Couldn't find any way to proceed.  Downgraded back to 4.6.7 and issue went away.  Not sure what changed here in new version.

Happy2Play
Posted

Not seeing an issue witn my ssl connection test.

image.png.5481bd380da8d74c9934369e36e1b80e.png
 

Probably need to see the server log for 4.7.0.60.

Posted

There was some problem during the beta with Let's Encrypt certificates - currently on my smartphone and didn't find it quickly.

If he upgraded from stable to stable then he might be experiencing that.

Posted

Hi, yes, please attach the emby server log. Thanks.

moviefan
Posted

I don't have Let's Encrypt certificate.  Just a wildcard CA certificate that I paid for.

This looks like the log from when it was happening.

embyserver-63788385384.txt

Posted

it looks like you're using your web app over plain http. Try switching it to https instead.

moviefan
Posted

You're just seeing my connection that I manually used after HTTPS wasn't working.  I guess I will just wait for more to upgrade and see if anyone else reports this behavior.

Mookdog
Posted (edited)

I had a problem with the past beta run where my ssl wasnt working. I removed portmapper and forwarded the ports in my router and the problem was solved

 

Mook

Edited by Mookdog
Spell correction
Posted

I have the same issues.

4.6.7.0 https/ssl is OK.

4.7.0.60 https/ssl is not OK.

Certutil  "Encryption test passed".

Posted

I have the same issues. With 4.7.0.60 with a wildcard certificate

moviefan
Posted

Heh I came back to post more logs but seems like others are seeing this now.  I upgraded again and experienced the same issue.

Painkiller8818
Posted

I can't confirm any issues with 4.7.0.60 and my SSL.
I use Emby on Win 10

Everything seems ok, tested it with my android phone and chrome browser from outside my network

Painkiller8818
Posted
On 5/19/2022 at 12:34 AM, moviefan said:

@Painkiller8818Is your cert a wildcard or FQDN?

its a normal wildcard cert

moviefan
Posted

Thanks so same deal as me.

I am running on Windows 7; how about you?  What about others in this thread experiencing issue?

Painkiller8818
Posted
11 hours ago, moviefan said:

Thanks so same deal as me.

I am running on Windows 7; how about you?  What about others in this thread experiencing issue?

i am running win 10 as win7 isn't suported anymore from windows. 
Maybe you should do an inplace upgrade to win 10 and make it work again.

Q-Droid
Posted (edited)
13 hours ago, moviefan said:

Thanks so same deal as me.

I am running on Windows 7; how about you?  What about others in this thread experiencing issue?

This is useful info. The devs could answer but it's possible that the latest release removed cipher suites and/or protocols that Windows 7 was still relying on for the HTTPS connections. Maybe the new release can no longer fallback to those ciphers/protocols.

Edited by Q-Droid
moviefan
Posted
1 hour ago, Painkiller8818 said:

i am running win 10 as win7 isn't suported anymore from windows. 
Maybe you should do an inplace upgrade to win 10 and make it work again.

I'm not very inclined to upgrade operating systems unless we identify this as the reason it's not working.  @deccat & @Elsaya can you confirm the operating systems you're running?

Posted

I use also Windows 7. But I downgraded back to 4.6.7, because the Mediaportal Plugin has also changed. 

Posted

Hmm. I wonder if the updated .NET runtime and aspnetcore are requiring something not supported by the older version of windows.

  • Agree 1
moviefan
Posted
7 hours ago, Luke said:

Hmm. I wonder if the updated .NET runtime and aspnetcore are requiring something not supported by the older version of windows.

This would allow the program to run but just not support HTTPS?

Posted
Just now, moviefan said:

This would allow the program to run but just not support HTTPS?

If it's related to the tls version then possibly, yes, given that windows 7 doesn't support tls 1.2+. 

Posted
13 hours ago, moviefan said:

I'm not very inclined to upgrade operating systems unless we identify this as the reason it's not working.  @deccat & @Elsaya can you confirm the operating systems you're running?

 

I'm using Windows 10 as a server and finally solved the problem using a 3rd party reverse proxy.

Posted

 

You can use a reverse proxy such as nginx or caddy to replace emby's https function.

moviefan
Posted

So it's also not working in Windows 10?  Is Win10 still officially supported by Emby?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...