firefox web interface - cache problem

[alberto.bracci 0]

Hello,

 

I have a problem with web interfaces, both in firefox and chrome on windows. In particular when I open emby from browser it often shows an older cached session, meaning that the next episodes to play and the one to be resumed are older. If I clean the cache, things get back to normal. Still, it happens all the time and I cannot keep clearing the cache every time, is there a way to prevent this from happening?

 

Thanks,

Alberto

[Happy2Play 9079]

What browser versions?  I have never experience this on either browser on my Windows systems.

[alberto.bracci 0]

firefox 69.0.1

[alberto.bracci 0]

The issue persists, with both chrome and firefox on different laptops.

[Luke 38528]

Thanks for the info. We'll take a look.

[alberto.bracci 0]

Do you need any logs or config info? Apparently the issue is present also in the android app.

I run emby server on a Manjaro Linux desktop machine, using nginx with reverse proxy for remote connection.

I am not sure but maybe the issue appeared with latest server update, it was not always present in the past

[Luke 38528]

I have not been able to reproduce this. Perhaps try without the reverse proxy?

[alberto.bracci 0]

I tried some changes in the reverse proxy but nothing works. In particular I tried adding proxy_cache off; or expires off; to the emby block without any success.

Only thing that works is disabling http caching in a firefox developer session. Unfortunately it is only a temporary workaround.

 

It seems like it is an issue with caching, maybe due to nginx. Unfortunately I have many services set up with nginx and cannot do without it. I share the emby block to see whether some of you might have any suggestion.

 

Thanks for your help!

 

 

[Luke 38528]

Have you compared your nginx setup to @@pir8radio 's ? 

[alberto.bracci 0]

Thanks for the hint! Apparently, I also had to look for cache related settings in other parts of the file.

In particular, I had a line the @@pir8radio 's file didn't have:

 

add_header Cache-Control "public, max-age = 15778463";

removing it seems to solve the issue at least for the browser.

Thanks!

[Luke 38528]

Thanks for the feedback.

[pir8radio 1301]

Yea you don't want to force long cache times for anything but the .webp images.    Emby versions all of their javascripts and what not, if you cache html it will try to call old scripts and stuff.  

 

Good job finding the issue. 

Edited October 9, 2019 by pir8radio

[alberto.bracci 0]

Thanks for the explanation! This reminds me of another small issue I have that might be related.

My libraries' images on the homepage are the same one that have been generated when I first set up emby. I cannot find a way to force their update, as the content has changed and thus the image shows wrong content.

Can it still be a cache related problem?

 

I think this issue was present even before I set up nginx, so it shouldn't be related to that.

[Happy2Play 9079]

Thanks for the explanation! This reminds me of another small issue I have that might be related.

My libraries' images on the homepage are the same one that have been generated when I first set up emby. I cannot find a way to force their update, as the content has changed and thus the image shows wrong content.

Can it still be a cache related problem?

 

I think this issue was present even before I set up nginx, so it shouldn't be related to that.

 

 

Haven't tested in awhile and am not sure if it is broke in stable version or not.  I know it has been updated in the beta 4.3.x.x and requires a delete of current image to generate new image on next library scan.

[alberto.bracci 0]

Thanks for another good hint!

Emby server stable version 4.2.1.0 on Manjaro Linux, deleting the images and scanning the libraries made them update!

 

Thanks again to all of you for your help!