SOLVED: WebOS client can't connect to a nightly build server (404)

[pulpul]

I'm trying to run jellyfin linuxserver.io nightly build. The container starts up fine and sets up the server. I can connect to it with my: desktop jellyfin client, computer web browser, android jellyfin client, webos web browser but NOT webos jellyfin client. Webos client returns "server returned 404, are you connecting to a jellyfin server?".

Has anyone come across similiar problems and know a workaround?

I was eager to test the new WebOS HLS-fixes which were committed to the source last week, but I'm having trouble connecting to the server with my webos client. https://github.com/jellyfin/jellyfin-web...3f75b00c9f

[TheDreadPirate]

Are you adding the port at the end of the URL? Are you using a reverse proxy?

I don't see why you wouldn't be able to connect through the app since the app simply displays jellyfin-web from the server.

[pulpul]

Are you adding the port at the end of the URL?  Are you using a reverse proxy?

I don't see why you wouldn't be able to connect through the app since the app simply displays jellyfin-web from the server.

Yes I am adding the port, no proxies. I have tried to reinstall the webos app, connecting using the url with http:// and without. I have a stable release of jellyfin installed next to it which it connects to normally every time, but no luck with the nightly build.

The strangest thing is that I can connect to the server with every other client, but not with webos client. I wonder if the webos client tries to use a direct url (i.e.http://192.168.1.75:8096/web/#/login.html) and the url has changed?

[TheDreadPirate]

If I had to guess, probably the "/system/info/public" endpoint.

I don't have an unstable build going at the moment, though I plan on standing one up soon.

[pulpul]

If I had to guess, probably the "/system/info/public" endpoint.

I don't have an unstable build going at the moment, though I plan on standing one up soon.

I browsed the webos client source and figured it out, lol.

The nightly build for some reason is missing the manifest.json, which webos client tries to get. I added it from the stable build and it works.

Code:

function getManifest(baseurl) {
    curr_req = ajax.request(normalizeUrl(baseurl + "/web/manifest.json"), {
        method: "GET",
        success: function (data) {
            handleSuccessManifest(data, baseurl);
        },
        error: handleFailure,
        abort: handleAbort,
        timeout: 5000
    });
}

[Tristan1019]

Where did you add the code? I’m having the same issue, I have the latest nightly build on Unraid and if I try to go back to stable it tells me that I can’t downgrade on I think it was library.db and won’t work on any client but when I leave it on the nightly it will only not work on WebOS. I tried to add this code in a few areas but it told me that it was longer than expected after I added the new lines and would not work.

[brunomlopes]

Where did you add the code? I’m having the same issue, I have the latest nightly build on Unraid and if I try to go back to stable it tells me that I can’t downgrade on I think it was library.db and won’t work on any client but when I leave it on the nightly it will only not work on WebOS. I tried to add this code in a few areas but it told me that it was longer than expected after I added the new lines and would not work.

I think the file is getting transformed by the build process and ends up with a hashed name like on the jellyfin-web folder. In my case, I navigated to the jellyfin-web folder and copied the file with the hash in the name to manifest.json and it started working: cp manifest.2a3e4c70f1221a29cd12.json  manifest.json

[interrobang]

https://github.com/jellyfin/jellyfin-web/pull/6845 fixes this