RANDOM DROPS AND CAN NEVER RECONNECT

[Psychoticinsane 7]

So lemme start off by saying im upset with emby and this issue, it has rendered 2 pcs unusable because it literally drops connection to the servee and then pretends like it never existed in the first place 

 

Let me explain:

 

I will be watching emby on a pc using the web app and/or the installed emby app connected to my ember server ran from another pc INSIDE MY HOME ON THE SAME LOCAL NETWORK. it will randomly just freeze and pause, and will not continue playing nor will it successfully get back to the homepage. So i try refreshing browser , nothing. So i try a new tab, emby now thinks emby never existed. Close the web browser try a new instance. Same thing says emby never existed and my login info fails everytime. So i reboot the pc, same thing emby still thinks it never existed and cannot find the account nor the server. I have even tried edge browser, and dolphin browser to the same results. I completey purged all tradfic and cookies and all network data. Same  issue. I then completely removed chrome and fresh installed with no previous user information not even an account. I go to log in to emby webpage, tells me my password is wrong, when i know for a fact it isnt, as im able to log in on the server machine and my phone with said "wrong" password. After the ridiculousness of being forced to change password because emby is broken, it finally lets me log in to the account and all is well right? WRONG!! now it says the server is unreachable/doesnt exist and im WATCHING A STREAM ON ANOTHER DEVICE THE WHOLE TIME!!!

 

What is causing this? Why does emby just act like it never existed and cannot find the server it was literally jus connected to? Not only are the web browsers not working but the emby apps wont connect either? This is a new issue as i have had emby for 7+ years. 

 

SO NOW THERE ARE TWO PCS IN MY HOME THAT EMBY JUST FLAT OUT REFUSES TO CONNECT WITH JUST FOREVER SAYS SERVER UNAVAILABLE 

 

IM AT MY WITS END AND READY TO JUMP BACK TO PLEX DUE TO THIS RIDICULOUS ISSUE. 

 

ANYONE HAVE ANY IDEAS OR A FIX???

Edited October 14, 2023 by psycoticinsane
Really?

[pwhodges 2012]

2 minutes ago, psycoticinsane said:

ANYONE HAVE ANY IDEAS OR A FIX???

(1) Calm down before you persuade people not to bother with you.

(2) Report the problems in detail, with server logs, so that we can see what's actually happening:

(3) Thousands of people use Emby without these problems, so there should be no problem sorting you out.

Paul

[Psychoticinsane 7]

My apologies, as this is very upsetting and shouldnt even be an issue.

 

For starters, where would the logs be located? In the server machine, or the connecting machine? As the connecting machines no longer connect the server machine doesnt even recognize them

[Psychoticinsane 7]

5 minutes ago, pwhodges said:

(1) Calm down before you persuade people not to bother with you.

(2) Report the problems in detail, with server logs, so that we can see what's actually happening:

(3) Thousands of people use Emby without these problems, so there should be no problem sorting you out.

Paul

My apologies. I have reworded my post im just very upset at the whole situation, its.mind boggling to how it can go from streaming fine, to acting like it never existed in a matter of seconds

 

For starters, where would the logs be located? In the server machine, or the connecting machine? As the connecting machines no longer connect the server machine doesnt even recognize them

Edited October 14, 2023 by psycoticinsane

[Psychoticinsane 7]

[Luke 42078]

 

Hi there, let's look at an example. Please attach the information requested in how to report a media playback issue. Thanks!

 

[pwhodges 2012]

Logs are in the server.  On the dashboard, in the lefthand menu, there is an item "Logs".  You can download the current Embyserver log from there and then attach it to a post in this thread simply by drag and drop.  Ffmpeg logs (if any) covering the same time interval may also be useful (I tend to zip up all the relevant logs rather than dropping them one by one).

Paul

[Psychoticinsane 7]

i have included everything in the logs folder from the specified timeframe roughly 12:18pm EST

ffmpeg-transcode-c9d2dc6b-d4ec-4dc6-be01-7412ae62cbcc_1.zip

[pwhodges 2012]

The "embyserver.log" is the important one.

Paul

[Psychoticinsane 7]

embyserver.zip

[pwhodges 2012]

I have to go out now (hopefully someone else will step in); but I note the first error is in DLNA, which I know nothing about, then lots of Portmapper errors, which can be ignored, then I see:

Could not find a part of the path 'Z:\For Mom'

which might mean something to you.

Paul

[Psychoticinsane 7]

35 minutes ago, pwhodges said:

I have to go out now (hopefully someone else will step in); but I note the first error is in DLNA, which I know nothing about, then lots of Portmapper errors, which can be ignored, then I see:

Could not find a part of the path 'Z:\For Mom'

which might mean something to you.

Paul

as it pertains to this problem, it means nothing, it was an old cloud drive that i mounted via raidrive and setup in emby, i nolonger use that storage location and everything is local, and i have removed it from the library it was associated with. in either case that library was not in use when the error occurred. was the main library for tv shows.

 

i was able to get it working again one time before, what i had to do after exhausting all options i could think of at the time, was uninstall chrome and do fresh install on the connecting pc as well as change my password (which i then changed back). that solution has since no longer worked.

[Psychoticinsane 7]

It seems to happen on chrome web browsers

Still loked out still dont know why

[Psychoticinsane 7]

