How did you install swag and jellyfin? Did you use stacks in portainer?
I installed it via AppTemplates as told in Techno Dad youtube channel.
Using LetsEncrypt for SSL to access Jellyfin over internet with duckdns
-
- gelöst
- OMV 6.x
- anchits123
-
App template? No idea what that is.
-
App template? No idea what that is.
Ok.
Anyway, error 502 bad gateway is shown at "jellyfin.apXXXXXXXX.duckdns.org"
Maybe there is some other error I am unable to understand.
-
-
Ok.
Anyway, error 502 bad gateway is shown at "jellyfin.apXXXXXXXX.duckdns.org"
Maybe there is some other error I am unable to understand.
That's probably because jellyfin sn't on the same network as swag
-
Here we go again....
+1 counter on the lack of info provided:
Post inside a codebox </> the stack you're using to launch SWAG.
From the first log you showed, your stack is missing fundamental configs:
Code
Alles anzeigenSUBDOMAINS= EXTRA_DOMAINS= ONLY_SUBDOMAINS=false VALIDATION=http CERTPROVIDER= DNSPLUGIN=cloudflare EMAIL= STAGING=false Using Let's Encrypt as the cert provider No subdomains defined No e-mail address entered or address invalid http validation is selected -
Alles anzeigen
Here we go again....
+1 counter on the lack of info provided:
Post inside a codebox </> the stack you're using to launch SWAG.
From the first log you showed, your stack is missing fundamental configs:
Code
Alles anzeigenSUBDOMAINS= EXTRA_DOMAINS= ONLY_SUBDOMAINS=false VALIDATION=http CERTPROVIDER= DNSPLUGIN=cloudflare EMAIL= STAGING=false Using Let's Encrypt as the cert provider No subdomains defined No e-mail address entered or address invalid http validation is selectedThis is the stack :
Code
Alles anzeigenPUID=1002 PGID=100 TZ=Asia/Calcutta URL=apxxxxxxxx.duckdns.org VALIDATION=http DNSPLUGIN=cloudflare ONLY_SUBDOMAINS=false STAGING=false PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin PS1=$(whoami)@$(hostname):$(pwd)\$ HOME=/root TERM=xterm S6_CMD_WAIT_FOR_SERVICES_MAXTIME=0 DHLEVEL=2048 AWS_CONFIG_FILE=/config/dns-conf/route53.ini S6_BEHAVIOUR_IF_STAGE2_FAILS=2 SUBDOMAINS=jellyfin -
-
This is the stack :
Code
Alles anzeigenPUID=1002 PGID=100 TZ=Asia/Calcutta URL=apxxxxxxxx.duckdns.org VALIDATION=http DNSPLUGIN=cloudflare ONLY_SUBDOMAINS=false STAGING=false PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin PS1=$(whoami)@$(hostname):$(pwd)\$ HOME=/root TERM=xterm S6_CMD_WAIT_FOR_SERVICES_MAXTIME=0 DHLEVEL=2048 AWS_CONFIG_FILE=/config/dns-conf/route53.ini S6_BEHAVIOUR_IF_STAGE2_FAILS=2 SUBDOMAINS=jellyfinUh, how is duckdns routing through cloudflare? I didn't even know that was possible. He's not even identified his duckdns token, so I have no idea how he's getting a cert.
-
This is the stack :
That looks nothing like a stack.
This is a proper stack:
Code
Alles anzeigen--- version: "2.1" services: swag: image: lscr.io/linuxserver/swag:latest container_name: swag cap_add: - NET_ADMIN environment: - PUID=1002 - PGID=100 - TZ=Asia/Calcuta - URL=yourdomain.url #change to your own - VALIDATION=duckdns # use this when using duckdns - DUCKDNSTOKEN= # place your duckdns token here - SUBDOMAINS=wildcard - EMAIL=your@email.here # needed for renewal warnings - ONLY_SUBDOMAINS=false #optional - STAGING=false #optional volumes: - /path/to/appdata/config:/config # change the path to the one you use ports: - 5443:443 - 5080:80 #optional restart: unless-stoppedNow make a portforward on the router from WAN 80 to OMV ip LAN 5080 && WAN 443 to OMV ip LAN 5443
-
Here we go again....
+1 counter on the lack of info provided:
It's almost like a theme here..
-
-
That's probably because jellyfin sn't on the same network as swag
I have created a network inside portainer and added these 3 containers on the same network.
The problem still persists.
-
That looks nothing like a stack.
This is a proper stack:
Code
Alles anzeigen--- version: "2.1" services: swag: image: lscr.io/linuxserver/swag:latest container_name: swag cap_add: - NET_ADMIN environment: - PUID=1002 - PGID=100 - TZ=Asia/Calcuta - URL=yourdomain.url #change to your own - VALIDATION=duckdns # use this when using duckdns - DUCKDNSTOKEN= # place your duckdns token here - SUBDOMAINS=wildcard - EMAIL=your@email.here # needed for renewal warnings - ONLY_SUBDOMAINS=false #optional - STAGING=false #optional volumes: - /path/to/appdata/config:/config # change the path to the one you use ports: - 5443:443 - 5080:80 #optional restart: unless-stoppedNow make a portforward on the router from WAN 80 to OMV ip LAN 5080 && WAN 443 to OMV ip LAN 5443
I had already done that.
-
I had already done that.
Post now the output of
docker logs -f swag
And can you see the swag park page when you go to https://www.yourduckdns.org
-
-
Post now the output of
docker logs -f swag
And can you see the swag park page when you go to https://www.yourduckdns.org
Whenever I open jellyfin.axxxxxxxxx.duckdns.org, "Welcome to SWAG instance" page is displayed instead of jellyfin page.
Maybe it is not redirecting to the specified port 8096...?
Here are the logs :
Code
Alles anzeigenBrought to you by linuxserver.io ------------------------------------- To support the app dev(s) visit: Certbot: https://supporters.eff.org/donate/support-work-on-certbot To support LSIO projects visit: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 1002 User gid: 100 ------------------------------------- cont-init: info: /etc/cont-init.d/10-adduser exited 0 cont-init: info: running /etc/cont-init.d/11-folders cont-init: info: /etc/cont-init.d/11-folders exited 0 cont-init: info: running /etc/cont-init.d/12-samples cont-init: info: /etc/cont-init.d/12-samples exited 0 cont-init: info: running /etc/cont-init.d/13-nginx cont-init: info: /etc/cont-init.d/13-nginx exited 0 cont-init: info: running /etc/cont-init.d/14-php cont-init: info: /etc/cont-init.d/14-php exited 0 cont-init: info: running /etc/cont-init.d/15-keygen using keys found in /config/keys cont-init: info: /etc/cont-init.d/15-keygen exited 0 cont-init: info: running /etc/cont-init.d/20-permissions cont-init: info: /etc/cont-init.d/20-permissions exited 0 cont-init: info: running /etc/cont-init.d/30-test-run cont-init: info: /etc/cont-init.d/30-test-run exited 0 cont-init: info: running /etc/cont-init.d/31-require-url cont-init: info: /etc/cont-init.d/31-require-url exited 0 cont-init: info: running /etc/cont-init.d/40-folders cont-init: info: /etc/cont-init.d/40-folders exited 0 cont-init: info: running /etc/cont-init.d/41-samples cont-init: info: /etc/cont-init.d/41-samples exited 0 cont-init: info: running /etc/cont-init.d/42-fail2ban cont-init: info: /etc/cont-init.d/42-fail2ban exited 0 cont-init: info: running /etc/cont-init.d/43-crontabs cont-init: info: /etc/cont-init.d/43-crontabs exited 0 cont-init: info: running /etc/cont-init.d/45-nginx cont-init: info: /etc/cont-init.d/45-nginx exited 0 cont-init: info: running /etc/cont-init.d/50-certbot Variables set: 2 PGID=100 TZ=Asia/Calcutta URL=axxxxxxxxx.duckdns.org SUBDOMAINS=jellyfin EXTRA_DOMAINS= ONLY_SUBDOMAINS=false VALIDATION=http CERTPROVIDER= DNSPLUGIN= EMAIL=anchitsingh9@gmail.com STAGING=false Using Let's Encrypt as the cert provider SUBDOMAINS entered, processing SUBDOMAINS entered, processing Sub-domains processed are: -d jellyfin.axxxxxxxxx.duckdns.org E-mail address entered: anchitsingh9@gmail.com http validation is selected Certificate exists; parameters unchanged; starting nginx cont-init: info: /etc/cont-init.d/50-certbot exited 0 cont-init: info: running /etc/cont-init.d/55-permissions cont-init: info: /etc/cont-init.d/55-permissions exited 0 cont-init: info: running /etc/cont-init.d/60-renew The cert does not expire within the next day. Letting the cron script handle the renewal attempts overnight (2:08am). cont-init: info: /etc/cont-init.d/60-renew exited 0 cont-init: info: running /etc/cont-init.d/70-outdated cont-init: info: /etc/cont-init.d/70-outdated exited 0 cont-init: info: running /etc/cont-init.d/85-version-checks cont-init: info: /etc/cont-init.d/85-version-checks exited 0 cont-init: info: running /etc/cont-init.d/99-custom-files [custom-init] No custom files found, skipping... cont-init: info: /etc/cont-init.d/99-custom-files exited 0 s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service init-mods: starting s6-rc: info: service init-mods successfully started s6-rc: info: service init-mods-package-install: starting s6-rc: info: service init-mods-package-install successfully started s6-rc: info: service init-mods-end: starting s6-rc: info: service init-mods-end successfully started s6-rc: info: service init-services: starting s6-rc: info: service init-services successfully started s6-rc: info: service legacy-services: starting services-up: info: copying legacy longrun cron (no readiness notification) services-up: info: copying legacy longrun fail2ban (no readiness notification) services-up: info: copying legacy longrun nginx (no readiness notification) services-up: info: copying legacy longrun php-fpm (no readiness notification) s6-rc: info: service legacy-services successfully started s6-rc: info: service 99-ci-service-check: starting [ls.io-init] done. s6-rc: info: service 99-ci-service-check successfully started Server ready -
Whenever I open jellyfin.axxxxxxxxx.duckdns.org, "Welcome to SWAG instance" page is displayed instead of jellyfin page.
Maybe it is not redirecting to the specified port 8096...?
Here are the logs :
Code
Alles anzeigenBrought to you by linuxserver.io ------------------------------------- To support the app dev(s) visit: Certbot: https://supporters.eff.org/donate/support-work-on-certbot To support LSIO projects visit: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 1002 User gid: 100 ------------------------------------- cont-init: info: /etc/cont-init.d/10-adduser exited 0 cont-init: info: running /etc/cont-init.d/11-folders cont-init: info: /etc/cont-init.d/11-folders exited 0 cont-init: info: running /etc/cont-init.d/12-samples cont-init: info: /etc/cont-init.d/12-samples exited 0 cont-init: info: running /etc/cont-init.d/13-nginx cont-init: info: /etc/cont-init.d/13-nginx exited 0 cont-init: info: running /etc/cont-init.d/14-php cont-init: info: /etc/cont-init.d/14-php exited 0 cont-init: info: running /etc/cont-init.d/15-keygen using keys found in /config/keys cont-init: info: /etc/cont-init.d/15-keygen exited 0 cont-init: info: running /etc/cont-init.d/20-permissions cont-init: info: /etc/cont-init.d/20-permissions exited 0 cont-init: info: running /etc/cont-init.d/30-test-run cont-init: info: /etc/cont-init.d/30-test-run exited 0 cont-init: info: running /etc/cont-init.d/31-require-url cont-init: info: /etc/cont-init.d/31-require-url exited 0 cont-init: info: running /etc/cont-init.d/40-folders cont-init: info: /etc/cont-init.d/40-folders exited 0 cont-init: info: running /etc/cont-init.d/41-samples cont-init: info: /etc/cont-init.d/41-samples exited 0 cont-init: info: running /etc/cont-init.d/42-fail2ban cont-init: info: /etc/cont-init.d/42-fail2ban exited 0 cont-init: info: running /etc/cont-init.d/43-crontabs cont-init: info: /etc/cont-init.d/43-crontabs exited 0 cont-init: info: running /etc/cont-init.d/45-nginx cont-init: info: /etc/cont-init.d/45-nginx exited 0 cont-init: info: running /etc/cont-init.d/50-certbot Variables set: 2 PGID=100 TZ=Asia/Calcutta URL=axxxxxxxxx.duckdns.org SUBDOMAINS=jellyfin EXTRA_DOMAINS= ONLY_SUBDOMAINS=false VALIDATION=http CERTPROVIDER= DNSPLUGIN= EMAIL=anchitsingh9@gmail.com STAGING=false Using Let's Encrypt as the cert provider SUBDOMAINS entered, processing SUBDOMAINS entered, processing Sub-domains processed are: -d jellyfin.axxxxxxxxx.duckdns.org E-mail address entered: anchitsingh9@gmail.com http validation is selected Certificate exists; parameters unchanged; starting nginx cont-init: info: /etc/cont-init.d/50-certbot exited 0 cont-init: info: running /etc/cont-init.d/55-permissions cont-init: info: /etc/cont-init.d/55-permissions exited 0 cont-init: info: running /etc/cont-init.d/60-renew The cert does not expire within the next day. Letting the cron script handle the renewal attempts overnight (2:08am). cont-init: info: /etc/cont-init.d/60-renew exited 0 cont-init: info: running /etc/cont-init.d/70-outdated cont-init: info: /etc/cont-init.d/70-outdated exited 0 cont-init: info: running /etc/cont-init.d/85-version-checks cont-init: info: /etc/cont-init.d/85-version-checks exited 0 cont-init: info: running /etc/cont-init.d/99-custom-files [custom-init] No custom files found, skipping... cont-init: info: /etc/cont-init.d/99-custom-files exited 0 s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service init-mods: starting s6-rc: info: service init-mods successfully started s6-rc: info: service init-mods-package-install: starting s6-rc: info: service init-mods-package-install successfully started s6-rc: info: service init-mods-end: starting s6-rc: info: service init-mods-end successfully started s6-rc: info: service init-services: starting s6-rc: info: service init-services successfully started s6-rc: info: service legacy-services: starting services-up: info: copying legacy longrun cron (no readiness notification) services-up: info: copying legacy longrun fail2ban (no readiness notification) services-up: info: copying legacy longrun nginx (no readiness notification) services-up: info: copying legacy longrun php-fpm (no readiness notification) s6-rc: info: service legacy-services successfully started s6-rc: info: service 99-ci-service-check: starting [ls.io-init] done. s6-rc: info: service 99-ci-service-check successfully started Server readyI still don't see how this is possible. If jellyfin.subdomain.duckdns.org is going to your swag page, this strongly suggests it's not on the proper NetworkMode
Can you post the output of these two conmmands
(the below assumes your swag container is named swag, and your jellyfin is named jellyfin...if they aren't, adjust commands as necessary. )
Codedocker inspect swag | grep NetworkModeRepeat for jellyfin
Codedocker inspect jellyfin | grep NetworkModeIt should look something likethis.
Coderoot@openmediavault:~# docker inspect swag | grep NetworkMode "NetworkMode": "swag_default", root@openmediavault:~# docker inspect emby | grep NetworkMode "NetworkMode": "swag_default", root@openmediavault:~# -
The problem is finally solved
Apparently, the problem was in nginx/resolver.conf
It was set to 8.8.8.8, 8.8.4.4
Changed it to 127.0.0.1.
Thank you so much for all the support.
-
-
anchits123
Hat das Label gelöst hinzugefügt. -
anchits123
Hat das Label OMV 6.x hinzugefügt.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!