ljm42

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)

Thanks for this. I dislike that we are sending raw HTML here but was having trouble coming up with a concrete reason why we shouldn't do it. This helps. Overall it is going to be low on the priority list, but it is something I would like to see changed.

Many improvements have been made to Docker since the original report. If you are still having the issue in Unraid 6.12.10, please post diagnostics and updated screenshots / details.

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?