spalmisano

The IP of the Unraid machine is 10.10.0.2. Since I’ve got it configured at port 81, the UI has always been at 10.10.0.2:81/Main There’s only the one subnet for the main network, and yes all the other machines are on that subnet. There’s a guest network that’s isolated and rightfully cannot access the Unraid UI. The server itself does have a KVM attached but I’ve only ever seen a command prompt after booting. I’ve only been able to access the UI remotely. I admit to not having paid attention to the boot options recently. Is there an option to have the UI enabled on the server?

Correct. All browsers report connection failed.

Tech debt from setting up Unraid years ago. Port 80 is being used by a Docker container and I’ve been using 81 ever since. Is there something in the diagnostics showing 81 now not having a correct configuration? It’s worked perfectly since.

Diagnostics taken via CLI at 21:04 EST. Thanks again. media-diagnostics-20220120-2103.zip

I recently started seeing “Invalid Certificate 1” errors in my Fix Common Problems output on array stop/start. I usually only stop to add or update drives, with hasn’t been all that often so I’m not certain when this began. I found several posts about how to address this in Management Access, and was able to add my *****.unraid.net address to Pihole/Unbound and address the certificate error. Today we lost power long enough for the UPS to shut down the whole system, and once it came back up I can no longer access the Unraid UI. The system is up, Docker containers are running, VMs are running, nothing else is using port 81, I can access drives, connect via SSH…everything you would expect the system to do, save for getting access to the UI. I’m at a loss about where to troubleshoot. With only having made that one change to the system recently, is addressing the SSL error a red herring and I should look elsewhere, or is there more to registering my *****.unraid.net address? Let me know what other diagnostic information would be helpful and I’ll update it here.

I have OpenVPN working properly on my Unraid box, and can connect to it via the laptop with my configured user, so Im confident things are correct server side. What I can't do is get the OpenVPN connect page to render on my iPhone. Ive downloaded the OpenVPN client and attempted to import my profile, but the resulting page never fully renders. Trying both in Safari and Chrome all I get is the OpenVPN logo and the rest of the page is blank. There's nothing in the logs server side, and Im not sure where to turn for anything more diagnostic. With the page not rendering I can't get my client.opvn file into the OpenVPN iOS app. Is there another way to do this? What am I missing?

This appears to be working. I am able to connect/authenticate with the non-admin user after a container restart. Im guessing that user account got out of sync with the database while I was tweaking it via the command line. Thanks for the help.

You mean the 'Authenticate users with' on the Active Configuration should be 'local'? That's what I have and still am experiencing the above. The user account I use to log in with shows up in the UI, but I still need to use the command line to re-add that user and set its password.

Yes, saw that. What I'm not clear on is why I have to update the users password every time the container gets updated and restarted.

I'm not. The user was added via the UI, and is still in the UI on container restart, but I still need to add the user via the command line in order to set its password. The authentication is is set to local, not PAM.

unRaid 6.3.5 and linuxserver.io's openvpn-as Docker container. Ive not read through this whole thread, so if the answer exists here already, please shove me in that direction. This was originally posted at Reddit, with no resolution so far. I followed Spaceinvader One’s video for setting up OpenVPN as a Docker container and was able to get everything set up correctly, save for one issue. Any time there’s an update to the container, the user I've created to access the VPN, not admin, is deleted. I can manually create the user via the command line, but should I have to? Why would updating/restarting the container cause the user to get removed? The user does show up in the UI, but I can’t connect using its credentials. When I do docker exec –it openvpn-as adduser username after restarting the container, I can connect again. What am I missing?