frakman1

Thank you. I tried that solution but that wasn't satisfactory either. It was still using the new Unraid certificate. Uninstalling the plugin should really remove everything that it added.

For those suffering from the recent error: Error: ER_WRONG_NAME_FOR_INDEX: Incorrect index name 'migrations_lock_lock_key_unique' I was able to recover by droping the two tables migrations and migrations_lock tables as mentioned in the ghost user forum I used the adminer docker that lets you do it easily via a web UI.

I decided to uninstall this plugin. However, now anytime I go to tower.local or the IP addres, it always redirects to the xxx.unraid.net URL which requires a functioning internet and DNS which isn't always true when I reboot the server. This seems like a bug. When I uninstall this plugin and reboot the server, I don't expect any remnants of the xxx.unraid.net to exist. How do I completely remove this redirection and go back to using my IP address directly? Update, well I looked at the /etc/nginx/conf.d/emhttp-servers.conf file and found the offending line here: server { # # Redirect http requests to https # listen *:80 default_server; listen [::]:80 default_server; return 302 https://xxxxx.unraid.net:443$request_uri; } However commenting it out just breaks the webUI and reverting the whole file to a backup and rebooting results in it being regenerated again. I can't find where to turn it off. I've already uninstalled the plugin so I can't go into any settings and turn things off. I even tried re-installing the plugin, turning off the remote access etc and then uninstalling but still have the same problem. Also, it is still using the WebUI SSL certificate that it installed for use with the unraid.net plugin. How do I remove that too? I just want it to go back to the way it was without any of the unraid.net stuff. I was able to locate the certificate here: /boot/config/ssl/certs/certificate_bundle.pem and the original one is in the same folder here: /boot/config/ssl/certs/Tower_unraid_bundle.pem but not sure what to do with them. _____________________________ Final Update -> Solved Under Settings -> Management Access -> Use SSL/TLS. When I hit the ? symbol, I saw this useful help page: The path is actually /boot/config/ssl/certs. In there I found the offending certificate, certificate_bundle.pem. I moved it somewhere else for safekeeping and rebooted the server and then it finally went back to normal. 🔍 Mystery solved.

When adding Code block into a post, there are several language options but not the one I use the most, Bash. Please add a Bash Syntax Highlighting option in the Code Block popup. Thank you

The "drvload" command should be run within the "Command Prompt" box, so it is surprising to me that anything would hang since it's not a full-blown windows environment. I don't really know but if it's hanging after loading the virtio driver, then take a look at which iso you are using. I'm using this one: Maybe you could try different ones.

@NanoI just made a quick guide. Hope that helps.

Pre-requisites - You have Nginx Proxy Manager already installed and working. I am using this one from the Community Applications: jlesage/nginx-proxy-manager: - You have installed goaccess from Community Applications but it's not working out-of-the-box. I am using this one from the Community Applications: gregyankovoy/goaccess There are three main steps 1- Have your log generator container (Nginx Proxy Manager) output its logs into a folder that goaccess can, well, access 2- Configure goaccess to look for the right log file 3- Configure goaccess to understand how to parse the log/date/time format Step One: Map Log File Folder I use Nginx Proxy Manager and by default, it puts its access logs in the file /config/log/default.log. This location is non-configurable. Well, actually it's configured in the file /etc/nginx/nginx.conf with the line: access_log /config/log/default.log proxy; ... but nginx.conf is not in a mapped folder so I just left it alone. I just ensured that it mapped its /config/log folder to a folder that both containers could access. In my case, I used /mnt/user/dmz/goaccess/log Step Two: Configure Log File The goaccess container looks for its access logs in the file /opt/log/access.log by default. Luckily, this is configurable in the goaccess.conf file that is mapped to the host's /mnt/user/appdata/goaccess/goaccess.conf file. In there, change the line: log-file /opt/log/access.log To: log-file /opt/log/default.log Step Three: Configure Log Format The other thing to do is to provide the log/date/time file format that Nginx Proxy Manager uses in a language that goaccess understands. The nginx format is defined in the same nginx.conf file mentioned above as: log_format standard '[$time_local] $status - $request_method $scheme $host "$request_uri" [Client $remote_addr] [Length $body_bytes_sent] [Gzip $gzip_ratio] "$http_user_agent" "$http_referer"'; There is a nifty script that does this mapping for you here. The short story is that it has to look like this for goaccess to understand it otherwise you get parsing errors. time-format %T date-format %d/%b/%Y log_format [%d:%t %^] %s - %m %^ %v "%U" [Client %h] [Length %b] [Gzip %^] "%u" "%R" Now, open the file goaccess.conf again and comment out the line: log-format COMBINED and paste the three lines describing the log/date/time format we want. That's it. You should now have a beautiful dashboard of your Nginx Proxy Manager access logs including which subdomains are getting used most (virtual hosts) and which URLs end up going to 404 (possible attacks) and a whole lot more besides! Sample Dashboard: Note that it should update in real time as long as the settings cog on the left has a green dot near it like this: That means that the websocket is connected. BONUS If you want to get all geeky and see the results in a terminal window, you can do that too. Just open the goaccess container's Console window and paste the three lines of log/date/time format into the file ~/.goaccessrc so it looks like this: # cat ~/.goaccessrc time-format %T date-format %d/%b/%Y log_format [%d:%t %^] %s - %m %^ %v "%U" [Client %h] [Length %b] [Gzip %^] "%u" "%R" and run: goaccess /opt/log/default.log And you will get the same information in a terminal window: (Navigate with TAB and SHIFT+TAB button to jump between sections and ENTER to expand selection. q to quit)

You would need to put your public key in: /root/.ssh/authorized_keys However, in order to survive a reboot, you'll have to put it in the USB flash drive too. That location is: /boot/config/ssh/authorized_keys Note that if you do this, you won't be able to use Virt Manager because that requires a username/password to login with.

Pardon the stupid question but isn't that everything that matters though? I thought those are the main Unraid folders that you'd want it to run on. What is it for if not that?

@jowi How do I get pip (for python 2.7.10) to work on Unraid? I have Nerd Pack and Dev Pack installed. I have version 2.7.10 of Python. When I run the above command, I get: # python -m ensurepip --default-pip ERROR:root:code for hash md5 was not found. Traceback (most recent call last): File "/usr/lib64/python2.7/hashlib.py", line 147, in <module> globals()[__func_name] = __get_hash(__func_name) File "/usr/lib64/python2.7/hashlib.py", line 97, in __get_builtin_constructor raise ValueError('unsupported hash type ' + name) ValueError: unsupported hash type md5 ERROR:root:code for hash sha1 was not found. Traceback (most recent call last): File "/usr/lib64/python2.7/hashlib.py", line 147, in <module> globals()[__func_name] = __get_hash(__func_name) File "/usr/lib64/python2.7/hashlib.py", line 97, in __get_builtin_constructor raise ValueError('unsupported hash type ' + name) ValueError: unsupported hash type sha1 ERROR:root:code for hash sha224 was not found. Traceback (most recent call last): File "/usr/lib64/python2.7/hashlib.py", line 147, in <module> globals()[__func_name] = __get_hash(__func_name) File "/usr/lib64/python2.7/hashlib.py", line 97, in __get_builtin_constructor raise ValueError('unsupported hash type ' + name) ValueError: unsupported hash type sha224 ERROR:root:code for hash sha256 was not found. Traceback (most recent call last): File "/usr/lib64/python2.7/hashlib.py", line 147, in <module> globals()[__func_name] = __get_hash(__func_name) File "/usr/lib64/python2.7/hashlib.py", line 97, in __get_builtin_constructor raise ValueError('unsupported hash type ' + name) ValueError: unsupported hash type sha256 ERROR:root:code for hash sha384 was not found. Traceback (most recent call last): File "/usr/lib64/python2.7/hashlib.py", line 147, in <module> globals()[__func_name] = __get_hash(__func_name) File "/usr/lib64/python2.7/hashlib.py", line 97, in __get_builtin_constructor raise ValueError('unsupported hash type ' + name) ValueError: unsupported hash type sha384 ERROR:root:code for hash sha512 was not found. Traceback (most recent call last): File "/usr/lib64/python2.7/hashlib.py", line 147, in <module> globals()[__func_name] = __get_hash(__func_name) File "/usr/lib64/python2.7/hashlib.py", line 97, in __get_builtin_constructor raise ValueError('unsupported hash type ' + name) ValueError: unsupported hash type sha512 Ignoring ensurepip failure: pip 6.1.1 requires SSL/TLS

There are many plugins that add to the Dashboard. The Plex Streams plugin is just one example. It has it's own Tab as well as a Dashboard widget Are you saying that you can't add to the UD widget in the Dashboard or that you don't want to (which is fine if that's the case)?

