Syslog errors after moving VM to Unassigned Devices SSD

[bally12345]

So a few weeks ago, I put a new SSD into my system and mounted it etc. Moved my VM and VM Shares to it but now I am seeing the following errors filling up my syslog

 

Mar  1 13:54:10 Server nginx: 2022/03/01 13:54:10 [error] 17266#17266: *849664 limiting requests, excess: 20.305 by zone "authlimit", client: 192.168.1.4, server: myHash.unraid.net, request: "PROPFIND /login HTTP/2.0", host: "myHash.unraid.net"
Mar  1 13:54:10 Server nginx: 2022/03/01 13:54:10 [error] 17266#17266: *849667 limiting requests, excess: 20.143 by zone "authlimit", client: 192.168.1.4, server: myHash.unraid.net, request: "PROPFIND /login HTTP/2.0", host: "myHash.unraid.net"
Mar  1 13:54:11 Server nginx: 2022/03/01 13:54:11 [error] 17266#17266: *849684 limiting requests, excess: 20.795 by zone "authlimit", client: 192.168.1.4, server: myHash.unraid.net, request: "PROPFIND /login HTTP/2.0", host: "myHash.unraid.net"
Mar  1 13:54:11 Server nginx: 2022/03/01 13:54:11 [error] 17266#17266: *849688 limiting requests, excess: 20.621 by zone "authlimit", client: 192.168.1.4, server: myHash.unraid.net, request: "PROPFIND /login HTTP/2.0", host: "myHash.unraid.net"

 

192.168.1.4 is the static ip assigned to my win11 VM 

server-diagnostics-20220301-1401.zip

[bally12345]

Found people with same issue here 

Looks like it might be something to do with Win11, I have closed all browsers sessions, rebooted VM and server but it did come back. I have also cleared all items in Quick access as I think that was one of the suggestions.

 

 

[bally12345]

logs at 99% again so not sure what it causing this, anyone have any ideas? Might move my VM back to array how it was originally as I did copy to new location using MC. If that doeesnt resolve it, then im assuming its WIN11 related.

[bally12345]

Moved vdisk img back to original location and still seeing this error, so have no idea what is causing.

 

Any suggestions what else I can look at? 

[esaru]

Only thing that worked for me was nuking my VM and doing a clean windows installation. Quite unsatisfying as far as solutions go..