-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Solved] Kobo sync and reverse proxy #1891
Comments
OK I think I have found the right configuration.
I have listed my configuration below so that it can be of help to other users. Nginx Proxy Manager
Calibre-web
Kobo
|
I use NPM set up also and tried your settings under the advanced tab. Everything synchronises well. However when I add my oauth server settings to the advanced tab, sync starts but nothing happens. proxy_buffer_size 128k; OAuth Snippet Start ----------------------------------------------------location /oauth2/ { location = /oauth2/auth { location / {
} Oauth Snippet End |
@norangebit did you experience issues with getting redirected the login screen? I am new to NPM as proxy manager and experience this issue (login works, every other page I load redirects to login) |
As seen in janeczku/calibre-web#1891 (comment), for reverse proxies, Kobo needs larger buffers than Swizzin's default.
Kobo Sync doesn't work unless the proxy buffer sizes are increased. The values/fix were pulled from here: janeczku/calibre-web#1891 (comment)
Environment:
books.mydomain
to port 8083 of the containerDescribe the bug/problem
The sync between calibre-web and Kobo doesn't always work.
I have run a couple of tests to try to find the problem and I think it has something to do with the reverse proxy.
In fact, I was only able to sync correctly when I used the server's IP directly as the endpoint.
It is possible that the error can be traced back to some configuration error in the proxy server. But for viewing the web app there is no problem, and this user seems to have a similar problem to mine.
I preferred to open a new issue because the OP of the other issue did not use a reverse proxy and had problems all the time, in my case if I use the ip the sync works.
Below are the conditions under which I performed the tests and the calibre logs.
Note: In all tests, NPM was set to force SSL and block exploitation. I have performed further tests, not reported, and it seems that these configurations are not relevant.
Test 1
books.<domain>/<token>
Sync result: ERROR
Test 2
books.<domain>/<token>
Sync result: OK
Test 3
books.<domain>/<token>
Sync result: ERROR
Test 4
books.<domain>/<token>
Sync result: ERROR
Test 5
<ip>:8083/<token>
Sync result: OK
The text was updated successfully, but these errors were encountered: