My overseerr stopped working what do I do

[visual crag]

i get errors on api calles

https://github.com/issues/recent?issue=sct|overseerr|4282

[bold quiver]

Have you tried changing your dns ?

[hardy rover]

This is dns

https://docs.seerr.dev/troubleshooting#tmdb-failed-to-retrievefetch-xxx

You can do

dns:
  - 9.9.9.9
  - 8.8.8.8
  - 1.1.1.1

On your compose

[visual crag]

i did that but still got the errors

services:
  overseerr:
    image: lscr.io/linuxserver/overseerr:latest
    container_name: overseerr
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
    volumes:
      - /medai/plexdisk/overseerr/config:/config
    ports:
      - 5055:5055
    restart: unless-stopped
    dns:
      - 9.9.9.9
      - 8.8.8.8
      - 1.1.1.1```

my compose

[visual crag]

i have tried all 3 of them but it is not working on any of the dnsses

[hardy rover]

Without logs cant tell

Please send logs

[visual crag]

just send them

[hardy rover]

Yeah will check in a while im not home rn

[visual crag]

No worries I am at work right now

[bold quiver]

You are still having dns resolution issues

[visual crag]

yes i know but dont know how to fix it

[hardy rover]

Can you try

docker exec -it overseerr sh

apk update && apk add curl

curl -L api.themoviedb.org

Alao

nslookup api.themoviedb.org

[visual crag]

i tried but it can not find the api nor google

[hardy rover]

Can you show the output

[bold quiver]

Not really related but I suggest you use the develop branch of Overseerr or plex watchlist feature won't work

[steel sequoia]

What O/S are you using? Do any of your other containers (if you have any), have DNS resolution? Does your container have connectivity? Can you ping 1.1.1.1 for example?

[visual crag]

i cant ping 1.1.1.1 and am using ubuntu

i dont think i have set up any other containers with a dns resolve

[visual crag]

i aint using the watch list anyway

[hardy rover]

Okay so this is not just dns issue

If you cant ping that means youe container isnt getting internet either

One thjng you could do is try restarting the docker service