Can't load EPUBs under HTTPS

gotson / komga

Media server for comics/mangas/BDs/magazines/eBooks with API, OPDS and Kobo Sync support

https://komga.org

MIT License

4.07k stars 240 forks source link

Can't load EPUBs under HTTPS #1638

Closed DCS-MANGO closed 3 months ago

DCS-MANGO commented 3 months ago

Steps to reproduce

can read epubs in HTTP, but can't in HTTPS

Expected behavior

setup nginx or, caddy as you said, can not load in HTTPS.

Actual behavior

I also found the similar issue "https://github.com/gotson/komga/issues/1453" but i could not solve that.

Logs

No response

Komga version

1.11.2

Operating system

synology linux

Installation method

Docker

Other details

No response

Acknowledgements

[X] I have searched the existing issues (open AND closed) and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a short but informative title.
[X] I have checked the FAQ.
[X] I have updated the app to the latest version.
[X] I will fill out all of the requested information in this form.

gotson commented 3 months ago

most likely a reverse proxy issue, please provide browser console logs, server logs, reverse proxy configuration or additional details

DCS-MANGO commented 3 months ago

Thanks a lot. Here are my logos. browser console log reverse proxy setting

gotson commented 3 months ago

i can't read korean, but it seems there is some issue with CORS and 2 ports being used, 8342 and 8341. What are those 2 ports ?

DCS-MANGO commented 3 months ago

8342 is for HTTPS and 8341 is for HTTP.

I made komga server on HTTPS and redirect to HTTPS.

gotson commented 3 months ago

I made komga server on HTTPS

so the Synology reverse proxy connects to local Komga via HTTPS ? that kinda nullifies the need for a reverse proxy

DCS-MANGO commented 3 months ago

so, what should I do? I don't have any kinds of knowledges about network. Should I try with kind of Nginx(caddy) step by step?

gotson commented 3 months ago

the reverse proxy can normally handle TLS termination and use plain HTTP locally. You might need to lookup for some guides about how to do this with Synology's built in feature.

DCS-MANGO commented 3 months ago

Thanks for your help. I fixed the issue by just changing port 8342 to 443 for HTTPS. It works!!