Bad Gateway connecting to Jellyfin through Pangolin resources. #703

New Issue

GiteaMirror · 2025-11-13T12:08:15-06:00

GiteaMirror commented

2025-11-13 12:08:15 -06:00

Originally created by @krod1408 on GitHub (Sep 28, 2025).

Created a new resource through Pangolin...using local computer ip 192.168.x.xxx and port, I have tried 8096 and 8920 using http and https with the same results bad gateway. Do you guy's have an idea what I am doing wrong here. Thanks in advance.

Originally created by @krod1408 on GitHub (Sep 28, 2025). Created a new resource through Pangolin...using local computer ip 192.168.x.xxx and port, I have tried 8096 and 8920 using http and https with the same results bad gateway. Do you guy's have an idea what I am doing wrong here. Thanks in advance.

GiteaMirror commented

2025-11-13 12:08:15 -06:00

@krod1408 commented on GitHub (Sep 28, 2025):

I was also wondering if I need to edit the config files to add wildcard domains, when I look at the domains section it says Wildcard Domain Verified and seems to work fine. I am asking because the first time I installed Pangolin I did edit the files this time I have just left it as default.

@krod1408 commented on GitHub (Sep 28, 2025): I was also wondering if I need to edit the config files to add wildcard domains, when I look at the domains section it says Wildcard Domain Verified and seems to work fine. I am asking because the first time I installed Pangolin I did edit the files this time I have just left it as default.

GiteaMirror commented

2025-11-13 12:08:15 -06:00

@keonramses commented on GitHub (Oct 5, 2025):

Do you have Newt installed with Docker discovery enabled?

newt:
    image: fosrl/newt
    container_name: newt
    restart: unless-stopped
    environment:
      - PANGOLIN_ENDPOINT=${PANGOLIN_ENDPOINT}
      - NEWT_ID=${NEWT_ID}
      - NEWT_SECRET=${NEWT_SECRET}
      - ACCEPT_CLIENTS=true
      - DOCKER_SOCKET=/var/run/docker.sock
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
    network_mode: service:gerbil

@keonramses commented on GitHub (Oct 5, 2025): Do you have Newt installed with Docker discovery enabled? ``` newt: image: fosrl/newt container_name: newt restart: unless-stopped environment: - PANGOLIN_ENDPOINT=${PANGOLIN_ENDPOINT} - NEWT_ID=${NEWT_ID} - NEWT_SECRET=${NEWT_SECRET} - ACCEPT_CLIENTS=true - DOCKER_SOCKET=/var/run/docker.sock volumes: - /var/run/docker.sock:/var/run/docker.sock:ro network_mode: service:gerbil ```

GiteaMirror commented

2025-11-13 12:08:16 -06:00

@l3pr-org commented on GitHub (Oct 6, 2025):

Created a new resource through Pangolin...using local computer ip 192.168.x.xxx and port, I have tried 8096 and 8920 using http and https with the same results bad gateway. Do you guy's have an idea what I am doing wrong here. Thanks in advance.

Make sure you set the target method to http with the 'Enable SSL (https)' option toggled. I had the same issue and this is what fixed it.

@l3pr-org commented on GitHub (Oct 6, 2025): > Created a new resource through Pangolin...using local computer ip 192.168.x.xxx and port, I have tried 8096 and 8920 using http and https with the same results bad gateway. Do you guy's have an idea what I am doing wrong here. Thanks in advance. Make sure you set the target method to http with the 'Enable SSL (https)' option toggled. I had the same issue and this is what fixed it.

GiteaMirror commented

2025-11-13 12:08:16 -06:00

@AstralDestiny commented on GitHub (Oct 19, 2025):

Sorry why do you have newt in your gerbil's network? @keonramses IF you need local resolution just use a docker aliases over putting newt in network namespace it's going cause issues in by chance..

Make sure you also don't hairpin the service.. it'll cause latency and other issues.. @krod1408

@AstralDestiny commented on GitHub (Oct 19, 2025): Sorry why do you have newt in your gerbil's network? @keonramses IF you need local resolution just use a docker aliases over putting newt in network namespace it's going cause issues in by chance.. Make sure you also don't hairpin the service.. it'll cause latency and other issues.. @krod1408

GiteaMirror commented

2025-11-13 12:08:16 -06:00

@keonramses commented on GitHub (Oct 19, 2025):

You are correct. I have since corrected this on my end.

@keonramses commented on GitHub (Oct 19, 2025): You are correct. I have since corrected this on my end.

GiteaMirror commented

2025-11-13 12:08:16 -06:00

@github-actions[bot] commented on GitHub (Nov 3, 2025):

This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.

@github-actions[bot] commented on GitHub (Nov 3, 2025): This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.

GiteaMirror commented

2025-11-13 12:08:16 -06:00

@AstralDestiny commented on GitHub (Nov 7, 2025):

@krod1408 Is this all fixed now or do you still need help?

@AstralDestiny commented on GitHub (Nov 7, 2025): @krod1408 Is this all fixed now or do you still need help?