-
|
I've set up two traefik rules (two routers with a URL each) for my locally hosted jellyfin-vue instance. One works perfectly fine, using the other URL, jellyfin-vue loads, but just hangs on the splash-screen (without the loading screen indicator and logout button like regular loading) I'm clueless to why that is. Atm I've set up JV to connect to a default server using docker DNS (DEFAULT_SERVERS=jellyfin:8096), this should be fine, as jellyfin-vue proxies traffic to the JF instance, right? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
|
The DEFAULT_SERVERS is relative to the client loading Jellyfin Vue, not the server serving Jellyfin Vue's assets. As mentioned in https://github.com/jellyfin/jellyfin-vue/wiki/Configuration#what-you-can-configure, you must test by adding a server manually, but the wording could be improved indeed. There's no relationship between jellyfin vue container and jellyfin, jellyfin vue is just an nginx container serving static assets, after your browser loaded all the assets, all the communication is between your browser and server (see https://github.com/jellyfin/jellyfin-vue?tab=readme-ov-file#privacy-disclaimer- as well). |
Beta Was this translation helpful? Give feedback.
-
|
Oh, that explains it, thanks! Really weird though, as I have been able to reach http://jellyfin:8096 through my browser then? Might have been an old cached version, but I'm a 100% sure I deleted browser cache in between testing, yet it still worked |
Beta Was this translation helpful? Give feedback.
-
|
Can you try accessing your deployed instance without the env vat and inputting manually the server address with exactly what you used in the env var? jellyfin:8096 != http://Jellyfin:8096, perhaps the validation fails for the former but succeeds with the latter. In either case, remember this will only work on browsers accessing on LAN. |
Beta Was this translation helpful? Give feedback.
-
|
Unable to reach either anymore. But it's weird, as I should never have been able to - docker is installed on my server, and the Jellyfin port is only exposed internally to the docker network. There's no funky DNS resolution rules which should've enabled this either. And the VPN server I'm connecting to is running on my firewall, not the docker host anymore. Probably a weird error on my side. Just wondering how that was possible... Using the FQDN to connect to the jellyfin-server through jellyfin-vue by connecting out to the internet is working well now :) |
Beta Was this translation helpful? Give feedback.
-
|
@alvitali So it's just a matter of setting the FQDN in the environment variable then. |
Beta Was this translation helpful? Give feedback.
The DEFAULT_SERVERS is relative to the client loading Jellyfin Vue, not the server serving Jellyfin Vue's assets. As mentioned in https://github.com/jellyfin/jellyfin-vue/wiki/Configuration#what-you-can-configure, you must test by adding a server manually, but the wording could be improved indeed. There's no relationship between jellyfin vue container and jellyfin, jellyfin vue is just an nginx container serving static assets, after your browser loaded all the assets, all the communication is between your browser and server (see https://github.com/jellyfin/jellyfin-vue?tab=readme-ov-file#privacy-disclaimer- as well).