Adiventure

The struggle is it's http://192.168.30.138 that's not working and is popping up that nginx 404 error. The struggle is it's http://192.168.30.138 that's not working and is popping up that nginx 404 error. Sorry for the lack of clarity, I should have, and thought I did, specify that I was trying the IP. Attempting to connect via VPN to my router http://tower.local gives a nxdomain. Router is a Unifi UDMP, DNS is being done locally by a PiHole w/ unbound.

I have no idea what has prompted this because I don't believe I've changed any settings since it last worked (approximately a week or two ago). I am able to connect with at least one machine which is hardwired, however multiple wireless devices, as well as remote devices using a vpn are unable to connect past a nginx 404. The hardwired device, connecting in the exact same manner is working fine. I do have SWAG running, but it shouldn't be catching the webui. tower-diagnostics-20230217-1228.zip

Struggling a bit with setup and hoping someone might be able to help. I'm pretty new to Plex, having used Emby for a long time, and picking up a license on sale. I've had Emby set-up with SWAG for a while, and figured I'd try setting up Plex that way as well. It's working insofar as my url is hitting Plex and I'm able to login to my user, but I'm not able to actually setup the server at all. If I go to webui I get about:blank#blocked in the address bar. I'm not quite sure what to make of that, clearly the swag side is working, but something is presumably wrong in my Plex setup. Plex is running on my swag network. No other settings have been fudged with. I do note that Plex isn't showing any port mappings on the docker page, I'm not sure if that's right or not.

Yeah, I was able to set it up in between my last message and yours, and just a minute ago solved the only other issue which was one interface showing as FE and not GBE. In all it's easy, but you're right either the interface could be changed or at least have some tooltips added, or the documentation could go into more detail.

Great. To make sure I'm understanding correctly, as long as the settings are configured correctly on ethos the settings for eth1 don't particularly matter? I don't need to select bonding on it as well? What about a semi unrelated setting, such as enable vlans? Does that not need to be the same between both interfaces?

I'm afraid to say I'm a bit confused as to what a proper config looks like. Presumably I need to enable bonding and selecting 802.3ad for eth0. From that point is where it gets hazier. Do I need to mirror the config for eth0 with eth1? That seems impossible at the moment, though that may be due to eth1 having no cable connected, as the only bonding option on the dropdown is itself. What about the rest of the details? Does configuring them on eth0 carry over to eth1? Is this right: