New containers refuse allow connections

[vitaprimo]

I've been trying to access containers but pretty much anything I install is unavailable.

 

I've tried setting the network as bridge and also have tried giving them their own IP address but no matter the method I get the same result in all browsers:

 

The containers already deployed continue to work and continue to connect to the Internet to do their stuff where applies. All can be updated.

 

Furthermore, unRAID cannot join the AD domain anymore. Just today I joined a computer to it and it worked just fine. It pulled everything from the domain as it had. I SSHed in to unRAID to try to diagnose using the few little commands I know but I couldn't do DNS queries from unRAID because it seems not to have the tools installed so I went for second best and I pinged the domain controllers--it went fine too:

For the moment SMB doesn't work because of the domain thing. I'm only using unRAID for the easy Docker deployment and the containers I need the most are working fine so I'm not too concerned about it, but, not being able to deploy more containers --or deploy them but not being able to access them I should say-- and not being able to use SMB, the most universally accepted protocol, sort of negates the need for unRAID.

 

How can I regain access to containers (or rejoin the domain)?

 

Thanks !

Edited December 5, 2019 by vitaprimo

[jonp]

Hi there,

 

Please upload your system diagnostics.  These can be obtained from the Tools > Diagnostics page.

 

All the best,

 

Jon

[vitaprimo]

Thanks for answering,

 

I had forgotten where this was. I did take a look and didn't catch anything obvious though.

 

What I do see when I try to join the domain is that it apparently succeeds:

Every time the same three messages appear. I believe the sshd in red, it is that it kills the SSH server to update its settings for domain users, I'm not sure how to set it up to test though. I'm using it as confirmation that something did happen.

 

Lastly, I just updated to 6.8.0 and disabled NetBIOS straight away but it didn't help. These last two screenshots are on 6.8.0.

 

Thanks once more.

hyperserver4-diagnostics-20191210-1756.zip

[vitaprimo]

Nothing seemed to work except wiping out the server and starting over. Strangely data on the array was not lost, not only that, it couldn't be made lost (erased) even after using the New Config feature in the Tools area.

 

I needed to wipe the disks because I wanted container settings gone but SSHing in and deleting the appropriate directories (/mnt/user/appdata/* then the parent /mnt/user/appdata) did the trick.