A reboot seems to heal things for now. I can see the Unassigned devices listed under Main now. Another question about the plugin: How come the Utilization bar is not populated in the Dashboard but is populated in the Main tab? Dashboard: Main:

My server is acting weird. Super high average load values even after stopping all VMs and docker. It may or not be related. There are a ton of hdparm calls in the D (uninterruptible sleep) state. I don't know if that's a plugin or OS thing I posted a thread about it here:

I stopped all my VMs and docker containers but it's still inthe same state. I looked at htop again and it's full of calls to hdparm that are in the D (uninterruptble sleep) state.

tower-diagnostics-20210227-1553.zip

I can't see anything in the syslog ot explainthe high load. I checked again today and it's up to the 90s! I tried running nethog and it doesn't show a big Network bandwidth usage I tried to restart the webui portion with these commands but now the webUI won't load even though all the docker webapps still do /etc/rc.d/rc.nginx restart /etc/rc.d/rc.nginx reload /etc/rc.d/rc.php-fpm restart /etc/rc.d/rc.php-fpm reload I don't see any errors in the syslog other than the timeouts. Is there some other log file to watch? Feb 27 15:57:30 Tower nginx: 2021/02/27 15:57:30 [error] 31631#31631: *271274 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.86.22, server: , request: "POST /plugins/unassigned.devices/UnassignedDevices.php HTTP/1.1", subrequest: "/auth_request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "tower", referrer: "http://tower/Main" Feb 27 15:57:30 Tower nginx: 2021/02/27 15:57:30 [error] 31631#31631: *271274 auth request unexpected status: 504 while sending to client, client: 192.168.86.22, server: , request: "POST /plugins/unassigned.devices/UnassignedDevices.php HTTP/1.1", host: "tower", referrer: "http://tower/Main" Feb 27 16:07:30 Tower nginx: 2021/02/27 16:07:30 [error] 31631#31631: *272608 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.86.22, server: , request: "GET /Plugins HTTP/1.1", subrequest: "/auth_request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "tower", referrer: "http://tower/Main" Feb 27 16:07:30 Tower nginx: 2021/02/27 16:07:30 [error] 31631#31631: *272608 auth request unexpected status: 504 while sending to client, client: 192.168.86.22, server: , request: "GET /Plugins HTTP/1.1", host: "tower", referrer: "http://tower/Main" Running netstat reveals that it is listening on all other ports, but not on 80. I can ssh into the sever but don't know what else to look at I've attached diagnostics. Please help! tower-diagnostics-20210227-1553.zip

