Jump to content

when emby launches I get ERR_SSL_PROTOCOL_ERROR


pimo1974
Go to solution Solved by jaycedk,

Recommended Posts

pimo1974

I am unable to access via http or https on the local machine server is installed on. However I can access emby via my roku app fine. This happened after I cleaned up some expired intermediate certs on my PC> I tried a full uninstall/reinstall but retained settings.

image.png.80168967a0615cd8479e62c83b805a08.png

 

This cant be a port forwarding issue as this is on local machine and I can connect fine remotely. I think it has to be some issue with the cert itself?

Link to comment
Share on other sites

Hello pimo1974,

** This is an auto reply **

Please wait for someone from staff support or our members to reply to you.

It's recommended to provide more info, as it explain in this thread:


Thank you.

Emby Team

Link to comment
Share on other sites

Lessaj

8096 is http unless you made changes to the network config, your browser might be trying to upgrade to https automatically. Make sure it's still set to http, maybe try another browser as well.

Link to comment
Share on other sites

pimo1974

Also note I am completely unable to access the portal to change any settings unless there is some way to do so I'm unaware of. I can attach any logs required to help but that's about all I have access to at this point. I have looked over other posts but their issues seem to be different as they can still access the portal.

Link to comment
Share on other sites

pimo1974
1 minute ago, Lessaj said:

8096 is http unless you made changes to the network config, your browser might be trying to upgrade to https automatically. Make sure it's still set to http, maybe try another browser as well.

it does seem to be trying to do an https redirect. But even if I try forcing HTTP same result. Insteringly enough it seems you are right it launches in edge and firefox weirdly as HTTP. so some chrome issue?

  • Like 1
Link to comment
Share on other sites

jaycedk
Posted (edited)

Yes its a know issue with http vs https with a valid ssl certificate.

And chrome is really bad about it.

Edited by jaycedk
Link to comment
Share on other sites

pimo1974
3 minutes ago, jaycedk said:

try http://localhost:8096

Ps. are you running jellyfin on the same pc ?

not using jellyfin no... but as above weirly it seems to only be affecting chrome at this point. yesterday it would not launch in any browser. for now I guess edge it is.

Link to comment
Share on other sites

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...