I Assigned My NIC to a Container--Can't Log In Now

Apps and Virtualization
,
1

I made a mistake, but didn’t know it at the time.

  1. I brought up a container running Debian Trixie on TrueNAS SCALE 25.04.2.4.
  2. Installed docker and Nextcloud-AIO.
  3. Could not access the internet at the given ip, 10.163.x.x
  4. (here is the stupid part) I attached the main NIC to the container. I thought this would be a bridge to my home network. For 5 minutes I thought it was a bridge. I could access TrueNAS and I could access Nextcloud.
  5. But now all app ports are accessible thought the NIC, and the http/https ports won’t take me into my system. This is strange to me because Nextcloud is using ports 8080 and 11000 only.
  6. I get the initial loading screen, but instead of the username/password screen I get only a warning, “Connecting to TrueNAS … Make sure the TrueNAS system is powered on and connected to the network,” so it seems that ports 80 and 443 are available, but are not connectiong to the TrueNAS UI.

So that’s the pickle I’m in. I have no idea how to get into the UI and unconnect that NIC from the container. Any ideas?

Bruce

2

Slight correction to the above: I can use the Nextcloud admin UI on port 8080, but the main UI on port 11000 only partially loads: the backdrop image and one sentence: " Nextcloud– a safe home for all your data." It feels like it’s mocking me.