Login to emby server with Microsoft Edge (chromium)

[prmusic 0]

Hi,

I am pretty new to emby. I was setting up the server and it works just fine. Emby is running on a Win10 machine.
On the local machine I can log in to the server with user password without a problem using MS Edge (chromium)
browser.
If I want to log into emby from a remote PC with MS Edge (chromium) it asks for my User and password and afterwards
the browser returns an error message:
RESULT_CODE_KILLED_BAD_MESSAGE

Using Firefox on that machine works normal. Actually when starting with emby, the login on that machine via Edge worked
perfectly. Not sure if I did anything which caused the issue.
Software version and updates of the machine running emby and the one I am trying to access emby are the same.
I have not updated to 2004 yet.

I did reset Edge already on the remote PC to make sure it isn't a specific setting in the browser causing the problem.

Any suggestions / advise how this can be solved?

Thanks

prmusic

[Luke 42078]

Hi there, as a test, have you tried Chrome to compare?

[prmusic 0]

On 6/20/2020 at 8:15 PM, Luke said:

Hi there, as a test, have you tried Chrome to compare?

Hi Luke,

Chrome, works just fine. Interestingly Microsoft Egde works on another PC just fine as well. Even on the problematic PC it worked - but no more.
Might be a local issue and I am thinking of how to fix it. I tried to reinstall Microsoft Edge but that didn't solved it.

Any suggestion how to get it fixed? Don't want to use a different Browser just because of Emby.

Thanks

 

prmusic

[Luke 42078]

I haven't heard of this before. Do you have any Edge extensions installed? if so then please try removing them.

[tekfranz 6]

I just encountered Edge Chromium having trouble logging in remotely and loading but Internet Explorer working just fine.

Update: I also tested in Chrome and it worked fine. I am not sure why MS Edge Chromium handles this differently. EMBY spins and spins before loading the home page. Then most links take the user to a broken page with unusable controls.  They're really should be no difference because Edge and Chrome are based on the same source code, but obviously Microsoft is doing something different here.

Edited June 30, 2020 by tekfranz

[Luke 42078]

Are you still running into this?

[tekfranz 6]

4 minutes ago, Luke said:

Are you still running into this?

It is resolved and the Microsoft Edge Browser works great. It seems like as I experimenting with different certificates and Edge was not accepting the new certificates as quickly as Chrome. After some time MS Edge began working as well.

[Luke 42078]

Thanks for the feedback !

[Corteq 5]

I just started having the same problem. Like prmusic, it works using Chrome and also on other machines, but not my primary with Edge Chromium. Tried a reset, disabled extensions but nothing seems to work. Tekfranz's issue was a bit different to this as he was trying to login remotely. My issue is when accessing a local server.

[Carlo 4561]

4 hours ago, Corteq said:

I just started having the same problem. Like prmusic, it works using Chrome and also on other machines, but not my primary with Edge Chromium. Tried a reset, disabled extensions but nothing seems to work. Tekfranz's issue was a bit different to this as he was trying to login remotely. My issue is when accessing a local server.

Can you be more specific exactly what you're seeing?

[Corteq 5]

6 hours ago, cayars said:

Can you be more specific exactly what you're seeing?

Attached is a screen grab of the error. This seems identical to the description prmusic gave.

[Luke 42078]

Interesting, never seen that error code before.

[WilhelmStroker 102]

What build of Edge are you on? If on stable, try with either Dev or Canary to see if the error goes away. I'm using Dev and have not seen this error.  

Are you accessing your server on the same machine or from a different machine? 

[Carlo 4561]

I've seen it before and normally one of these is the issue:

Try restarting the computer/nas/device running Emby if you haven't done that already.

Turn off any browser extensions you may have running.

If using a PROXY of any kind try it without the proxy involved.

Try http vs https and see if the problem disappears as it's likely related to an SSL issue.

[Corteq 5]

7 hours ago, WilhelmStroker said:

What build of Edge are you on? If on stable, try with either Dev or Canary to see if the error goes away. I'm using Dev and have not seen this error.  

Are you accessing your server on the same machine or from a different machine? 

Edge Version 86.0.622.48 (latest). Emby is installed on a Virtual Server running Windows Server 2012. I access this from several internal machines. All other clients have no problem, just my main PC. Tried using inPrivate but still get the same error. No other problems on this PC. All other sites, both internal and outside the network return fine, it is only Emby that fails.

[Corteq 5]

6 hours ago, cayars said:

I've seen it before and normally one of these is the issue:

Try restarting the computer/nas/device running Emby if you haven't done that already.

Turn off any browser extensions you may have running.

If using a PROXY of any kind try it without the proxy involved.

Try http vs https and see if the problem disappears as it's likely related to an SSL issue.

Thank you for your response. Yes I have restarted the server, and client. Browser extensions were turned off and no proxy. Access is via http (unsecure). Emby is on Ver 4.5.2.0. I am not sure if the upgrade to this version was the cause but it coincided very closely with it.

[WilhelmStroker 102]

43 minutes ago, Corteq said:

Edge Version 86.0.622.48 (latest). Emby is installed on a Virtual Server running Windows Server 2012. I access this from several internal machines. All other clients have no problem, just my main PC. Tried using inPrivate but still get the same error. No other problems on this PC. All other sites, both internal and outside the network return fine, it is only Emby that fails.

That version is the release version, try installing either Dev or Canary from https://www.microsoftedgeinsider.com/en-us/ and see if you still see the same issue. 

[Corteq 5]

Thank you for your help. Unfortunately nothing has worked so I recovered the system from an earlier backup. Things are working fine now and I am slowly bringing the system up to date. It is always a little unsettling when you can't identify what caused a specific problem. I was hoping we could get to the bottom of this so it would be of help to others. Anyway, I do appreciate people taking the time to post suggestions. This Emby community and moderators have always been a credit to the platform.

[bmflagg 21]

I too am having this same issue.
Some machines with edge work.. My local PC, only Chrome.
Reset all settings on Edge and cleared cache... nothing.

[Luke 42078]

Seems to be working OK from here using vanilla installations of both stable and dev channels of the Edge browser.

[Happy2Play 9780]

12 minutes ago, bmflagg said:

Some machines with edge work.. My local PC, only Chrome.

Now the hard part of what is different about this pc vs the others.  Things like these can be very difficult to identify as it only affect one browser on the specific system.

[Carlo 4561]

I've got the dev and release version and don't experience this issue either.

[bmflagg 21]

On difference is I moved emby to qnap.. I think we are now dual posting.

I started a thread today..same subject...

[Carlo 4561]

Right but you are using the new IP address of the QNAP in your browser right?

It matches the URL of what you see in the web Dashboard?

[bmflagg 21]

Yes..

 I signed in with my wife account on my PC and edge works fine so it appears to be profile related..

Investigating further...