SOLVED: Accessing the web server

[ArbitraryRenaissance]

Code:

(# ufw status verbose)
Status: active
Logging: on (low)
Default: deny (incoming), allow (outgoing), disabled (routed)
New profiles: skip

To                        Action      From
--                        ------      ----
22/tcp                    ALLOW IN    Anywhere
8096                      ALLOW IN    Anywhere
22/tcp (v6)                ALLOW IN    Anywhere (v6)
8096 (v6)                  ALLOW IN    Anywhere (v6)

If my network topology is more complex than a typical user's network, it's not by intention.  As I said in my initial post, I have a road warrior setup through wireguard, which I built using the OPNsense documentation as a guide.  Here's the link, which will spell out the interfaces and firewall rules that I would have on my system associated with this: https://docs.opnsense.org/manual/how-tos...lient.html

In addition to this, I've installed a gateway to Mullvad's VPN servers, which I built using a guide spelled out on the OPNsense forums: https://forum.opnsense.org/index.php?topic=38550.0

In order to get SSH working, I had to introduce one extra rule to force local traffic to bypass this gateway.  I'll include a picture of the table that includes the floating rules in my firewall.  "Moles" is an alias of devices (identified with the wg0 interface) for which WAN traffic is meant to be tunneled through Mullvad first.  This at the moment includes my NAS (which holds the Jellyfin server) and my main computer (which is trying to access it).  HomeVPN is the more descriptive name for wg0.