-
Notifications
You must be signed in to change notification settings - Fork 98
[Feature Request] Proxy Support #30
Comments
Also having an issue with this, using a basic nginx proxy config with:
However as there's no option to set the baseurl in requestrr, it's trying to serve all JS on I've looked at a few options of setting the baseurl in |
Use sub domains. Proxy's to a "sub folder" cause so many problems, just add a subdomain. |
@ChaseHall unfortunately that's not an option with my setup |
This bug has been fixed in v1.0.14, you can now configure a base url with https for Requestrr. |
running v1.0.14. its not fixed.
Do you have "Configure for HTTPS" checked in project settings? forgot to mention. Web GUI loads. But auth doesnt work 🤔 |
Requestrr itself doesnt support HTTPS, however it now supports being behind an HTTPS reverse proxy. The proxy would handle the HTTPS, not Requestrr directly. |
Install requestrr for linux, as described in the wiki. Start the service to generate a sample config nginx config (swizzin tested): location /requestrr {
proxy_pass http://127.0.0.1:4545/requestrr;
proxy_set_header Host $proxy_host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_redirect off;
}
|
I run a bunch of services on a single VM and exposed them on 443 with nginx. Requestrr fails with this message:
warn: Microsoft.AspNetCore.HttpsPolicy.HttpsRedirectionMiddleware[3] Failed to determine the https port for redirect.
Google indicates that the app server needs to be coded to support proxied traffic.
The text was updated successfully, but these errors were encountered: