Jump to content

Bug Report: Chrome issues


doonze

Recommended Posts

doonze

Using the latest version of chrome, Latest Emby server running on Linux

 

Backup plugin "restore" screen will never load right in chrome. Loads fine in Edge. Works till you click on a backup to load, then it opens the options screen and the spinny thing starts spinning, and never stops. Nothing ever loads. Even waited 10 mins just to see. Seen this reported elsewhere. Works fine in Edge and Firefox.

 

For now, I just do my backup restores in Edge. But I was creating a new server today, and so it was on my mind. I've seen this reported on several threads here about backing up. Thought I'd drop a bug report about it.  

 

 

Link to comment
Share on other sites

doonze

There were 6 errors when the problem was coming up. Now I have two.... and suddenly it's working. Problem has been evident on two servers, one I accessed HTTPS through an apache2 reverse proxy, the other was directly non-http through the local ip and the 8096 port. Problem has been happening both local and remote for some time. Just now I switched the target of my reverse proxy to the new instance of Emby on the new server (the whole reason this came up) , and now it's working. Both Emby instances have had been restarted multiple times, as well as their servers during this. Problem persisted. Now both instances automagicly work....  :wacko:

 

I do still get two warnings, but I commonly get these types of errors anyway from Emby on most pages. I think it has something to do with my reverse proxy. Emby normally still works fine.

 

Mixed Content: The page at 'https://xxxxxxxx/web/index.html#!/plugins.html'was loaded over HTTPS, but requested an insecure image 'http://embydata.com/images/configbackuptile.png'. This content should also be served over HTTPS.
index.html#!/plugins.html:1 Mixed Content: The page at 'https://xxxxxxxxxxx/web/index.html#!/plugins.html'was loaded over HTTPS, but requested an insecure image 'http://embydata.com/images/autoboxsettile.png'. This content should also be served over HTTPS.
 
I also get some errors sometimes about insecure content, and a socket API error, but it comes and goes. 
 
Bottom line, wasn't working for a couple of weeks, now it's working fine for whatever reason suddenly. Figures as soon as I go to report it. Sorry to waste your time. 
Edited by doonze
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...