ljm42

Please go to Settings -> Fix Common Problems and set "Log Ignored Errors/Warnings?" to "yes" so we can see what else it is warning about, then press Rescan and gather fresh diagnostics Then reboot into safe mode (this disables all plugins), run for a while and see if the problem persists. Take fresh diagnostics from here as well so we can compare.

Right, all the fancy bonding options require the NICs to be connected to a network switch that is configured with the same settings. it sounds like something is trying to send mail but mail isn't configured. You can do that at Settings -> Notification Settings -> SMTP Settings

singularity098 appears to have a newer version, but everything I said above still applies. Modifying Unraid like this is strongly discouraged.

So it looks like you followed a guide somewhere and added 27 lines of code to the config/go script on your flash drive. This code modifies two core Unraid fails: /etc/rc.d/rc.docker /usr/local/emhttp/plugins/dynamix/scripts/monitor I strongly recommend removing all that and restoring your go script to stock: #!/bin/bash # Start the Management Utility /usr/local/sbin/emhttp & then rebooting. This will get you back into a supported configuration. If you are unwilling to return to stock Unraid, you should find where you originally got the code and see if there is an updated version. Keep in mind that with every Unraid update there is a chance this code will break so you should bookmark the source and check it regularly for updates. Modifying core Unraid files like this is highly discouraged, always be sure to upload your diagnostics when asking questions so the people helping you know up front about the mod. Any support questions about the mod or the files it modifies should be asked in the thread where you got the mod.

Navigate to Settings -> Network Settings and change your bond type to "active backup", see if that makes the errors go away. I'd recommend reviewing the warnings from Fix Common Problems, it has probably been warning about this but the specifics are not being logged: root: Fix Common Problems: Ignored errors / warnings / other comments found, but not logged per user settings There is more info about complex bonds here: https://forums.unraid.net/topic/120220-fix-common-problems-more-information/page/2/#comment-1100015

To be safe, make a backup of your flash drive first. Main -> Boot -> Flash -> Flash Device Settings -> Flash Backup The files are stored on the flash drive in the config/wireguard directory. Delete everything in that directory (but leave the directory itself) to start over with WireGuard. To do this from the web terminal type: rm -r /boot/config/wireguard/* ( Be extremely careful typing that command! A space in the wrong place will wreak havoc. )

The code being discussed in this thread is not stock Unraid. Something has completely overwritten this file: /usr/local/emhttp/plugins/dynamix/scripts/monitor. I'm guessing that you added code to your /boot/config/go script but without diagnostics it is hard to tell. Please upload your diagnostics.zip (from Tools -> Diagnostics)

This is not stock Unraid code, but was due to a modification you added to your go script right? Please make that clear when requesting help, and upload your diagnostics so people can see the code you added to your go script. Overall though, I'd recommend discussing this in the thread where you got the code, perhaps there has been an update. Or you can delete all the mods to the go script and return to stock Unraid.

Big thanks to Github user baumerdev, they submitted a PR ( https://github.com/unraid/webgui/pull/1717 ) that will likely solve the problem mentioned in this thread In the meantime, if you get a 500 error when signing in you can do the following: Sign in from a different IP address, to bypass a bug in the bad password rate limiter -Or- SSH in to the server (or use the server's console) and type: rm /var/log/pwfail/*

Hey @EldonMcGuinness, got another one for you I am seeing this PHP warning show up in my log: [07-May-2024 17:15:01 America/Phoenix] PHP Warning: Undefined array key "type" in /usr/local/emhttp/plugins/DriveStandbyMonitor/includes/page.php on line 47 Even though it is just a warning, we try to clean these sorts of things up. To see these warnings, go to Tools -> PHP Settings and enable "All Categories". Then press View Log. As you interact with the server you will see any PHP errors or warning in the log.

@EldonMcGuinness please add this file to the plugin to stop Unraid Connect from backing up monitor.db every 15 minutes: echo "monitor.db" > /boot/config/plugins/DriveStandbyMonitor/.gitignore Here is an example of how the rclone plugin distributes a similar file: https://github.com/Waseh/rclone-unraid/blob/6ed5f0ecf8cf1077795ecf7831aa84fd54408096/plugin/rclone.plg#L241 Note: initially this will only take effect on new plugin installs. The next release of the Connect plugin will make sure existing systems obey that .gitignore file too, without anyone having to do anything at the command line. This does mean that Unraid Connect Flash Backup will stop backing up this file. If you think it should be backed up occasionally, you could have the plugin copy it to a new file name perhaps once a day or once every few days. The main goal here is to avoid the write amplifications that flash backup causes when this file changes every 15 minutes.

Flash backup runs whenever it detects a change on the flash drive, so something is updating a file on your flash drive every 15 minutes. To see what it is, open a web terminal and type: cd /boot then git log --stat You can up/down arrow through the list, press Q to quit You will probably see the same file being mentioned multiple times, please copy/paste what you see back here.

This is the problem, DNS Rebind Protection needs to be disabled. Diagnostics shows that DNS requests for 192-168-4-100.hash.myunraid.net do not resolve. It needs to resolve to 192.168.4.100 in order for the url to work. Isn't there a message about this on the Settings -> Management Access page?

Please right click on the https://ip.hash.unraid.net one and choose "open in a new tab". Please show a screenshot of what happens. A screenshot of this would be helpful too

Something must be wrong with your bookmark, maybe the server's IP address changed? Access the webgui through Connect and go to the Settings -> Management Access page. That will list all of the available local access urls, including the ip.hash.myunraid.net one. When you use the url listed there you should be able to access the server. I need more detail about what you are doing. Based on the settings you provided, your webgui is hosted on port 443 not 4200. Are you maybe trying to do something with a Docker container? Also please provide the full diagnostics.zip (from Tools -> Diagnostics)

This thread is perfect for quick questions or comments, but if you suspect there will be back and forth for your specific issue, please start a new topic. Be sure to include your diagnostics.zip.

When the problem is occurring, please SSH in and run: /etc/rc.d/rc.nginx restart What is the response, and does it help? Also please run: cat /var/log/nginx/error.log and copy/paste the results back here. There is a lot of noise in this file but maybe something useful.

Please start a new thread in General Support, include as much detail as you can along with your diagnistics.zip (can get from SSH by typing "diagnostics", any questions go ahead and ask in your new thread to avoid a lot of back and forth in this announce post)

This thread is perfect for quick questions or comments, but if you suspect there will be back and forth for your specific issue, please start a new topic. Be sure to include your diagnostics.zip.

When you are ready to try again, be sure to grab your diagnostics.zip (from Tools -> Diagnostics) while in the new version. Then start a new thread under General Support, describe the issue and upload the diagnostics.

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.