The toggles are all on. Toggling them off and on didn't make a difference. Clicking on the reload button returned Success but nothing changed Clicking on the Gear icon tried to go to "/Settings/UnassignedDevicesSettings" but it hangs there and never loads. syslog shows a timeout. All other pages seem to load fine. Feb 27 15:28:00 Tower nginx: 2021/02/27 15:28:00 [error] 31631#31631: *265334 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.86.22, server: , request: "POST /plugins/unassigned.devices/UnassignedDevices.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "tower", referrer: "http://tower/Main"

I recently updated this plugin and can no longer see my unassigned devices listed in the Main tab of the webUI. It shows up in the Dashboard though Dashboard: Main: I have both Unassigned Devices and Unassigned Devices Pro installed: Using UNRAID Version: 6.8.3

I think this is a bug in the WebUI. The Dashboard shows one CPU code at 100% all the time. No change. It's been like this for days. I checked htop and that core is not at 100%. It changes, but is generally low: I checked my CPU allocations under VMs (/Dashboard/CPUset) and there are only three used VMs and that CPU (8 & 20) is pinned to a Win 10 VM. I paused that VM but it is still stuck at 100% in the WebUI. I checked Docker and there are no CPUs pinned to anything. Am I missing something or is this a bug? Is there any way to reset things (webUI or something) without having to restart the server?

The docker image that this template uses is missing the security features that the latest one in GitHub contains even though the GitHub code is 5 years old. This one doesn't have this security settings page under http://<ip>/settings/security: nor the corresponding settings.security.html page available in the GitHub version: GitHub: UNRAID: root@dc87d0587a01:/opt/youtransfer/dist/views/pages# ls -lsth total 52K 4.0K -rw-r--r-- 1 root root 608 Feb 10 17:47 unlock.html 4.0K -rw-r--r-- 1 root root 2.8K Feb 10 17:47 settings.transfer.html 4.0K -rw-r--r-- 1 root root 3.7K Feb 10 17:47 settings.template.html 4.0K -rw-r--r-- 1 root root 1.7K Feb 10 17:47 settings.html 8.0K -rw-r--r-- 1 root root 6.1K Feb 10 17:47 settings.storage.html 4.0K -rw-r--r-- 1 root root 3.0K Feb 10 17:47 settings.general.html 4.0K -rw-r--r-- 1 root root 1.4K Feb 10 17:47 settings.finalise.html 12K -rw-r--r-- 1 root root 9.9K Feb 10 17:47 settings.email.html 4.0K -rw-r--r-- 1 root root 1006 Feb 10 17:47 index.html 4.0K -rw-r--r-- 1 root root 743 Feb 10 17:47 download.html

Support for JFrog Artifactory OSS docker container Application Name: JFrog Artifactory OSS Application Site: https://www.jfrog.com/ Docker Hub: JFrog Private Registry: docker.bintray.io/jfrog/artifactory-oss:6.23.7 Github Template: https://github.com/frakman1/docker-templates/blob/master/tynor88/artifactory-oss.xml Default credentials: admin/password

Since there are user icons available in the Users tab like this: Then why not include them in the Dashboard's Users table? Instead of: Why not this:

Thank you @jonathanm It turned out to be Dynamix System Temperature plugin. It's for the CPU and Mainboard temperature (not the hard drives). I didn't set it up so it defaults to that. I got it to work now. Too bad it doesn't support putting the harddrive temperature there. I hate having to go to the Main or Dashboard pages just to see the temperature. I wish it was available everywhere in a banner or footer. Looks like this when it works:

I'm on Version: 6.8.3 I never noticed this before but I checked the footer in the WebUI and there are two temperature icons and they are both set to infinity. Any ideas how to get this to work properly? The Dashboard shows the correct temperatures:

I'm on Version: 6.8.3 I never noticed this before but I checked the footer in the WebUI and there are two temperature icons and they are both set to infinity. Any ideas how to get this to work properly? The Dashboard shows the correct temperatures: