SOLVED: "Startup probe failed" failed after updating TrueNAS & Jellyfin

[jymotion]

I was running Jellyfin on TrueNAS Scale as recently as this morning without issue. I saw today that both had updates available (they were both only 1 release behind or so), so I updated TrueNAS Scale, then Jellyfin. Now when I try to start Jellyfin back up again, it gets stuck in DEPLOYING with the following events:

Code:

2023-10-14 17:13:24
Startup probe failed: Get "http://172.16.0.63:8096/health": dial tcp 172.16.0.63:8096: connect: connection refused
2023-10-14 17:13:14
Started container jellyfin
2023-10-14 17:13:13
Created container jellyfin
2023-10-14 17:13:12
Container image "jellyfin/jellyfin:10.8.11" already present on machine
2023-10-14 17:13:11
Created container jellyfin-init-01-permissions
2023-10-14 17:13:11
Started container jellyfin-init-01-permissions
2023-10-14 17:13:10
Add eth0 [172.16.0.63/16] from ix-net
2023-10-14 17:13:10
Container image "bash:4.4.23" already present on machine
2023-10-14 17:13:09
Scaled up replica set jellyfin-844545c6b5 to 1
2023-10-14 17:13:09
Created pod: jellyfin-844545c6b5-nqfxw
2023-10-14 17:13:09
Successfully assigned ix-jellyfin/jellyfin-844545c6b5-nqfxw to ix-truenas

I don't recognize the IP address it's trying to reach. When I watch content, I'm connecting at http://192.168.0.86:30013, but maybe that's irrelevant. When I look at my Kubernetes Settings, I see:

Code:

Cluster CIDR: 172.16.0.0/16
Service CIDR: 172.17.0.0/16
Cluster DNS IP: 172.17.0.10

I'm not familiar with what this is, but it seems similar to what is listed in the Events log. Sorry if this is a stupid issue. Would appreciate any help.