[GH-ISSUE #445] Server error with CSS files with new version #274

New issue

Closed

opened 2026-02-25 23:33:50 +03:00 by kerem · 4 comments

kerem commented

2026-02-25 23:33:50 +03:00

Owner

Originally created by @pgrunm on GitHub (Jun 28, 2022).
Original GitHub issue: https://github.com/go-shiori/shiori/issues/445

Hello, I'm running Shiori with my Raspberry pi behind a Caddy reverse proxy. I followed the guide here to run Shiori behind Caddy as reverse proxy.

Until the last update everything was fine, but since 1.5.3 any CSS file isn't loaded correctly if you run Shiori like this shiori serve --webroot /shiori/ parameter. In Firefox I can see internal server errors (HTTP code 500) and this is also displayed on the console but no further information.

The page as result looks like this now:

And now the great part: If you run Shiori without the --webroot /shiori/ parameter, everything is fine. I also verified this on my local machine, once with the parameter and once without, same result as with the Raspberry Pi, without reverse proxy of course.

Steps to reproduce

Download Shiori (if not already in path or something)
Extract and run with to test: shiori serve --webroot /shiori/ and open up Shiori http://127.0.0.1:8080/shiori/. This is how no CSS is displayed.
To verify the working state run Shiori like this: shiori serve and open Shiori again.
If I try to open the source-sans-pro.min.css file as an example my browser says the following: open /css/source-sans-pro.min.css: invalid name. The corresponding log entry from the containers log is:
time="2022-06-28T17:43:40Z" level=warning msg="GET /shiori/css/source-sans-pro.min.css" proto=HTTP/1.1 remote="172.19.0.2:43460" reqlen=0 size=48 status=500

Originally created by @pgrunm on GitHub (Jun 28, 2022). Original GitHub issue: https://github.com/go-shiori/shiori/issues/445 Hello, I'm running Shiori with my Raspberry pi behind a Caddy reverse proxy. I followed the guide [here](https://github.com/go-shiori/shiori/pull/374#issuecomment-1044704202) to run Shiori behind Caddy as reverse proxy. Until the last update everything was fine, but since 1.5.3 any CSS file isn't loaded correctly if you run Shiori like this shiori serve --webroot /shiori/ parameter. In Firefox I can see internal server errors (HTTP code 500) and this is also displayed on the console but no further information. ![image](https://user-images.githubusercontent.com/8317771/176247663-d58fe684-c83e-469a-89af-b57dd849e640.png) The page as result looks like this now: ![image](https://user-images.githubusercontent.com/8317771/176108818-f3b1e7b2-b8fb-4ee4-b777-950eba255deb.png) And now the great part: If you run Shiori without the --webroot /shiori/ parameter, everything is fine. I also verified this on my local machine, once with the parameter and once without, same result as with the Raspberry Pi, without reverse proxy of course. ## Steps to reproduce - Download Shiori (if not already in path or something) - Extract and run with to test: shiori serve --webroot /shiori/ and open up Shiori http://127.0.0.1:8080/shiori/. This is how no CSS is displayed. - To verify the working state run Shiori like this: shiori serve and open Shiori again. - If I try to open the `source-sans-pro.min.css` file as an example my browser says the following: `open /css/source-sans-pro.min.css: invalid name`. The corresponding log entry from the containers log is: `time="2022-06-28T17:43:40Z" level=warning msg="GET /shiori/css/source-sans-pro.min.css" proto=HTTP/1.1 remote="172.19.0.2:43460" reqlen=0 size=48 status=500`

kerem closed this issue

2026-02-25 23:33:50 +03:00

kerem commented

2026-02-25 23:33:51 +03:00

Author

Owner

@hulb commented on GitHub (Jul 6, 2022):

Sorry for your trouble, it will be fixed when the PR merged

@hulb commented on GitHub (Jul 6, 2022): Sorry for your trouble, it will be fixed when the PR merged

kerem commented

2026-02-25 23:33:51 +03:00

Author

Owner

@pgrunm commented on GitHub (Jul 7, 2022):

No problem, I appreciate your upcoming fix. :-)

@pgrunm commented on GitHub (Jul 7, 2022): No problem, I appreciate your upcoming fix. :-)

kerem commented

2026-02-25 23:33:51 +03:00

Author

Owner

@fmartingr commented on GitHub (Jul 8, 2022):

Hey @pgrunm, I just merged @hulb's fix. Please check if this solves it, if not, please reopen the issue so we can take a look.

@fmartingr commented on GitHub (Jul 8, 2022): Hey @pgrunm, I just merged @hulb's fix. Please check if this solves it, if not, please reopen the issue so we can take a look.

kerem commented

2026-02-25 23:33:51 +03:00

Author

Owner

@pgrunm commented on GitHub (Jul 8, 2022):

Works great, thank you very much! 👍

@pgrunm commented on GitHub (Jul 8, 2022): Works great, thank you very much! 👍

kerem referenced this issue

2026-02-25 23:35:19 +03:00

[PR #703] [CLOSED] #WIP: Documentation revamp #741