Can't access vaultwarden through working reverse proxy

[SamKook]

Let me first say I'm aware it needs https to be accessed outside of localhost, but I'm at a bit of a loss and would appreciate some help to find ways to diagnose the issue.

I can access vaultwarden fine on the local machine(running in a freebsd proxmox VM, installed from the package from pkg) with either localhost or 127.0.0.1 on http.
I can't access vaultwarden using the local ip(192.168.1.x) on the local machine on http, I get the browser unable to connect error.
I can access the nginx test page fine using the local ip on both the local machine and another pc on my local network.
I can't access vaultwarden with my caddy reverse proxy setup on my opnsense router(I have 13 other working local services I can access fine with it and I even tried modifying the ip and port on a working one to make sure it wasn't me messing up setting the one for vaultwarden) on https using my sub-domain for it(it had plenty of time to propagate and I tested on an already set up one too). I tested this from both my local network and from a separate network, even though I knew can access other service fine with my external ip on my local machines.
And I can access the nginx test page from that same VM through the reverse proxy just fine on https.

With all this testing, I don't really know where the issue would be. I would expect vaultwarden to throw a different error when accessing it from an unsecure connection, like how nextcloud does it, but if even the local machine gets a generic error, I assume that's either normal or there's a configuration I missed.

Any idea what the issue could be? I can access vaultwarden locally, I can access websites from the VM ip and my reverse proxy is working and using https so...

[SamKook]

Welp, as these things go, when you ask for help after hours of trying to figure out a problem, you immediately figure out the solution...

I just had to change the ROCKET_ADDRESS env var to the local ip instead of 127.0.0.1