#Reverse proxy and WG

2 messages · Page 1 of 1 (latest)

stoic ruin
#

Hi there,
I used to have NGINX installed on a RPi and acting as a reverse proxy to get to my Overseerr instance, but I recently spun up a VPN at Oracle and deployed NGINX over there, and connects back to my internal LAN through a Wireguard VPN. So my domain name points to Oracle, which then hits NGINX, and redirects the traffic to Overseerr through the WG pipe. For some unknown reasons, I am unable to get to the login page and cannot figure out what is causing this to happen. I have been struggling for the last 3 days with no luck, so I am wondering if someone had a similar experience with this kind of setup. I have searched through the existing posts, but was unable to find a similar environment.
When I try to access Overseerr, I can see that it hits Overseerr cause it tries to redirect my client to https://****/login, but then it hangs for a bit and then it throws an error 504 Gateway Time-out. I don't think it is a issue with Overseerr, and more an issue on the network side of thing, but I am curious to see if someone encountered a similar issue here, and how it got resolved?

stoic ruin
#

Alright, so after a lot of investigation, analysis and testing, I finally found the root cause of the issue... For anyone that are interested to know what was causing the issue to occur, it was the MTU setting on the Wireguard interface. By default, it is set to 1500, however, I have found in the documentation that it should be set to 1420. As soon as I changed the value of that guy, it actually worked! 🍺