Suwayomi-Server: [Bug] Wrong MIME Type for WebUI

Device information

  • Tachidesk version: Tachidesk-Server-v0.7.0-r1197.jar & Tachidesk-Server-v0.7.0-r1424.jar (preview)
  • Server Operating System: Fedora Kinoite 39
  • Server Desktop Environment: N/A
  • Server JVM version: OpenJDK 21.0.1
  • Client Operating System: Fedora Kinoite 39
  • Client Web Browser: Mozilla Firefox 119.0.1

Steps to reproduce

  1. Download jar and the latest version of OpenJDK from .
  2. Run the jar.

Expected behavior

The web ui should load normally.

Actual behavior

The tab Tachidesk opens is blank, accessing other pages via url gives the same result. Firefox’s console shows: The stylesheet "http://127.0.0.1:4567/static/css/2.8c49bb0a.chunk.css" was not loaded because its MIME type, "text/html", is not "text/css". The stylesheet "http://127.0.0.1:4567/static/css/main.efc3b6a7.chunk.css" was not loaded because its MIME type, "text/html", is not "text/css". The script from "http://127.0.0.1:4567/static/js/2.8953c29e.chunk.js" was loaded even though its MIME type ("text/html") is not a valid JavaScript MIME type. The script from "http://127.0.0.1:4567/static/js/main.9b92ea11.chunk.js" was loaded even though its MIME type ("text/html") is not a valid JavaScript MIME type. Uncaught SyntaxError: expected expression, got '<' Uncaught SyntaxError: expected expression, got '<'

Other details

I have tried deleting all files in the WebUI folder and restarting, as well as using the Sorayomi and preview WebUI. This was tested with both preinstalled and flatpak Firefox. I tested in a VM and on a HP laptop; both were clean installs.

My personal server on Arch Linux has not faced this issue, so I presume it has something to do with Fedora.

About this issue

Most upvoted comments

After coming back to this last week, I believe I found the problem. In short, atomic versions of Fedora set $HOME to /var/home, and symlinks /home to it. However, aside from Silverblue, they create users during installation, and that change has not yet been added to the installer, so initial users still have $HOME as /home (users created after install are not affected).

My wonder is why this is an issue; there should be no functional difference between the two, and other programs I use work as they should with this ‘bug’. Maybe symlinks break how the server delivers files?