SOLVED: Web server stuck at logo (remotely and locally)

[supahfox]

• The version of Jellyfin you are running (e.g. 10.8.10): 10.9.11
  
• Your installation method and platform (e.g. Linux Docker, Debian repository, Windows installer, etc.): Windows Installer
  
• A brief description of the issue as your thread subject, using the description for additional important context only if required: Web server stuck at logo (remotely and locally)
  
• A full explanation of what is happening, versus what you expect to happen: So I can't get Jellyfin to work as it's stuck at logo everytime I launch it. I've already deleted my data folder, reinstalled Jellyfin, deleted my browser's cache, but nothing
  
• What client(s) you are using and how the issue manifests: Browser (Brave and Firefox), iOS client. All have the same issue
  
• Any other context you might think is relevant: https://pastebin.com/P1DJEQWT (logs, they're in debug mode)
  

[TheDreadPirate]

I don't see any connection attempts in your log. Is the Windows firewall open for Jellyfin?

Click Start > type Resource Monitor > click Network tab > expand Listening ports table

Find jellyfin.exe on port 8096, what does it say in the firewall status column?

[supahfox]

I don't see any connection attempts in your log.  Is the Windows firewall open for Jellyfin?

Click Start > type Resource Monitor > click Network tab > expand Listening ports table

Find jellyfin.exe on port 8096, what does it say in the firewall status column?

Ports are enabled and unrestricted

[TheDreadPirate]

Is your server's address static? Are you using the correct address?

http://192.168.1.20:8096

Do you have a VPN running on the server? How about a pihole on your network?

[supahfox]

Okay, it's seems that now it's working locally but not remotely with my own address.
And yes, I'm using a reverse proxy

---

Code:

#user  nobody;
worker_processes  1;

#error_log  logs/error.log;
#error_log  logs/error.log  notice;
#error_log  logs/error.log  info;

#pid        logs/nginx.pid;


events {
    worker_connections  1024;
}


http {
    include      mime.types;
    default_type  application/octet-stream;

    # Logging settings
    access_log  logs/access.log;
    error_log  logs/error.log;

    # Enable Gzip compression
    gzip on;
    gzip_vary on;
    gzip_proxied any;
    gzip_types text/plain text/css application/json application/javascript application/x-javascript text/xml application/xml application/xml+rss text/javascript;

    # SSL settings
    ssl_certificate      C:/nginx/cert/cert.pem; # Update with your SSL certificate path
    ssl_certificate_key  C:/nginx/cert/private.pem;    # Update with your SSL key path
    ssl_trusted_certificate C:/nginx/cert/fullchain.pem;
    ssl_protocols        TLSv1 TLSv1.1 TLSv1.2;        # Adjust protocols as needed
    ssl_ciphers          HIGH:!aNULL:!MD5;

    # Server block for HTTPS
    server {
        listen      443 ssl;
        server_name  supahfox.********.com; # Replace with your domain

        # Location block to handle all requests
        location / {
            # Reverse proxy configuration
            proxy_pass http://localhost:8096; # Replace with your backend server address
            proxy_set_header Host $host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-Forwarded-Proto $scheme;
        }
    }

    # Server block for HTTP to redirect to HTTPS
    server {
        listen      80;
        server_name supahfox.********; # Replace with your domain
        return      301 https://$host$request_uri;
    }
}

---

I'm not using any kind of vpn or pihole

[supahfox]

Is your server's address static?  Are you using the correct address?
http://192.168.1.20:8096
Do you have a VPN running on the server?  How about a pihole on your network?

ip address is static, yes

[TheDreadPirate]

While not strictly necessary for basic connections, you're missing the /socket block. You are also missing some proxy_set_header options in your / location.

Look over our Nginx docs and try making adjustments to your server block accordingly.

https://jellyfin.org/docs/general/networking/nginx/

For the moment, focus on mirroring the / and /socket location blocks in our documentation. Replace $jellyfin with localhost, as you currently have it, or you can set $jellyfin to equal local host (in our documentation).

I'm not 100% certain whether the under-configured Nginx is the problem, but we want to eliminate that as a factor.

Unrelated, gzip compression should be disabled for security reasons. It weakens encryption.

[supahfox]

Working like a charm now!

Idk what was the error but at least it's working as before

[SpecialBrownie]

I am facing the exact same problem today. Jellyfin was working until last night but this morning, it went kaput.

1. Win 10, 8 GB ram
2. Static IP
3. Firewall listening port - allowed, not restricted
4. Logs have no errors
5. Not accessible using localhost or the ipaddress on the installed machine
6. Remote comp on the local network gets the same splash screen with nothing loading
7. I didn't change the port, didn't install anything new on the computer that might have changed the port so it's still on the default one


This happened once in the past on my win11 machine too and I ended up blaming some update and reinstalled on win 10 machine with all updates turned off. Looks like it's a JF issue as it happens often regardless of what's going on.

---

[SpecialBrownie]

update on this:

Browser used earlier: Brave (fully updated) on both machines - stuck on the splash screen
Browser retested on: Edge (fully updated) on both machines - JFin works

Looks like it's a browser issue, weird!