![]() if your using a vps for that activity, a reverse proxy can be used with. After checking nginx proxy, I've rebuild the Sonarr container multiple times and after checking that accessing IP:8989 was working fine, I went and checked nginx-proxy, and apparently that's what's broken.Īnything I should try? I've seem other similar issues and nothing worked, I already have a VIRTUAL_PORT and VIRTUAL_HOST on my container env's.Īll other containers are fine, radarr, plex, nginx website, everything is working. I am a big user of FREENAS and the goal behind this was to have one domain and to redirect the requests for my jails using, jails/sickrage, jails/sonarr. SABNZBD SONARR SETUP DOCKER TV Sonarr finds, downloads and manages TV shows You. ![]() This morning, out of the blue, my sonarr instance started to act weirdly, with 502 errors every now and then, after a while it just stopped working. Nginx.1 | 0 20:43:01 707#707: *1077 connect() failed (113: No route to host) while connecting to upstream, client: MY.IP, server:, request: "GET /vendors~index.js?h=faRhAy83bMn0pnvHe55DnQ HTTP/2.0", upstream: "", host: "", referrer: "" ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |