search

aunefyren / wrapperr

Website based application that summarizes Plex statistics from a given period and displays it in a nice format. Similar to the Spotify Wrapped concept.
315 stars 22 forks source link

Working behind haproxy #52

Closed secrdrew closed 11 months ago

secrdrew commented 1 year ago

I want to make wrapperr available to my users. I have set everything up in haproxy. However, when I try to browse to my URL I get a 503 Service unavailable error.

I am wondering if I am missing something that is preventing me from getting it working. I have multiple other services available via HAproxy.

Thanks for your help.

aunefyren commented 1 year ago

Hey, good question. I think I need a few more details to diagnose this issue.

secrdrew commented 1 year ago
secrdrew commented 1 year ago

Here is my config.

https://pastebin.com/bTc9UJZn

aunefyren commented 1 year ago
  • I am sharing it with subfolder/url base. stats.mydomain.com

So you are using a subfolder/url base as well as the stats subdomain? The latest release is quite strict and requires a trailing slash in the URL.

Like this stats.mydomain.com/mycoolbase/.

secrdrew commented 1 year ago

Sorry no. I am just using the subdomain. So it is just stats.mydomain.com.

On Sat, Dec 10, 2022, 6:01 AM Aune @.***> wrote:

  • I am sharing it with subfolder/url base. stats.mydomain.com

So you are using a subfolder/url base as well as the stats subdomain? The latest release is quite strict and requires a trailing slash in the URL.

Like this stats.mydomain.com/mycoolbase/.

— Reply to this email directly, view it on GitHub https://github.com/aunefyren/wrapperr/issues/52#issuecomment-1345260203, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE7GHXTDNNX5FOZNSBH5TKTWMR5LNANCNFSM6AAAAAASY6WJR4 . You are receiving this because you authored the thread.Message ID: @.***>

aunefyren commented 1 year ago

Mmm, I am sorry but I am not sure why you are having trouble using HaProxy. I haven't used it myself and everything seems to be correct. If the proxy can reach Wrapperr on 10.20.50.16:8282 then it should work.

mrjohnpoz commented 1 year ago

I just set this up for my users, and I am behind haproxy running on pfsense - had zero issues setting it up. Clicky clicky and up and running.

I just setup a frontend on my public IP on port 44301 (added firewall rule to allow that port), using a acme cert I setup using ssl offload, and the backend sends it to my nas that is running the docker to the nas IP 192.168.9.10 on port 8282

You mention a 503 error - I do recall seeing that either on ombi or my current setup for overseerr - pretty sure the fix for that was to not use a backend check. From your config looks like you have that disabled, but you are using shared frontend - I don't like doing that, not using a wildcard cert and not sure how do strict-sni on a shared frontend with different certs, etc. I like to use strict sni because if someone just hits the IP and port I don't want them getting anywhere, and don't like the CN from the cert being returned either, etc. So if you are not using the correct CN to hit my IP your not going anywhere, and your not getting any info back on what the right fqdn would be either...

aunefyren commented 11 months ago

I am closing this issue due to inactivity. If the issue persists, feel free to re-open it or create a new one.