If Shiori is behind a reverse proxy (patch with --webroot option), the extension doesn't connect anywhere but the root of the URL.

[lawrencecandilas]

This commit fixes by making the new URL calls append the API path to the server URL config string instead of using 2 parameters to the URL() function.

[efrecon]

I proposed a fix through #32

[l0b0]

Has this been fixed by #32? If so, how do I actually use it? I tried using the base URL "https://[omitted]/shiori/" in the "Server" field in the configuration, but it must be talking to the wrong URL, because I get a HTTP 404 from the server.

[efrecon]

I just checked what I have: I start shiori with -r /shiori and have a reverse proxy in front. In the webextension, I have what you have. I am running caddy as the reverse proxy, if that helps in anyway.

(I suppose you are self-hosting this).

[l0b0]

Oh, maybe my trailing slash (--webroot /shiori/) is breaking things? The web interface works fine though.

[fmartingr]

Hey @l0b0, are you using the latest release or the latest master?