Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Images not loading #319

Closed
1 task done
Savanta opened this issue Jan 31, 2023 · 22 comments
Closed
1 task done

Images not loading #319

Savanta opened this issue Jan 31, 2023 · 22 comments

Comments

@Savanta
Copy link

Savanta commented Jan 31, 2023 •
edited
Loading

Description

Images are not loading and console keeps throwing 504 errors

Version

78ccea9

Steps to Reproduce

  1. Go to main page
  2. Images not loading

Screenshots

image
image

Logs

https://termbin.com/174r

Platform

desktop

Device

Docker

Operating System

Docker

Browser

Firefox, Vivaldi

Additional Context

version: '3'
services:
    jellyseerr:
       image: fallenbagel/jellyseerr:develop
       container_name: Jellyseer
       user: "${UID}:${GID}"
       environment:
            - LOG_LEVEL=debug
            - TZ=Europe/Warsaw
       volumes:
            - /media/Dane/.docker/jellyseer:/app/config
       restart: always
       networks:
            - InternalNPM

networks:
  InternalNPM:
      external: true

UID: 1000
GID: 1000

Code of Conduct

  • I agree to follow Overseerr's Code of Conduct
@Fallenbagel
Copy link
Owner

Could you try turning on image caching

@Savanta
Copy link
Author

Savanta commented Jan 31, 2023

It is on, problem persists

@Fallenbagel
Copy link
Owner

It is on, problem persists

Okay try this. Turn image caching off, go to settings > jobs and cache and flush image caching and tmdb cache

@Savanta
Copy link
Author

Savanta commented Jan 31, 2023

So I did some testing, it doesn't matter is it from local port or reverse proxy. Images take about 4 minutes to load and not all of them. Also searching is fast but image loading is even slower, about 5 minutes per search.
For reverse proxy I'm using nginx proxy manager.
image
image
image

@Savanta
Copy link
Author

Savanta commented Jan 31, 2023

Okay try this. Turn image caching off, go to settings > jobs and cache and flush image caching and tmdb cache

Also I did all of that and things are updating but terribly slow

@Kuuchuu
Copy link

Kuuchuu commented Feb 1, 2023

I have also been experiencing this issue. Seems to happen randomly on both Blink & Gecko based browsers.
I was however on v1.3.0, just updated to v1.4.1 when I noticed it was available. Haven't had the issue yet since updating, but I only updated maybe 10min ago.

@Fallenbagel
Copy link
Owner

@Savanta Is jellyseerr installed onto an HDD or SSD? and is it running under any vpn?
And could you now turn image proxying back on and navigate around a bit then provide the logs for it starting from when you did that?
also output of stat /media/Dane/.docker/jellyseer

@Savanta
Copy link
Author

Savanta commented Feb 6, 2023

It is running behing nginx reverse proxy.

❯ stat /media/Dane/.docker/jellyseer
  File: /media/Dane/.docker/jellyseer
  Size: 4096            Blocks: 8          IO Block: 4096   directory
Device: 804h/2052d      Inode: 22872066    Links: 5
Access: (0755/drwxr-xr-x)  Uid: ( 1000/  savant)   Gid: ( 1000/  savant)
Access: 2023-02-06 14:24:10.177083895 +0100
Modify: 2023-01-31 13:12:33.454835063 +0100
Change: 2023-01-31 13:12:33.454835063 +0100
 Birth: 2022-12-21 19:49:08.388453260 +0100

It is 1TB SSD

Here's log from console
image
image
I'm sorry, last few days were busy

@Fallenbagel
Copy link
Owner

Here's log from console
image
image
I'm sorry, last few days were busy

Could you try another browser 🤔

@Savanta
Copy link
Author

Savanta commented Feb 9, 2023

I'm trying Vivaldi on windows and Firefox on linux. No change

@Fallenbagel
Copy link
Owner

I'm trying Vivaldi on windows and Firefox on linux. No change

Nothing on the overseerr.log
I cant seem to reproduce this and it sounds like sth to do with the tmdb api and your geo-ip being rate limited or something. Have you got any vpns running?

@Savanta
Copy link
Author

Savanta commented Feb 9, 2023

No vpn, I even redeployed everything with clean config. Problem persisted.
For some reason ombi works fine. Any log I could provide?
Jellyseer shows no error in log, just regular scanning

@Savanta
Copy link
Author

Savanta commented Feb 9, 2023

Maybe I should explain my setup.
I got docker with jellyseer and separate nginx proxy manager. Both are connected by bridge network so no exposed port form jellyseer. Nginx redirects my subdomain to Jellyseer domain resolved through docker dns.
It looks like this:
image

@Fallenbagel
Copy link
Owner

That all looks good to me 🤔
For some reason jellyseerr is having trouble hitting the api.tmdb.org maybe. Try exec into container and run ping api.themoviedb.org

@Savanta
Copy link
Author

Savanta commented Feb 9, 2023

All good
picture

@Fallenbagel
Copy link
Owner

You're getting a 504 on those images. That's a gateway timeout error 🤔

@Savanta
Copy link
Author

Savanta commented Feb 9, 2023

But only sometimes...

@Savanta
Copy link
Author

Savanta commented Feb 13, 2023

Any ideas?

@Fallenbagel
Copy link
Owner

The thing I can think of is, try native installation. Could be a docker networking problem because 504 is gateway timeout error so 🤔

@Savanta
Copy link
Author

Savanta commented Feb 20, 2023

I've got a breakthrough!
So I finally did my local dns records, and when domain bounce of pihole to 10.0.0.5 everything loads instantaneously!
So problem only occurs when accessed from outside.

@Fallenbagel
Copy link
Owner

What's your upstream dns?

@Savanta
Copy link
Author

Savanta commented Feb 21, 2023

I changed from google to cloudflare, everything works now like a charm.
I'm closing. Thanks.

@Savanta Savanta closed this as completed Feb 21, 2023
Fallenbagel added a commit that referenced this issue May 23, 2024
@Fallenbagel
fix(jellyfinapi): use the cacheManager to cache jellyfin api and exte…
9c74ba7 
…nd it to external api class

This fix should in theory use nodeCache with the help of the cacheManager class to cache
jellyfin/emby api requests. Jellyfin's standard Time-To-Live was set as 6 hours so as to ensure that
the cached data is relatively up to date without making excessive API requests. In addition, this
fix sets the checkPeriod for the jellyfin cache to 30 minutes as it sounds suitable enough for
checking and cleaning up expired cach entries without causing perfomance overhead.

fix #728, fix #319
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Savanta @Kuuchuu @Fallenbagel