bandwidth-hero doesn't catch urls when using my own instance
rakoo opened this issue · comments
First off, thanks for the extension I was looking for something like Chrome data saver but didn't want all my data to go to Google, and thanks to being an actual extension I can see how much data is actually saved while browsing.
I have tried to self-host the backend (I'm using https://github.com/PrairieOps/bandwidth-hero-core/ because https://github.com/ayastreb/bandwidth-hero-proxy doesn't build for some reason). So:
- When I put the backend on localhost, it works
- When I put the backend on my domain, it doesn't work (http)
- When I put the backend on my domain, behind a reverse proxy (https), it doesn't work
- When I use the backend graciously provided in #19, it works
By "it doesn't work" I mean that the extension doesn't even send the url to the backend: I don't see any trace of requesting it in the Network tab (when the backend url is set I don't have the message telling me that the url is invalid, so I assume the extension got it right).
I don't know if the url is captured or something else... I just don't see how setting the backend url can have an impact on whether the backend will be called or not
My solution for now: have a reverse proxy locally that will call the reverse proxy on my domain that will call the backend... I'd love to simplify my installation :)
My domain is https://bh.rako.space. I don't know if it fails for everyone or just me.
Hi,
From what I can see when I try accessing bh.rako.space, there's a 301 forcing it to https, and then there's a 502 Bad Gateway error. I'd double check your reverse proxy and web server configuration, if I were you also make sure the nodejs process for this is running and hosted on the expected port. Since it should read "bandwidth-hero-proxy" when you try to access the url without sending any url parameters.
I'm actually more concerned about the upstream version not building for you.
What error do you get when building and what version of NodeJS are you using?