Laov

Hello, I did look into the user scripts plugin however pressing run in background does not generate the email from any of my scrips. This email only appears during startup of my server. Anything else I could look into? I am not that experienced using linux so I would really appreciate detailed instructions.

Hello, I started getting these emails: nginx: the configuration file /etc/nginx/nginx.conf syntax is ok nginx: configuration file /etc/nginx/nginx.conf test is successful These seem completely useless. Can some one help me find why these are coming from my server and how to dissable them?

I doubt this is related to ZFS master plugin so you might want to make a general support thread for this. On a side note from personal experience I've had issues with UNRAID resetting user passwords and permissions. Though this happened when rebuilding unraid USB from a backup. It is quite simple to reset user password and permissions so you may as well try.

Well at that time I didn't know that SSL/TLS: STRICT forces redirect to through that proxy - so no internet no unraid management... Meh... Switching it to Yes should solve my issue.

I had a similar issue as well when my internet connection went down. Could no longer access Unraid managment from my local network via: https://192-168-0-10.HASH.myunraid.net/ For now I disabled Use SSL/TLS: STRICT in hopes that I will be able to access it via local ip if internet goes down again... Though I doubt it is specifically related to tailscale...

I ran a correcting check but it came back with 0 errors... Notification also consistently shows the previous parity checks result I really have to wonder where this 1 error came from...

Yes. I checked. It says I have 1 error. What should my next steps be as it was a non correcting parity check that found it? I'd like to identify the cause. Attached diagnostics. dataserver-diagnostics-20231001-1517.zip

Hello, I ran into this weird situation where notifications say that my parity check came out clean yet the parity history says I had 1 error. Notifications: Parity history: I wonder what should I believe... Notification seems to be reporting last parity check instead of the current one (speed and time difference)? I run non correcting parity checks monthly. Had no issues for ~1 year. But now since 1 error came up I wonder how should I correctly handle it or identify which drive it came from? There are no smart errors logged from any of my drives... Or should I just run a correcting parity check and forget about it?

Thx! Works exactly as expected now! Time to hunt down non ZFS master related spin ups now! BUT STILL! There is a minor bug: This timer still gets updated every time you visit the main page even if no data is pulled. It also does not conform to the same format as server -> settings -> date and time. (24 h vs 12 h format) And a thought for improvement: Is there a way to keep last loaded ZFS data visible past the main page refresh? Currently when no information is loaded on page refresh plugin is shown empty. I think it would be much better to display last loaded data (given that the timestamp at the top is also fixed to display the time this data was pulled).

Are you sure the fix for refresh works? I have the latest plugin version. Settings: And every time I enter my Main page the plugins last refresh keeps changing:. My drives also spin up. PS: I also tried with Lazy Load = Yes with the same result. Every time you enter the Main tab a refresh happens and then every time you click the main tab it also refreshes...

I usually just avoid the "main" tab as the plague and only go to it if I need something. Otherwise if I just let the server sit ZFS master causes no issues...

You just need to advertise the IPs you want to be visible with advertise-routes command. Example: 1. Just open the Unraid console and run: tailscale set --advertise-routes=192.168.0.0/24

Basically that and no docker overhead. Perhaps a bit more support as the docker guy only releases versions and rarely answers questions. As he himself said - the only reason to use docker is if you are doing something interesting with routing docker containers through tailscale.

0/24 is meant to advertise the entire subnet (0 - 255 last number IP range). If it is ok then yes. For me it was. As for why it didn't work maybe someone else will answer. Maybe .2/32 is the correct syntax for a single IP. Feel free to read this: https://www.freecodecamp.org/news/subnet-cheat-sheet-24-subnet-mask-30-26-27-29-and-other-ip-address-cidr-network-references/ I was to lazy.

In tailscale console tailscale set --advertise-routes=192.168.1.2 Then in plugin settings enable IP forwarding And finally in tailscale admin console (tailscale web page) accept the advertised subnet.

Same for me... I guess Tailscale is somehow blocking SMB port on the tailscale IP and domain name. What worked for me is advertising my servers internal IP and using it for shares.

In my case the ZFS master plugin was causing drive spin ups every time I entered the Main page. When I set the refresh option to longer drives would stay spun down for a while. Once I removed the plugin drives are no longer spining up when I enter the Main page. What is weird is that it would spin up ALL my drives even the XFS one. Perhaps the plugin does a default refresh once the page is entered? Will this also be disabled with the 'manual' option? Perhaps there could be a way to only refresh for SSDs and keep HDDs idle until requested?

I am having the same issue. Aparently these files are being used: ** Disk 1 ** Jul 29 18:19:03 CREATE => /mnt/disk1/1616079831.tmp Jul 29 18:19:03 OPEN => /mnt/disk1/1616079831.tmp Jul 29 18:19:03 MODIFY => /mnt/disk1/1616079831.tmp Jul 29 18:19:03 OPEN => /mnt/disk1/1616079831.tmp Jul 29 18:19:03 DELETE => /mnt/disk1/1616079831.tmp I am not sure where they come from... Apparently it was the ZFS plugin that kept spinning up my drives every time I entered the Main tab....

1. Thx. Would be nice to include this in the help section. 2. Done. Damn it would be nice to have a progress bar for this one... I hate staring at a page refreshing symbol and wondering if something is happening... DataServer-tailscale-diag-20230726-030227.zip

Hello, How do I add --advertise-routes=192.168.0.0/24 to the tailscale plugin? I did not see this option under settings... However it shows up in the Info tab... Also perhaps you can help with my quest to access an unraid share from a tailscale network? I can't access any of my unraid shares from a windows PC when I connect to tailscale VPN. I tried using DNS name (unraid) - ping works, access from windows explorer \\unraid\share does not... I tried using tailscale IP - same ressult. The only thing that ACTUALLY WORKS is advertising my local IP to tailscale and then I can easily access all my shares... But ideally I want to use DNS name for this task instead of IP.

Thanks. This worked well after a bit of confusion setting it up.

Actually scratch that It worked. Just had to put the full string 192-168-0-10.xe99ax999axx6c9fxx3e479dxcxdec3c8x1xf1ec.myunraid.net instead of IP Also perhaps you can expand this to work with dockers as well.

1st a note about UI - the notifications cover the log out. Please move them somewhere Really liked the idea but it did not work... Maybe it is due to self signed SSL certificate used for unraid connect but yea I have no idea atm Here is the log hope you can help. I really need an easy way let users start their own VMs [0] [Symbol(res)]: [TLSWrap], [0] [Symbol(verified)]: false, [0] [Symbol(pendingSession)]: null, [0] [Symbol(async_id_symbol)]: 777, [0] [Symbol(kHandle)]: null, [0] [Symbol(lastWriteQueueSize)]: 248, [0] [Symbol(timeout)]: null, [0] [Symbol(kBuffer)]: null, [0] [Symbol(kBufferCb)]: null, [0] [Symbol(kBufferGen)]: null, [0] [Symbol(kCapture)]: false, [0] [Symbol(kSetNoDelay)]: false, [0] [Symbol(kSetKeepAlive)]: true, [0] [Symbol(kSetKeepAliveInitialDelay)]: 60, [0] [Symbol(kBytesRead)]: 0, [0] [Symbol(kBytesWritten)]: 248, [0] [Symbol(connect-options)]: [Object] [0] }, [0] _header: 'POST /login HTTP/1.1\r\n' + [0] 'Accept: */*\r\n' + [0] 'Content-Type: application/x-www-form-urlencoded\r\n' + [0] 'User-Agent: axios/1.3.3\r\n' + [0] 'Content-Length: 32\r\n' + [0] 'Accept-Encoding: gzip, compress, deflate, br\r\n' + [0] 'Host: 192.168.0.10\r\n' + [0] 'Connection: close\r\n' + [0] '\r\n', [0] _keepAliveTimeout: 0, [0] _onPendingData: [Function: nop], [0] agent: Agent { [0] _events: [Object: null prototype], [0] _eventsCount: 2, [0] _maxListeners: undefined, [0] defaultPort: 443, [0] protocol: 'https:', [0] options: [Object: null prototype], [0] requests: [Object: null prototype] {}, [0] sockets: [Object: null prototype], [0] freeSockets: [Object: null prototype] {}, [0] keepAliveMsecs: 1000, [0] keepAlive: false, [0] maxSockets: Infinity, [0] maxFreeSockets: 256, [0] scheduling: 'lifo', [0] maxTotalSockets: Infinity, [0] totalSocketCount: 1, [0] maxCachedSessions: 100, [0] _sessionCache: [Object], [0] [Symbol(kCapture)]: false [0] }, [0] socketPath: undefined, [0] method: 'POST', [0] maxHeaderSize: undefined, [0] insecureHTTPParser: undefined, [0] path: '/login', [0] _ended: false, [0] res: null, [0] aborted: false, [0] timeoutCb: null, [0] upgradeOrConnect: false, [0] parser: null, [0] maxHeadersCount: null, [0] reusedSocket: false, [0] host: '192.168.0.10', [0] protocol: 'https:', [0] [Symbol(kCapture)]: false, [0] [Symbol(kBytesWritten)]: 0, [0] [Symbol(kEndCalled)]: true, [0] [Symbol(kNeedDrain)]: false, [0] [Symbol(corked)]: 0, [0] [Symbol(kOutHeaders)]: [Object: null prototype] { [0] accept: [Array], [0] 'content-type': [Array], [0] 'user-agent': [Array], [0] 'content-length': [Array], [0] 'accept-encoding': [Array], [0] host: [Array] [0] }, [0] [Symbol(kUniqueHeaders)]: null [0] }, [0] cause: Error: self signed certificate [0] at TLSSocket.onConnectSecure (node:_tls_wrap:1539:34) [0] at TLSSocket.emit (node:events:513:28) [0] at TLSSocket._finishInit (node:_tls_wrap:953:8) [0] at TLSWrap.ssl.onhandshakedone (node:_tls_wrap:734:12) { [0] code: 'DEPTH_ZERO_SELF_SIGNED_CERT' [0] } [0] } [1] HTTP 7/25/2023 1:26:20 AM 192.168.0.222 GET /src/assets/favicon.ico [1] HTTP 7/25/2023 1:26:20 AM 192.168.0.222 Returned 304 in 1 ms

Yes I did that as well. But now I have a situation where a few different VMs are needed and they are RAM intensive. Thus currently I would like to leave an option to shut down in case the user needs a different VM and wants to have maximum RAM allocated... It would be so nice if Unraid had a "user" gui login that would have limited rights. Say manage VMs, start/stop dockers... But for now I need a work around...

Hello, I need a way to let users start their own VMs on my unraid server. I don't wish to be bothered again with the "I accidentally shut down my VM can you start it for me coz I don't have access to your Unraid root". Is there any webui that would enable VM start / stop? Or a command line script that I could run on a windows machine that would try in start a VM?