2023-11-29, 08:49 AM
(This post was last modified: 2023-11-29, 08:58 AM by ohshitgorillas. Edited 1 time in total.)
I am currently traveling in China while my Jellyfin server is at home in the USA. I am trying like hell to watch some of my content but I am running into several issues, but I'll just focus on the most confusing one here: inability to access the remote server.
On the server end, I am running Jellyfin inside docker, with host networking, and update it on a daily basis. I also have nginx set up as a reverse https proxy for remote access. The docker-compose file is below.
On the client end, I am using both my Android tablet and a Google Chromecast 4K.
Both client apps fail to see the server located at its address, let's call it https://jf.ohshitgorillas.com. I enter "https://jf.ohshitgorillas.com:42069" into the app, and the app tells me that the server can't be found. This also fails if I type in my IPv4 address. The only way I can get the Jellyfin apps to recognize the server is to connect to WireGuard and type in the server's local address, however, my WireGuard server is currently getting awful speeds and I can't stream anything while connected, so this isn't exactly a solution.
Here's the kicker: it's definitely, 100% there. I asked my friend with remote access to test it out and he said he had no problems connecting and streaming 4K material. I can even visit the address in a browser and get the login page. It's only the apps on my tablet and my Chromecast that can't see it.
So if the server is located at the address, why can't the Jellyfin client apps see it?
docker-compose.yml:
On the server end, I am running Jellyfin inside docker, with host networking, and update it on a daily basis. I also have nginx set up as a reverse https proxy for remote access. The docker-compose file is below.
On the client end, I am using both my Android tablet and a Google Chromecast 4K.
Both client apps fail to see the server located at its address, let's call it https://jf.ohshitgorillas.com. I enter "https://jf.ohshitgorillas.com:42069" into the app, and the app tells me that the server can't be found. This also fails if I type in my IPv4 address. The only way I can get the Jellyfin apps to recognize the server is to connect to WireGuard and type in the server's local address, however, my WireGuard server is currently getting awful speeds and I can't stream anything while connected, so this isn't exactly a solution.
Here's the kicker: it's definitely, 100% there. I asked my friend with remote access to test it out and he said he had no problems connecting and streaming 4K material. I can even visit the address in a browser and get the login page. It's only the apps on my tablet and my Chromecast that can't see it.
So if the server is located at the address, why can't the Jellyfin client apps see it?
docker-compose.yml:
Code:
version: "2.1"
services:
jellyfin_ddns4:
image: sjmayotte/route53-dynamic-dns:latest
container_name: jellyfin_ddns4
env_file:
- ./4.env
restart: unless-stopped
logging:
driver: gelf
options:
gelf-address: "udp://10.0.0.1:12201"
tag: "jellyfin_ddns4"
jellyfin_ddns6:
image: sjmayotte/route53-dynamic-dns:latest
container_name: jellyfin_ddns6
env_file:
- ./6.env
network_mode: host
restart: unless-stopped
logging:
driver: gelf
options:
gelf-address: "udp://10.0.0.1:12201"
tag: "jellyfin_ddns6"
jellyfin:
image: linuxserver/jellyfin:latest
container_name: jellyfin
runtime: nvidia
environment:
- PUID=1000
- PGID=1000
- TZ=America/Los_Angeles
- NVIDIA_VISIBLE_DEVICES=all
- NVIDIA_DRIVER_CAPABILITIES=all
volumes:
- ./config:/config
- /srv/media/music:/music
- /srv/media/tv:/tv
- /srv/media/movies:/movies
network_mode: host
depends_on:
- jellyfin_ddns4
- jellyfin_ddns6
restart: unless-stopped
nginx:
container_name: nginx_jellyfin
image: nginx:latest
volumes:
- ./nginx/log:/var/log/nginx
- ./nginx/keys:/config/keys
- ./nginx/nginx.conf:/etc/nginx/nginx.conf
ports:
- 42069:80
depends_on:
- jellyfin
restart: unless-stopped