kiwijunglist

Hi I just installed tailscale plugin and I can no longer access the unraid gui (Unraid version 6.11.5) I can still access all my local dockers and I can access the server via SSH. The tailscale plugin breaks access to the unraid GUI via both the local url and the myunraid.net. Is there an SSH command to disable tailscale plugin? Do you want any particular logs for this problem. (Of note I am using dynamic remote access for unraid connect) Thanks

Attached is diagnostics post fixing the problem. Hopefully might help with any bug fixing etc diag-postfix.zip

I issued the following two commands and it was fixed (without needing to restart system) nginx -s reload /etc/rc.d/rc.inetd restart

I found this error: root@manitoba:/# nginx nginx: [emerg] bind() to unix:/var/run/nginx.socket failed (98: Address already in use) nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use) nginx: [emerg] bind() to [::]:80 failed (98: Address already in use) nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use) nginx: [emerg] bind() to [::]:443 failed (98: Address already in use) Message from syslogd@manitoba at Sep 18 18:53:48 ... nginx: 2023/09/18 18:53:48 [emerg] 6381#6381: bind() to unix:/var/run/nginx.socket failed (98: Address already in use) Message from syslogd@manitoba at Sep 18 18:53:48 ... nginx: 2023/09/18 18:53:48 [emerg] 6381#6381: bind() to 0.0.0.0:80 failed (98: Address already in use) Message from syslogd@manitoba at Sep 18 18:53:48 ... nginx: 2023/09/18 18:53:48 [emerg] 6381#6381: bind() to [::]:80 failed (98: Address already in use) Message from syslogd@manitoba at Sep 18 18:53:48 ... nginx: 2023/09/18 18:53:48 [emerg] 6381#6381: bind() to 0.0.0.0:443 failed (98: Address already in use) Message from syslogd@manitoba at Sep 18 18:53:48 ... nginx: 2023/09/18 18:53:48 [emerg] 6381#6381: bind() to [::]:443 failed (98: Address already in use) nginx: [emerg] bind() to unix:/var/run/nginx.socket failed (98: Address already in use) nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use) nginx: [emerg] bind() to [::]:80 failed (98: Address already in use) nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use) nginx: [emerg] bind() to [::]:443 failed (98: Address already in use) Message from syslogd@manitoba at Sep 18 18:53:48 ... nginx: 2023/09/18 18:53:48 [emerg] 6381#6381: bind() to unix:/var/run/nginx.socket failed (98: Address already in use) Message from syslogd@manitoba at Sep 18 18:53:48 ... nginx: 2023/09/18 18:53:48 [emerg] 6381#6381: bind() to 0.0.0.0:80 failed (98: Address already in use) Message from syslogd@manitoba at Sep 18 18:53:48 ... nginx: 2023/09/18 18:53:48 [emerg] 6381#6381: bind() to [::]:80 failed (98: Address already in use) Message from syslogd@manitoba at Sep 18 18:53:48 ... nginx: 2023/09/18 18:53:48 [emerg] 6381#6381: bind() to 0.0.0.0:443 failed (98: Address already in use) Message from syslogd@manitoba at Sep 18 18:53:48 ... nginx: 2023/09/18 18:53:48 [emerg] 6381#6381: bind() to [::]:443 failed (98: Address already in use) nginx: [emerg] bind() to unix:/var/run/nginx.socket failed (98: Address already in use) nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use) nginx: [emerg] bind() to [::]:80 failed (98: Address already in use) nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use) nginx: [emerg] bind() to [::]:443 failed (98: Address already in use) Message from syslogd@manitoba at Sep 18 18:53:49 ... nginx: 2023/09/18 18:53:48 [emerg] 6381#6381: bind() to unix:/var/run/nginx.socket failed (98: Address already in use) Message from syslogd@manitoba at Sep 18 18:53:49 ... nginx: 2023/09/18 18:53:48 [emerg] 6381#6381: bind() to 0.0.0.0:80 failed (98: Address already in use) Message from syslogd@manitoba at Sep 18 18:53:49 ... nginx: 2023/09/18 18:53:48 [emerg] 6381#6381: bind() to [::]:80 failed (98: Address already in use) Message from syslogd@manitoba at Sep 18 18:53:49 ... nginx: 2023/09/18 18:53:48 [emerg] 6381#6381: bind() to 0.0.0.0:443 failed (98: Address already in use) Message from syslogd@manitoba at Sep 18 18:53:49 ... nginx: 2023/09/18 18:53:48 [emerg] 6381#6381: bind() to [::]:443 failed (98: Address already in use) nginx: [emerg] bind() to unix:/var/run/nginx.socket failed (98: Address already in use) nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use) nginx: [emerg] bind() to [::]:80 failed (98: Address already in use) nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use) nginx: [emerg] bind() to [::]:443 failed (98: Address already in use) Message from syslogd@manitoba at Sep 18 18:53:49 ... nginx: 2023/09/18 18:53:48 [emerg] 6381#6381: bind() to unix:/var/run/nginx.socket failed (98: Address already in use) Message from syslogd@manitoba at Sep 18 18:53:49 ... nginx: 2023/09/18 18:53:48 [emerg] 6381#6381: bind() to 0.0.0.0:80 failed (98: Address already in use) Message from syslogd@manitoba at Sep 18 18:53:49 ... nginx: 2023/09/18 18:53:48 [emerg] 6381#6381: bind() to [::]:80 failed (98: Address already in use) Message from syslogd@manitoba at Sep 18 18:53:49 ... nginx: 2023/09/18 18:53:48 [emerg] 6381#6381: bind() to 0.0.0.0:443 failed (98: Address already in use) Message from syslogd@manitoba at Sep 18 18:53:49 ... nginx: 2023/09/18 18:53:48 [emerg] 6381#6381: bind() to [::]:443 failed (98: Address already in use) nginx: [emerg] bind() to unix:/var/run/nginx.socket failed (98: Address already in use) nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address already in use) nginx: [emerg] bind() to [::]:80 failed (98: Address already in use) nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use) nginx: [emerg] bind() to [::]:443 failed (98: Address already in use) Message from syslogd@manitoba at Sep 18 18:53:50 ... nginx: 2023/09/18 18:53:48 [emerg] 6381#6381: bind() to unix:/var/run/nginx.socket failed (98: Address already in use) Message from syslogd@manitoba at Sep 18 18:53:50 ... nginx: 2023/09/18 18:53:48 [emerg] 6381#6381: bind() to 0.0.0.0:80 failed (98: Address already in use) Message from syslogd@manitoba at Sep 18 18:53:50 ... nginx: 2023/09/18 18:53:48 [emerg] 6381#6381: bind() to [::]:80 failed (98: Address already in use) Message from syslogd@manitoba at Sep 18 18:53:50 ... nginx: 2023/09/18 18:53:48 [emerg] 6381#6381: bind() to 0.0.0.0:443 failed (98: Address already in use) Message from syslogd@manitoba at Sep 18 18:53:50 ... nginx: 2023/09/18 18:53:48 [emerg] 6381#6381: bind() to [::]:443 failed (98: Address already in use) nginx: [emerg] still could not bind() Message from syslogd@manitoba at Sep 18 18:53:50 ... nginx: 2023/09/18 18:53:48 [emerg] 6381#6381: still could not bind()

I should add. This is a problem cropped up this morning, and everything was working fine yesterday and I haven't changed any unraid or network settings recently. Have also tried to clear browser cache and a different browser/device.

The other thing that is intersting is if I attempt to access my unraid server via connect myunraid from outside the local network then it says "Dynamic Remote Access is enabled, but not required for this server to be managed from your current location." which is strange, because it definitely is required in this situation.

Hi Unraid 6.11.5 I can access the login page on my local network: 192.168.1.173 However after entering the login details it tries to load the myunraid address http://192-168-1-173.xxxxxxxxxxxxxxxxx.myunraid.net:8081/ This doesn't work and nothing loads. This used to work but has stopped working. I can still access the server via SSH, the dockers are still working and I can view the server on: https://connect.myunraid.net/server/details/xxxxxxxxxxxxxxxxxxxx However I can't manage the server. Attached diag-nostics file Thanks diag.zip

what was the option in bios? I've been unable to get a good powerstate in Pkg(hw). I'm sure i've added all the options i need in bios.

if you benchmark the parity drive in the array, does that break the parity?

Hi, Are these errors a problem (unraid 6.11.5) ? root@manitoba:~# powertop --auto-tune powertop: /lib64/libncursesw.so.6: no version information available (required by powertop) powertop: /lib64/libtinfo.so.6: no version information available (required by powertop) modprobe cpufreq_stats failed Loaded 0 prior measurements Cannot load from file /var/cache/powertop/saved_parameters.powertop File will be loaded after taking minimum number of measurement(s) with battery only RAPL device for cpu 0 RAPL device for cpu 0 Devfreq not enabled glob returned GLOB_ABORTED Cannot load from file /var/cache/powertop/saved_parameters.powertop File will be loaded after taking minimum number of measurement(s) with battery only Leaving PowerTOP

Just in case someone has trouble adding config.gateway.json you need to place the folder inside \data\sites\your_site_name eg. for unraid running unifi controller in docker it would be "appdata\unifi-controller\data\sites\default" If you don't have \data\sites\ directory you need to create the folders by creating a "floor plan" in unifi. Click topology , then floorplan , then add floorplan. If you don't have the floor plan option in the GUI you need to enable the legacy GUI under settings -> advanced or something like that. Then you can create the config.gateway.json file and you should be good to go. After creating / editing the file you need to run "force provision" to the USG in UniFi Devices > select the USG > Config > Manage Device > Force provision. Hope that helps others.

Thanks... From my experience, on my system , it didn't work (detect button greyed out and can't be clicked and can't choose anything on the PWM controller drop down menu ) and I tried that .... but after installing the dyanmix temp plugin everything was able to be selected etc.

Hi I couldn't get dynamix fan control plugin to work. I have subsequently found out that the dynamix fan plugin only works if you have installed the dyanmix system temp plugin I think this is a bit unclear with the documentation. I suggest that the dynamix plugin throws a warning if the system temp plugin is not installed.

I didn't have any luck with that plugin, at-least initially. It's a bit tricky with dynamix megathread for all the plugins it's hard to find information.

Sorry for what might be a silly question. I wanted to investigate software control of my PWM fans connected to motherboard headers so I could tie the fans to HDD temps etc. My motherboard is Asrock Z790 - https://www.asrock.com/MB/Intel/Z790 Pro RS WiFi/index.asp I have a feeling I can't use the plugin? At least on first try I wasn't able to get it to see any of the fans. Thanks

Hi Thanks for making this plugin. I am using unraid 6.1.1.5 and CA Backup / Restore Appdata 2023.03.28c I have the myservers plugin enabled and have used that to backup to flash drive, but I thought it might be good to also use the plugin to do incremental backups of the flash drive. Is there a way to use this plugin to do incremental backups of the flash drive? It looks like it just supports a one off backup rather than multiple rsync incremental backups. Thanks Mike