Web Access Problem - Printable Version +- Jellyfin Forum (https://forum.jellyfin.org) +-- Forum: Support (https://forum.jellyfin.org/f-support) +--- Forum: General Questions (https://forum.jellyfin.org/f-general-questions) +--- Thread: Web Access Problem (/t-web-access-problem) |
Web Access Problem - ebeachlr - 2024-08-21 I cannot connect to the Jellyfin server web content. When I open a terminal window and type Jellyfin I get back the following: [09:59:46] [INF] [1] Main: Jellyfin version: 10.9.9 [09:59:46] [INF] [1] Main: Environment Variables: ["[JELLYFIN_LOG_DIR, /home/ebeachlr/.local/share/jellyfin/log]"] [09:59:46] [INF] [1] Main: Arguments: ["/usr/lib/jellyfin/bin/jellyfin.dll"] [09:59:46] [INF] [1] Main: Operating system: Linux Mint 21.3 [09:59:46] [INF] [1] Main: Architecture: X64 [09:59:46] [INF] [1] Main: 64-Bit Process: True [09:59:46] [INF] [1] Main: User Interactive: True [09:59:46] [INF] [1] Main: Processor count: 16 [09:59:46] [INF] [1] Main: Program data path: /home/ebeachlr/.local/share/jellyfin [09:59:46] [INF] [1] Main: Log directory path: /home/ebeachlr/.local/share/jellyfin/log [09:59:46] [INF] [1] Main: Config directory path: /home/ebeachlr/.config/jellyfin [09:59:46] [INF] [1] Main: Cache path: /home/ebeachlr/.cache/jellyfin [09:59:46] [INF] [1] Main: Web resources path: /usr/lib/jellyfin/bin/jellyfin-web [09:59:46] [INF] [1] Main: Application directory: /usr/lib/jellyfin/bin/ [09:59:46] [ERR] [1] Main: The server is expected to host the web client, but the provided content directory is either invalid or empty: /usr/lib/jellyfin/bin/jellyfin-web. If you do not want to host the web client with the server, you may set the '--nowebclient' command line flag, or set'hostwebclient=false' in your config settings The ERR message is correct, the /usr/lib/jellyfin/bin/jellyfin-web directory does not exist. How do I fix this problem? Any help will be appreciated. RE: Web Access Problem - TheDreadPirate - 2024-08-21 How are you starting Jellyfin and how did you install Jellyfin? If you are simply typing "jellyfin", that is not going to work. You need to start jellyfin with systemctl. sudo systemctl start jellyfin RE: Web Access Problem - ebeachlr - 2024-08-21 Jellyfin is being started at boot time. The Jellyfin server was installed via Curl as you previously instructed. The server appears to be functioning correctly. Results of systemctl status Jellyfin are: Loaded: loaded (/lib/systemd/system/jellyfin.service; enabled; vendor pres> Drop-In: /etc/systemd/system/jellyfin.service.d └─jellyfin.service.conf Active: active (running) since Wed 2024-08-21 09:53:30 EDT; 6h ago Main PID: 3779 (jellyfin) My TV was able to connect with the system before the uninstall of Linux Mint Jellyfin and the subsequent installation of the server via Curl. It now cannot jellyfin from the TV even though the other Sansung devices on the network can. If you have any suggestions, I am willing to try. I have not been able to find a way to purge the cache on the TV web browser. Memory: 2.0G CPU: 15min 27.828s CGroup: /system.slice/jellyfin.service └─3779 /usr/bin/jellyfin --webdir=/usr/share/jellyfin/web --ffmpeg> Aug 21 14:23:28 Janeway jellyfin[3779]: at MediaBrowser.XbmcMetadata.Savers.> Aug 21 14:23:28 Janeway jellyfin[3779]: at MediaBrowser.XbmcMetadata.Savers.> Aug 21 14:23:28 Janeway jellyfin[3779]: at MediaBrowser.Providers.Manager.Pr> Aug 21 14:27:58 Janeway jellyfin[3779]: [14:27:58] [WRN] [23] Emby.Server.Imple> Aug 21 14:27:58 Janeway jellyfin[3779]: [14:27:58] [INF] [23] Emby.Server.Imple> Aug 21 14:34:42 Janeway jellyfin[3779]: [14:34:42] [INF] [35] Emby.Server.Imple> Aug 21 14:55:03 Janeway jellyfin[3779]: [14:55:03] [INF] [51] Emby.Server.Imple> Aug 21 14:55:03 Janeway jellyfin[3779]: [14:55:03] [INF] [33] MediaBrowser.Medi> Aug 21 15:19:08 Janeway jellyfin[3779]: [15:19:08] [INF] [20] Emby.Server.Imple> Aug 21 15:19:08 Janeway jellyfin[3779]: [15:19:08] [INF] [20] MediaBrowser.Medi> lines 1-22/22 (END) RE: Web Access Problem - TheDreadPirate - 2024-08-21 Jellyfin is already running via systemctl. Typing "jellyfin", as you stated in the opening post, will trigger it to try to run another instance. But without all of the variables and options jellyfin expecting. If you're having trouble accessing the instance already running, double check that your server's LAN IP didn't change and that port 8096 is open on the firewall. Code: sudo ufw status If UFW is not enabled or port 8096 hasn't been allowed through: Code: sudo ufw enable |