Anyone have any help on this at all? Im still locked out, emby still cannot connect to running and visible server on certain pcs using chrome web browser, yet if i use edge on that same pc, it can see and connect to the server. I dont feel i should be forced to use a web browser i do not like because there is a programming error through emby. all pcs on the same local network. Happened to a third since i originally posted this thread.

 

 

 

[pwhodges 2012]

On the machines on which Chrome doesn't connect, does the address bar show "https" instead of "http" when it fails?

Paul

[Psychoticinsane 7]

10 hours ago, pwhodges said:

On the machines on which Chrome doesn't connect, does the address bar show "https" instead of "http" when it fails?

Paul

I have attached two photos. 

The first is of the address bar of chrome on one of the affected machines, it also shows the address of the server

The second is of a chrome browser(on the right) and a edge browser (on the left) side by side showing the pc itself is able to connect to the server, just chrome will not. A reset of browsing history and a complete uninstall and reinstall, does not help at all. 

[Psychoticinsane 7]

10 hours ago, pwhodges said:

On the machines on which Chrome doesn't connect, does the address bar show "https" instead of "http" when it fails?

Paul

After re reading your comment, i clicked on the address bar which revealed it was https. I deleted the s, and reloaded, and had to sign in again, once signed in i was able to access the server and my user profile. I will check the other machines and see if it shows the same and if this fix works on those as well. 

[Psychoticinsane 7]

Why would http and https have such a different affect on emby?

 

 

 

[Luke 42078]

22 minutes ago, psycoticinsane said:

Why would http and https have such a different affect on emby?

 

 

 

It's the rules of the browser. A web app on https is not allowed to communicate with an http-based url.

That means you either need setup https for your emby server, or you need to use the http web app. Does that make sense?

[pwhodges 2012]

1 hour ago, psycoticinsane said:

Why would http and https have such a different affect on emby?

Think of the web address as a door and http or https as keys to open the door - using the incorrect key doesn't work.

(What follows is a slight rant:)

There are circumstances in which Chrome decides to override your selection and change your typed "http" into "https" which then fails - having done this it caches the incorrect decision, and it can be a pain to get it to behave properly again.  This is something that Google calls "security"...

It doesn't help that browsers hide the protocol they're using (like Windows hides file types by default).

Note, my description is not exact, as I don't use Chrome, and haven't seen this happen myself - but I have seen plenty of posts on the Internet helping people who are struggling to get out of this mess.  I prefer a browser that does what I tell it to (though they're all becoming less predictable these days).  HSTS (Hypertext Strict Transport Security) is sometimes involved - some server security web sites seem to recommend that server admins set a header which forces this change from http to https even when it's not appropriate.

Paul

[Psychoticinsane 7]

7 hours ago, Luke said:

It's the rules of the browser. A web app on https is not allowed to communicate with an http-based url.

That means you either need setup https for your emby server, or you need to use the http web app. Does that make sense?

It does make sense, but why would it randomly happen out of the blue one day , when i have been using emby since 2018/19? 

I didnt make any changes or anything 

I was watching as usual, the show froze, i tried refreshing and restarting and then boom this happened. Im just very confused as to the why and how i guess. I could understand if i made changes that messed it up, but i literally did nothing different than the previous 5 years lol

 

[Psychoticinsane 7]

6 hours ago, pwhodges said:

Think of the web address as a door and http or https as keys to open the door - using the incorrect key doesn't work.

(What follows is a slight rant:)

There are circumstances in which Chrome decides to override your selection and change your typed "http" into "https" which then fails - having done this it caches the incorrect decision, and it can be a pain to get it to behave properly again.  This is something that Google calls "security"...

 

Your explanation makes sense to me 

 

Im just baffled as to the why and the how of it all. Literally happened mid stream when nothing was changed added used downloaded etc. I will definitely keep this in mind for the future if it ever happens again as its a stupid simple fix for a very frustrating problem.

 

6 hours ago, pwhodges said:

some server security web sites seem to recommend that server admins set a header which forces this change from http to https even when it's not appropriate.

Paul

How would one do this to avoid this issue all together? Besides switching browsers.

 

7 hours ago, Luke said:

hat means you either need setup https for your emby server, or you need to use the http web app. Does that make sense?

How would one set up the https for emby , or force http on browser?

[tedfroop 34]

2 hours ago, psycoticinsane said:

It does make sense, but why would it randomly happen out of the blue one day , when i have been using emby since 2018/19? 

In Chrome, if you go to the top right corner, click on the three dots, go down the list to Settings, then to Privacy and Security you can set the options to allow use of http or https as you want.  I'm not sure but there may be a whitelist, or list of sites allowed to use Http while still preferring to use https for other sites.  

I use one for my older network devices that do not support https.

[pwhodges 2012]

2 hours ago, tedfroop said:

In Chrome, if you go to the top right corner, click on the three dots, go down the list to Settings, then to Privacy and Security you can set the options to allow use of http or https as you want. 

A recent update to Chrome has added a list of TLDs which require extra effort to allow the use of http - ".dev" is one, and I have seen developers who use .dev screaming about the change.

Paul

[Luke 42078]

5 hours ago, psycoticinsane said:

It does make sense, but why would it randomly happen out of the blue one day , when i have been using emby since 2018/19? 

 

Because it coincided with a Chrome update.