2023-08-03, 07:28 PM
(This post was last modified: 2023-08-03, 07:31 PM by St. Glocktopus. Edited 2 times in total.)
I saw those too and that's what lead me down the NAT loopback rabbit-hole.
The Tp-Link router is not supported by any 3rd party firmware, I also looked into that and was sorely disappointed. I do have a Sonicwall TZ-240 hardware firewall sitting around that I've been considering implementing to replace the Tp-Link as primary but that would break my DDNS and domain forcing me to recreate the whole setup I think.
All my devices are connected via the DDNS address, I cannot connect to it using the local IP address and port 8096 as I get an error with failure to connect or in a browser it just fails to load and says the site does not exist or is not available.
I can post my apache config file for my 000-default-le later today as I was a dummy and configured both Ombi and Jellyfin to run in the same config file.
The Tp-Link router is not supported by any 3rd party firmware, I also looked into that and was sorely disappointed. I do have a Sonicwall TZ-240 hardware firewall sitting around that I've been considering implementing to replace the Tp-Link as primary but that would break my DDNS and domain forcing me to recreate the whole setup I think.
All my devices are connected via the DDNS address, I cannot connect to it using the local IP address and port 8096 as I get an error with failure to connect or in a browser it just fails to load and says the site does not exist or is not available.
I can post my apache config file for my 000-default-le later today as I was a dummy and configured both Ombi and Jellyfin to run in the same config file.