Closed franciscomfcmaia closed 2 weeks ago
can you get the logs from the Javascript console of the browser, and the XHR network requests made by the browser?
Hi @gotson,
I think the javascript console might be hiding the reason for this error.....but the 404 is really strange....
Okay @gotson,
I had a look at the X-Frame-Options on my traefik side. I made the following addition for anyone in this situation:
---
apiVersion: traefik.io/v1alpha1
kind: Middleware
metadata:
name: komga-middleware
namespace: media
spec:
headers:
customRequestHeaders:
X-Forwarded-Proto: https
customFrameOptionsValue: "ALLOW-FROM https://read.${SECRET_DOMAIN}" # This can still be kept if you want to allow this specific origin
contentSecurityPolicy: "frame-ancestors 'self' https://read.${SECRET_DOMAIN};" # Allow framing from self and specified URL
Books are now opening!!! 👍🏼
However, I still see the 404 error but the webpage works fine. Maybe an old call still on the webui code?
but the 404 is really strange
this is expected behaviour if the series has only 1 book
Steps to reproduce
When attempting to open any book in Komga, the screen remains blank [with a simple warning sign in the middle], and the Chrome web traffic logs show a 404 error when trying to load the next or previous book.
1.14.0
Expected behavior
The book should display correctly without any 404 errors, and navigating to the next or previous book should function properly.
Actual behavior
/api/v1/books/{bookId}/next
and/api/v1/books/{bookId}/previous
.Error response from the logs:
Logs
komga_cleaned.log
Komga version
1.14.0
Operating system
Talos OS (K8S, Docker)
Installation method
jar
Other details
My Deployment:
My Reverse Proxy Config:
Acknowledgements