Somewhere between my instance and the VPS, I’m running into 502 errors on occasion, with seemingly increasing occurrence.

Seeing as my VPS has been flakier over the last year in general, I’m leaning towards that.

Maybe I’ll find a use for my second WAN IP after all - cut out the VPS completely.

Now I need to figure out how to get a virtual interface on my OpnSense box running over a VLAN so that my router gets that second WAN IP…

Maybe a virtual interface on the physical connection I’m using for WAN, but with a different MAC? Is that a thing?

I know how to do the above on a Sophos box, but OpnSense works so differently that I can’t quite figure it out. I need to read more documentation, I think.

@maddy One possibility could be the VPS server itself (or the switch). I've had Linode "emergency move" my instances to different physical machines when they detected an excessively high number of errors. If you can force a re-allocation/re-deployment of your VPS (by say changing its specs), that might be a way to quickly resolve it. Otherwise definitely poke your host as it may be them.

@maddy why do you need another MAC address (or indeed even another interface) to get the second WAN IP?

I don't know how your ISP does things and it's probably different but mine gives me a single WAN IPv4 address that is assigned to the PPPoE WAN interface on my router and then routes my subnet to it without me having to assign any of the other IPs to the WAN interface. (and similarly for IPv6 except prefixes can be assigned using either DHCPv6-PD or statically)

@maddy Is this why I keep getting “Connection Lost” errors? I has been getting worse lately. It was near constant yesterday.

@kiki Could very well be. I know it’s not the connection where the server lives, so I think it’s the VPS. I am actively looking into a solution. 💜