You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As it stands if I'm hosting multiple things on the same reverse proxy the booksonic server ends up dropping my url base I entered for the proxy and not connecting properly.
I believe this used to work on the "Legacy" Booksonic server
Is this the same problem as #28 and #33 ? If so, I hope we can do
something, it disables access to the settings and to the home page for
people using subdomains with a reverse proxy (which really shouldn't be a
rare configuration).
On Sun, Jun 13, 2021 at 10:13 PM Kickbut101 ***@***.***> wrote:
As it stands if I'm hosting multiple things on the same reverse proxy the
booksonic server ends up dropping my url base I entered for the proxy and
not connecting properly.
I believe this used to work on the "Legacy" Booksonic server
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#42>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJ7H6KDLZSLS4TJP46MJWDTSWFYFANCNFSM46UPPJYA>
.
Check out the last comment in issue #33, it solved the problem for me with a single line added to a single configuration file (although, fair warning, that configuration file contains a warning that it's automatically generated and not to modify it, so it's probably not the right solution but since it worked instantly I used it).
As it stands if I'm hosting multiple things on the same reverse proxy the booksonic server ends up dropping my url base I entered for the proxy and not connecting properly.
I believe this used to work on the "Legacy" Booksonic server
Current usage if I visit https://myaddress.com/booksonic the connection just drops the /booksonic and it doesn't connect
Ideally we'd want the server to respond to https://myaddress.com/booksonic and persist that appended /booksonic
The text was updated successfully, but these errors were encountered: