2024-09-06, 11:48 PM
(This post was last modified: 2024-09-06, 11:48 PM by TheDreadPirate.)
I looked at the SWAG git and couldn't find anything in the nginx config that would cause this.
When this happens again, can you open a bash shell into both the SWAG container and Jellyfin container and run these commands.
This will open a bash shell into the container. Replace "jellyfin" with "swag" to open a bash shell for that container.
Now we are verifying that the container's networking isn't broken and that it can actually reach TMDB.
Run this command in the container.
When this happens again, can you open a bash shell into both the SWAG container and Jellyfin container and run these commands.
This will open a bash shell into the container. Replace "jellyfin" with "swag" to open a bash shell for that container.
Code:
sudo docker exec -it jellyfin bash
Now we are verifying that the container's networking isn't broken and that it can actually reach TMDB.
Run this command in the container.
Code:
curl -vvv https://image.tmdb.org/t/p/original/uqIVJR1fmkiwpcIsIcV0vxiyY4z.jpg -o /tmp/futurama.jpg
ls -l /tmp/