SOLVED: Android app doesn't load anymore. Plus web address changed after update

[ovingiv]

Found this today.

https://jellyfin.org/posts/jellyfin-rele...ng-changes

The last entry in that section.

https://github.com/jellyfin/jellyfin/issues/11540

Try removing this block from your nginx config.

Code:

    location = /web/ {
        # Proxy main Jellyfin traffic
        proxy_pass http://$jellyfin:8096/web/index.html;
        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;
        proxy_set_header X-Forwarded-Protocol $scheme;
        proxy_set_header X-Forwarded-Host $http_host;
    }

I apologize for the very late reply. 

Making a backup of my nginx file and removing that block of code then restarting both nginx and jellyfin did not fix my issue. 
In fact its like almost nothing happened as it still redirects to "https://sub.domain.com/web/index.html#/home.html"

[TheDreadPirate]

What version of Jellyfin are you on? There was a bug in .1 or .2 that broke Android specifically. It was fixed in .3, IIRC.

[ovingiv]

I recently just updated to 10.9.6 and also remade the nginx file to what was updated in the documents and that actually broke everything for me. On top of it I actually had to reinsert the "location = /web/ {" block of text as it gave me issues otherwise.

Here's what I made for the new nginx file: https://pastebin.com/C0esCTa7
It initially gave me an error for line 14 complaining about it didn't know what it was so I did move it to where it was between "ssl" and ";" in lines 12 and 13
Running "sudo nginx -t" gave an error for jellyfin.ovingivhomelab.page 80 and 443 being used? But it passed the test nonetheless. Upon restarting both nginx and jellyfin it refused to load any page and any url related to jellyfin gave 404 or ERR_TOO_MANY_REDIRECTS.

[TheDreadPirate]

Comment out this block. I had problems with it when I originally set up my Nginx proxy and just removed it entirely.

Code:

location = / {
        return 302 http://$host/web/;
        #return 302 https://$host/web/;
    }

[ovingiv]

So making the subsequent changes to the new conf file and fiddling with other errors I did get the new conf file working. But now I can't use either the desktop app nor the android app, but Roku still works.

[TheDreadPirate]

Try commenting out this block.

Code:

# COOP/COEP. Disable if you use external plugins/images/assets
    add_header Cross-Origin-Opener-Policy "same-origin" always;
    add_header Cross-Origin-Embedder-Policy "require-corp" always;
    add_header Cross-Origin-Resource-Policy "same-origin" always;

[ovingiv]

Try commenting out this block.

Code:

    # COOP/COEP. Disable if you use external plugins/images/assets
    add_header Cross-Origin-Opener-Policy "same-origin" always;
    add_header Cross-Origin-Embedder-Policy "require-corp" always;
    add_header Cross-Origin-Resource-Policy "same-origin" always;

So doing that didn't do anything. I'm thinking its related to the fact that when I try to go to my site it just gives me a 404 and I need to enter a certain web address to access it.

[TheDreadPirate]

Just remembered something. In your nginx config add in a cert file that contains the full chain.

Code:

ssl_certificate /etc/letsencrypt/live/jellyfin.domain.tld/fullchain.pem; #### like this one
    ssl_certificate_key /etc/letsencrypt/live/jellyfin.domain.tld/privkey.pem;
    ssl_trusted_certificate /etc/letsencrypt/live/domain.tld-0001/chain.pem;
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

[ovingiv]

Hello again.

I decided to simmer on this issue a while and take a break from it. Now I want to take a crack at it again.

I had backed up everything inside "/var/lib/jellyfin/data/" and apt remove jellyfin && apt autopurge.

I then setup a docker for jellyfin from the official repo and got that up and running along with for the sake of consistency used the same ports as required from Here. Also setup the 5 drive locations of my media folders.

Restored the jellyfin.db and library.db. Started the container and after a moment I was able to login with my user with everything as it was as far as watched/currently watching/next episode.

But I was using http 8096. I had then setup https 8920 with my PKCS #12 file and password then restarted jellyfin. It moved me to https 8920. All that was left was to get it back to my domain with the newest Nginx HTTPS config and changed the few lines needed to match my domain and letsencrypt locations. After trying to "ln -s" to many failures as it wasn't linking for whatever reason and just "ln", restarted nginx, restarted jellyfin. I was now using my domain which still directs me to "jellyfin.domain.com/web/index.html#/home.html". And when trying to just go to "jellyfin.domain.com/" it tries to load "jellyfin.domain.com/web/" and stops. I then need to manually add "index.html" to the end and it works.

Accessing from a roku still works without an issue. But both android app and desktop app refuse to connect still having the same issues. I'm to the point to ask you to look at my system over ssh to help me understand what I'm doing wrong.

Here's my updated conf file for nginx: Pastebin

[TheDreadPirate]

Starting with 10.9 you need to remove the /web location.

Code:

# location block for /web - This is purely for aesthetics so /web/#!/ works instead of having to go to /web/index.html/#!/
      location ~ ^/web/$ {
          # Proxy main Jellyfin traffic
          proxy_pass http://$jellyfin:8096/web/index.html/;
          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;
          proxy_set_header X-Forwarded-Protocol $scheme;
          proxy_set_header X-Forwarded-Host $http_host;
      }

Our nginx documentation was updated accordingly.

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

The change was also announced in the 10.9 blog post in May.

https://jellyfin.org/posts/jellyfin-rele...ng-changes

Nginx reverse proxy users: If you have a block in your nginx config that begins with location ~ ^/web/$ { and the comment # location block for /web - This is purely for aesthetics [...], please remove that block as it will cause occasional issues with 404's and/or slow performance on 10.9.z.