ljm42

I'm confused about that first screenshot, did you actually see that or did you grab it from another post somewhere?

This is correct. The certificate_bundle.pem cert is ONLY valid for *.myunraid.net urls. There is zero benefit to using it with other urls. If you access the server by IP address or by name then it will use a self-signed cert. It is fully setup. To use it, click the url starting with https://192-168... that you blanked out of the screenshot. For more information, see https://docs.unraid.net/unraid-os/manual/security/secure-webgui-ssl/

Keep playing with this, it should do what you want. The only other option is to change the IP in the client config but as you said it is not exactly secure. If you can't get it to work, try hosting VPN on your Unifi device instead.

Give IETF a try

This is not normal. Do you have the WG Docker container enabled at the same time? Maybe there is some sort of conflict. I'd suggest stopping the Docker container and following the guide here to set up the built in one: https://forums.unraid.net/topic/84226-wireguard-quickstart/ Get "Remote access to LAN" working before trying something else. Read the entirety of the first two posts in that thread, there are many helpful tips that may point out an issue in your network.

Are you changing SSL settings? The only cause I know of for what you are describing happens when you disable SSL, it can confuse your browser. To help prevent confusion, the webgui shows this message: If you are sure that is not the cause, go to Settings > Syslog Server and temporarily enable "Mirror syslog to flash". The next time it happens: 1) clear your browser's cache to see if that helps 2) if not, reboot the server and upload your diagnostics (from Tools -> Diagnostics) here Note: once you past this issue be sure to disable "Mirror syslog to flash" as it adds wear and tear to the flash drive

Think of Unraid as an appliance, not a general purpose operating system. If you need a place to perform "daily business" the recommendation would be to run a different OS in a VM.

Manual upgrade instructions are in the docs: https://docs.unraid.net/unraid-os/manual/upgrade-instructions/#manual-upgrade-or-downgrade It sounds like you might have skipped this step: Move (not copy) bz* and changes.txt from the root of the flash drive to the "previous" directory, overwriting files as needed If so, when you replaced the files in the root of the flash you overwrote the running OS. There is no graceful recovery for this. Your best bet would be to turn the system off, put the flash drive in a different computer, and follow those manual instructions from the top

Unraid 6.12.8 does not have proper support for Lifetime keys. Please upgrade to Unraid 6.12.10

Yes, this release is intended to resolve the issue with your drive controller: https://forums.unraid.net/topic/160471-unraid-os-version-61210-available/

Yes the update process isn't really setup for people to run in "pending restart" mode for an extended period. TBH this could confuse plugins and other things that aren't prepared for this as well, I would not recommend updating the OS until you are ready to restart. 6.12.9 does have an issue with certain Asmedia controllers, if you are at all concerned about that you can go to Settings -> Disk Settings and disable array autostart. Then when it boots into 6.12.9 there will be no problems and you can just run the update to 6.12.10 and reboot into that.

Glad to hear it! Kudos to @Kilrah

This is suspect. Try manually stopping the container (reload the page and be sure it is really stopped) before doing the update and see if it makes a difference. Otherwise, I agree with the suggestion to recreate the docker image

Unraid 6.12.10 is now available:

Thanks, we got the feedback we needed and have published 6.12.10: