We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
After updating from the Feb 4th build to the March 27th build, I am inferring an issue where I am not able to login to Jellyseerr using jellyfin
Also, I noticed that curl to jellyfin is failing from both jellyseerr and jellyfin
sakthi@sakthi-standardpc:~/docker-compose-nas\[\] (master)# docker exec -it jellyfin /bin/sh # curl curl: try 'curl --help' or 'curl --manual' for more information # curl http://jellyfin:8096/jellyfin #
sakthi@sakthi-standardpc:~/docker-compose-nas\[\] (master)# docker exec -it jellyseerr /bin/sh /app # curl http://jellyfin:8096/jellyfin /app # curl http://sonarr:8989/sonarr <!doctype html><html lang="en">
Meanwhile, curl to sonarr and the rest of the services are successful.
Only changes I have made in docker-compose are as follows.
diff --git a/docker-compose.yml b/docker-compose.yml index b1a738b..1d71b12 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -8,6 +8,7 @@ services: - CLOUDFLARE_DNS_API_TOKEN=${CLOUDFLARE_DNS_API_TOKEN} - CLOUDFLARE_ZONE_API_TOKEN=${CLOUDFLARE_ZONE_API_TOKEN} - LETS_ENCRYPT_EMAIL=${LETS_ENCRYPT_EMAIL} + - TZ=${TIMEZONE} command: - --ping=true - --providers.docker=true @@ -23,7 +24,7 @@ services: - --experimental.plugins.rewriteHeaders.version=v0.0.3 - --certificatesresolvers.myresolver.acme.dnschallenge=${DNS_CHALLENGE:-true} - --certificatesresolvers.myresolver.acme.dnschallenge.provider=${DNS_CHALLENGE_PROVIDER:-cloudflare} - - --certificatesresolvers.myresolver.acme.dnschallenge.resolvers=1.1.1.1:53,8.8.8.8:53 + - --certificatesresolvers.myresolver.acme.dnschallenge.resolvers=172.64.35.61:53,1.1.1.1:53,172.64.34.244:53,8.8.8.8:53 - --certificatesresolvers.myresolver.acme.caserver=${LETS_ENCRYPT_CA_SERVER:-https://acme-v02.api.letsencrypt.org/directory} - --certificatesresolvers.myresolver.acme.email=${LETS_ENCRYPT_EMAIL} - --certificatesresolvers.myresolver.acme.storage=/letsencrypt/acme.json @@ -307,10 +308,6 @@ services: ["CMD", "curl", "--fail", "http://127.0.0.1:8080", "https://google.com"] interval: 30s retries: 10 - network_mode: "service:vpn" - depends_on: - vpn: - condition: service_healthy labels: - traefik.enable=true - traefik.http.routers.qbittorrent.rule=(Host(`${HOSTNAME}`) && PathPrefix(`/qbittorrent`)) @@ -332,40 +329,9 @@ services: - homepage.description=Bittorrent client - homepage.weight=2 - homepage.widget.type=qbittorrent - - homepage.widget.url=http://vpn:8080 + - homepage.widget.url=http://qbittorrent:8080/qbittorrent - homepage.widget.username=${QBITTORRENT_USERNAME} - homepage.widget.password=${QBITTORRENT_PASSWORD} - vpn: - image: ghcr.io/thrnz/docker-wireguard-pia:latest - container_name: vpn - volumes: - - ${CONFIG_ROOT:-.}/pia:/pia - - ${CONFIG_ROOT:-.}/pia-shared:/pia-shared - cap_add: - - NET_ADMIN - - SYS_MODULE - environment: - - LOC=${PIA_LOCATION} - - USER=${PIA_USER} - - PASS=${PIA_PASS} - - QBT_USER=${QBITTORRENT_USERNAME} - - QBT_PASS=${QBITTORRENT_PASSWORD} - - LOCAL_NETWORK=${PIA_LOCAL_NETWORK} - - PORT_FORWARDING=1 - - PORT_PERSIST=1 - - PORT_SCRIPT=/pia-shared/portupdate-qbittorrent.sh - - FIREWALL=0 - sysctls: - - net.ipv4.conf.all.src_valid_mark=1 - - net.ipv6.conf.default.disable_ipv6=1 - - net.ipv6.conf.all.disable_ipv6=1 - - net.ipv6.conf.lo.disable_ipv6=1 - healthcheck: - test: ping -c 1 www.google.com || exit 1 - interval: 30s - timeout: 10s - retries: 3 - restart: always unpackerr: image: ghcr.io/unpackerr/unpackerr:latest container_name: unpackerr
The text was updated successfully, but these errors were encountered:
No branches or pull requests
After updating from the Feb 4th build to the March 27th build, I am inferring an issue where I am not able to login to Jellyseerr using jellyfin
Also, I noticed that curl to jellyfin is failing from both jellyseerr and jellyfin
Meanwhile, curl to sonarr and the rest of the services are successful.
Only changes I have made in docker-compose are as follows.
The text was updated successfully, but these errors were encountered: