Access your Jellyfin anywhere with Caddy

[OsulivanAB]

Appreciate the help! After following your advice, I successfully set up remote access to my server using a Duck DNS domain. Post-setup, I noticed a drastic drop in my home network's performance, even when the server wasn't in use, and there was no unusual activity logged on the Jellyfin logs.
I'm very new to networking, but I suspect the issue might be related to misrouted traffic via Caddy? I'm not sure Here's my setup:
- An old laptop runs Proxmox, hosting a TrueNas VM for storing movies and running Jellyfin in a jail.
- Caddy is configured in a separate jail for web access.
- Port forwarding is set to the Caddy IP for ports 80 and 443.
- Configured Caddy with:

Code:

caddy reverse-proxy --from <mydomain>.duckdns.org --to 192.168.<jellyfin>:8096

- Configured Caddyfile:

Code:

<mydomain>.duckdns.org
reverse proxy <internal ip>:8096

Despite the guide suggesting the use of a public IP, I opted for an internal IP since the domain already points to my public IP. This setup worked, enabling remote server access. But if I still should have used the public IP let me know.
The following day, my internet speed plummeted from around 700mbps to 60mbps. My Raspberry Pi which monitors the internet speeds periodically throughout the day noted this decline coincided with the setup completion.
Given no active server use was logged, I'm puzzled by the significant impact on my network's outgoing internet quality. Could simple port forwarding be the culprit?
I'm not sure why forwarding incoming web server ports would impact my other devices so bad.