Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

How to setup WinNUT Client on Win 10 with synology #47

Closed
witzker opened this issue Dec 10, 2020 · 107 comments
Closed

How to setup WinNUT Client on Win 10 with synology #47

witzker opened this issue Dec 10, 2020 · 107 comments
Labels
good first issue Good for newcomers

Comments

@witzker
Copy link

witzker commented Dec 10, 2020

I put in the NUT Host IP
As port for Synology 3493
Smart-UPS C 1500 as shown in Synology Host

username and PW for Synology Admin

When I click connect nothing happens.
Pls Help
@gbakeman
Copy link
Contributor

When I was setting up the original NUT software to talk to a Synology host, I found out that Synology uses a hardcoded username/password to connect to their NUT software. In /etc/syno/etc/ups/ups.users, the username is monuser and password is secret. Although when I just tried this with WinNUT, it did not indicate a successful or failed connection, so I think it may be silently failing somewhere.

@FileCity
Copy link

I always setup my NUT server (with the UPS connected to it) on a Linux machine and then I setup each clients.
You can use a Raspberry Pi as server, works very well and it's using the complete NUT package with all options available.

@gbakeman
Copy link
Contributor

Update for @witzker: I was able to get this working with my Synology device.

On your Diskstation web page, go to Control Panel, Hardware & Power, then click on the UPS tab. Make sure Enable UPS server is checked, then click the Permitted DiskStation devices button. Type in the IP address for your computer running WinNUT. You might need to put in both IPv4 and IPv6 addresses, I'm not clear on which one is preferred. After you've done that, click OK and then Apply. Now open the Options for WinNUT. Type in the hostname or IP for your diskstation in NUT host. Port can be left at 3493, and UPS Name left at UPSName. For login, type upsmon, and for password, type secret. Click OK, and it should connect.

Please let us know if you have any issues with this.

@gawindx
Copy link
Owner

gawindx commented Jan 12, 2021

@tgp1994
Can you take some screenshots and post them? I will have to do a wiki one day or another and that will allow me to inform specific cases.

@gbakeman
Copy link
Contributor

Sure! Here's the first part:

upssetup

  1. Navigate to DiskStation's webui
  2. Open Control Panel
  3. Find the Hardware & Power section
  4. Open the UPS tab
  5. Make sure Enable network UPS server is checked, then click Permitted DistStation Devices
  6. Put in the WinNUT's client IP address, and click OK
  7. Finally click Apply (important!)

Finaly step, in WinNUT:

upssteps2

  1. Open WinNUT, and open the Settings menu.
  2. Put in the hostname or IP address of your DiskStation.
  3. Set login and password as I've set
  4. Click OK, and it should connect.

@SeeBer61
Copy link

SeeBer61 commented Jan 17, 2021 •
edited
Loading

I've just recently set up my UPS (APC Back-UPS Pro) to secure my Diskstations. I've set up UPS monitoring with automated shutdown (to safe mode) in my DS220+ as a server and DS213+ as a client. Now I was looking for a way to include my PCs into this and found this project. Great - love it !!

Actually it took my only one hour to set everything up including configuring Windows NUT client. After some trial & error I did some research and found that only

ups works as a parameter for the UPS Name
3493 as NUT Port, upsmon as Login and secret as password are still the default values in DSM6.x

@gbakeman
Copy link
Contributor

You're right - I don't know why I didn't figure it out before, but I had the ups name wrong the whole time until recently. I'll need to redo the screenshots...

@gawindx gawindx added the good first issue Good for newcomers label Feb 10, 2021
@gfairchild
Copy link

gfairchild commented Feb 23, 2021 •
edited
Loading

I'm trying to get WinNUT 2.0.7722.30975 working with my Synology DS1019+, and I'm having issues getting WinNUT to talk to the NAS. I'm hoping some of you guys might be able to help.

As you can see here, I've got the UPS attached to the NAS:

image

I've got my PC's IP included in the list of permitted devices:

image

I've verified my PC's local IP both in my router's device list table, as well as in my Windows networking settings.

I've plugged everything in WinNUT as best I can:

image

Here, I've tried both monuser and upsmon as the login, and secret is the password. Additionally, I've verified the IP of my NAS, and I've also tried the NAS' hostname.

When I try to list UPS variables, I get this error:

image

[Id 7: 2/22/2021 9:26:54 PM] Connection to Nut Host 192.168.1.46:3493 Failed: Connection to Nut Host seem broken when Retrieving ListUPSVars

Does anyone have any ideas? The firewall on the NAS is completely disabled, so it shouldn't be that. Any help is appreciated!

@gawindx
Copy link
Owner

gawindx commented Feb 23, 2021 •
edited
Loading

Try With « Polling interval » >=1 in your options.

@gfairchild
Copy link

Try With « Polling interval » >=1 in your options.

Ok, that's hilarious; that worked immediately! I should've tried tweaking that setting! Thank you!

@gfairchild
Copy link

One more minor question: I thought I could put a hostname in the NUT host field, but it doesn't seem to work. If I specify the IP of my NAS, I can connect no problem, but if I put the hostname, I get this error:

[Id 8: 2/23/2021 12:04:23 PM] Connection to Nut Host <hostname>:3493 Failed: Access is denied.

Is this expected behavior?

@gbakeman
Copy link
Contributor

Just want to chime in here: I was having issues connecting to my Synology just like you, and the reason seemed to be because I was using an IPv4/v6 combined LAN and the allowed hosts list is very strict about what address you put in. So if I put the hostname in, it resolves to the IPv6 address when I had only put my v4 address in the allowed hosts list.

To work around this, you'll want to make sure you have both IPv4 and v6 addresses in the allowed hosts list, or enter the IPv4 address when you connect. As a note to us developing WinNUT, perhaps we can attempt connection over both addresses if we detect a Synology host or get access denied the first time?

@gawindx
Copy link
Owner

gawindx commented Feb 23, 2021

Well seen for the IPV4 / 6 combo.

@gbakeman, For your suggestion, it would have to be studied but on this blow I could not certainly not develop it alone, I will need one or more beta testers who have a synology.

It will be seen for v2.1 when it starts to be sufficiently developed.

@gfairchild
Copy link

gfairchild commented Feb 23, 2021 •
edited
Loading

Just want to chime in here: I was having issues connecting to my Synology just like you, and the reason seemed to be because I was using an IPv4/v6 combined LAN and the allowed hosts list is very strict about what address you put in. So if I put the hostname in, it resolves to the IPv6 address when I had only put my v4 address in the allowed hosts list.

To work around this, you'll want to make sure you have both IPv4 and v6 addresses in the allowed hosts list, or enter the IPv4 address when you connect. As a note to us developing WinNUT, perhaps we can attempt connection over both addresses if we detect a Synology host or get access denied the first time?

Nice to note. I just put my local IPv6 address in the list of permitted devices:

image

But this still doesn't seem to enable me to connect using the NAS' hostname. WinNUT still yields this error:

[Id 27: 2/23/2021 1:50:36 PM] Connection to Nut Host <hostname>:3493 Failed: Access is denied.

It still only works if I provide the IPv4 address. I tried providing the NAS' IPv6 address in the NUT host field, but that's not working either.

@gawindx, I'm happy to help test.

@gbakeman
Copy link
Contributor

gbakeman commented Feb 23, 2021 •
edited
Loading

Just to double check, are you clicking "Ok" and "Apply" after that? I was only doing one, and that caught me up!

Edit: To confirm, you're adding the IP of your computer running WinNUT and not the NAS, correct?

@gfairchild
Copy link

Just to double check, are you clicking "Ok" and "Apply" after that? I was only doing one, and that caught me up!

Edit: To confirm, you're adding the IP of your computer running WinNUT and not the NAS, correct?

Yes, correct on both accounts. The 2 IPs in that screenshot are of my PC running WinNUT, and I did apply those settings.

@gawindx
Copy link
Owner

gawindx commented Feb 23, 2021

I say maybe a stupidity but there is no limit of the number of connections? a session lifetime?

Normally Winnut forces a clean logout but can synology keep an active session for a while?

@gbakeman
Copy link
Contributor

gbakeman commented Feb 23, 2021 •
edited
Loading

I just double checked on my end, and I think I may have misremembered what I did! I was just now able to authenticate with an IPv6 connection. I admit I still don't understand how IPv6 works, but for some reason my PC has multiple IPv6 addresses. I opened a connection with a terminal (KiTTY), then opened a network monitor (Process Hacker) and found the exact local endpoint it was using. It ended up being a different address than I thought. I added that to the list of authorized clients, and I can connect now.

Lesson learned here: I guess you either need to figure out exactly which IPv6 address the application is using on your PC to establish the connection, add every IPv6 address assigned to your PC to the authorized clients list, disable IPv6 wholesale on your diskstation, or explicitly use IPv4 when connecting.

@gfairchild
Copy link

I say maybe a stupidity but there is no limit of the number of connections? a session lifetime?

Normally Winnut forces a clean logout but can synology keep an active session for a while?

Good question. I can't imagine there is a session limit that's impacting us (i.e., if there is a limit, I'd sure hope it's greater than 2!).

@gfairchild
Copy link

I just double checked on my end, and I think I may have misremembered what I did! I was just now able to authenticate with an IPv6 connection. I admit I still don't understand how IPv6 works, but for some reason my PC has multiple IPv6 addresses. I opened a connection with a terminal (KiTTY), then opened a network monitor (Process Hacker) and found the exact local endpoint it was using. It ended up being a different address than I thought. I added that to the list of authorized clients, and I can connect now.

Lesson learned here: I guess you either need to figure out exactly which IPv6 address the application is using on your PC to establish the connection, add every IPv6 address assigned to your PC to the authorized clients list, disable IPv6 wholesale on your diskstation, or explicitly use IPv4 when connecting.

Ah, your comment really helped! After digging around, for reasons I don't understand yet, I see the same thing. Here's a screenshot of my network adapter properties:

image

Of particular note is that temporary IPv6 address, which is different than the (non-temporary?) IPv6 address listed above it. I thought to check my Synology logs to see what IP Synology's logs are capturing, and I see this:

image

So what Synology is seeing is my temporary IPv6 address, not the other one. When I pasted that IPv6 address into the list of IPs that are permitted to access the NUT service, all of a sudden I can specify the NUT host in WinNUT to be either the IPv4, IPv6, or hostname of my NAS; all 3 work equivalently now.

The fact that my NAS is only seeing the temporary IPv6 is concerning because if I'm supposed to rely on a whitelist in the Synology UI and that IPv6 address is changing with some regularity, then that'll mean that the whitelist is functionally useless.

My takeaway here is to stick with IPv4 addresses in the Synology UI as well as WinNUT preferences. It would be really neat if WinNUT tried connecting to both IPv4 and IPv6 addresses when a hostname is provided (since that's one less static IP that needs to be tracked), but I can use the IPv4 address until that gets implemented.

@BrckedmyRMpro
Copy link

Hi Guys,
I have a Synology 214+Play and have just set up a new APC UPS connected to the NAS. I set up the Power options in the NAS to as shown above and installed the client using the WinNUT-Setup.msi But after configuring the settings as shown above in the NUT I'm unable to get a connection to the NAS host.

When trying to connect I get the following Error message: [Id 19: 01/04/2021 19:13:17] Connection to Nut Host nutserver host:3493 Failed: Connection Error

image

Does anyone have any ides what to try next? I'm not using IPv6 at all so when I use config/all I only have IPv4 addresses shown for the PC.

Thanx for any help.

@gawindx
Copy link
Owner

gawindx commented Apr 1, 2021

Did you authorize your ip in the nas config?
see here

@BrckedmyRMpro
Copy link

Yes I did specify my computer IPv4 in the Synalogy Permitted discstation settings and I can see the ups information in the Nas ups device information.

@gfairchild
Copy link

Can you try using monuser as the username? upsmon didn't work for me, but monuser did.

@BrckedmyRMpro
Copy link

Thank you for the suggestion, Yes I had already tried monuser but still the same result.

@gbakeman
Copy link
Contributor

gbakeman commented Apr 1, 2021

Can you provide the full logs from WinNUT when it tries to connect?

@BrckedmyRMpro
Copy link

Here is the Debug log:

01/04/2021 20:32:23 Pid: 14020 WinNUT : Windows standby, WinNUT will disconnect
01/04/2021 20:48:24 Pid: 14020 WinNUT : Restarting WinNUT after waking up from Windows
01/04/2021 20:49:16 Pid: 14020 Pref_Gui : Pref_Gui Params Saved
01/04/2021 20:49:16 Pid: 14020 WinNUT : Main Gui Has Focus
01/04/2021 20:49:16 Pid: 14020 WinNUT : Update Icon
01/04/2021 20:49:19 Pid: 14020 WinNUT : Force Reconnect from menu
01/04/2021 20:49:40 Pid: 14020 WinNUT : Connect To Nut Server
01/04/2021 20:50:01 Pid: 14020 WinNUT : Error When Connection to Nut Host.
01/04/2021 20:50:01 Pid: 14020 String : New Log to CB_Current Log : Connection to Nut Host 192.168.100.4:3493 Failed: Connection Error
01/04/2021 20:50:02 Pid: 14020 WinNUT : Main Gui Lose Focus
01/04/2021 20:50:02 Pid: 14020 WinNUT : Update Icon
01/04/2021 20:50:17 Pid: 14020 WinNUT : Main Gui Has Focus
01/04/2021 20:50:17 Pid: 14020 WinNUT : Update Icon
01/04/2021 20:50:21 Pid: 14020 WinNUT : Open About Gui From Menu
01/04/2021 20:50:22 Pid: 14020 About_Gui : Load About Gui
01/04/2021 20:50:22 Pid: 14020 WinNUT : Main Gui Lose Focus
01/04/2021 20:50:22 Pid: 14020 WinNUT : Update Icon
01/04/2021 20:50:30 Pid: 14020 About_Gui : Close About Gui
01/04/2021 20:50:30 Pid: 14020 WinNUT : Main Gui Has Focus
01/04/2021 20:50:30 Pid: 14020 WinNUT : Update Icon
01/04/2021 20:50:44 Pid: 14020 WinNUT : Main Gui Lose Focus
01/04/2021 20:50:44 Pid: 14020 WinNUT : Update Icon
01/04/2021 20:50:52 Pid: 14020 WinNUT : Main Gui Has Focus
01/04/2021 20:50:52 Pid: 14020 WinNUT : Update Icon
01/04/2021 20:51:24 Pid: 14020 WinNUT : Open Pref Gui From Menu
01/04/2021 20:51:24 Pid: 14020 Pref_Gui : Load Pref Gui
01/04/2021 20:51:24 Pid: 14020 WinNUT : Main Gui Lose Focus
01/04/2021 20:51:24 Pid: 14020 WinNUT : Update Icon
01/04/2021 20:51:24 Pid: 14020 Pref_Gui : Pref Gui Opened.
01/04/2021 20:51:39 Pid: 14020 Pref_Gui : Show LogFile

@gbakeman
Copy link
Contributor

gbakeman commented Apr 1, 2021

Ok. It looks like we need to make the error messages more clear. :) Just to be sure, when you added your computer's IP address to the authorized devices, did you hit OK then Apply after? I forgot to click Apply one time! If you did that, then it may be worth rebooting your Synology since that has also cleared out some strange NUT server bugs for me.

@BrckedmyRMpro
Copy link

Here is the log after changing the user name to monuser:

01/04/2021 20:51:24 Pid: 14020 WinNUT : Open Pref Gui From Menu
01/04/2021 20:51:24 Pid: 14020 Pref_Gui : Load Pref Gui
01/04/2021 20:51:24 Pid: 14020 WinNUT : Main Gui Lose Focus
01/04/2021 20:51:24 Pid: 14020 WinNUT : Update Icon
01/04/2021 20:51:24 Pid: 14020 Pref_Gui : Pref Gui Opened.
01/04/2021 20:51:39 Pid: 14020 Pref_Gui : Show LogFile
01/04/2021 20:53:02 Pid: 14020 Pref_Gui : Save Parameters.
01/04/2021 20:53:03 Pid: 14020 Pref_Gui : LogFile Enabled.
01/04/2021 20:53:03 Pid: 14020 Pref_Gui : Pref_Gui Params Saved
01/04/2021 20:53:23 Pid: 14020 WinNUT : Main Gui Has Focus
01/04/2021 20:53:23 Pid: 14020 WinNUT : Update Icon
01/04/2021 20:53:27 Pid: 14020 WinNUT : Force Reconnect from menu
01/04/2021 20:53:48 Pid: 14020 WinNUT : Connect To Nut Server
01/04/2021 20:54:09 Pid: 14020 WinNUT : Error When Connection to Nut Host.
01/04/2021 20:54:09 Pid: 14020 String : New Log to CB_Current Log : Connection to Nut Host 192.168.100.4:3493 Failed: Connection Error
01/04/2021 20:54:13 Pid: 14020 WinNUT : Main Gui Lose Focus
01/04/2021 20:54:13 Pid: 14020 WinNUT : Update Icon
01/04/2021 20:54:15 Pid: 14020 WinNUT : Main Gui Has Focus
01/04/2021 20:54:15 Pid: 14020 WinNUT : Update Icon
01/04/2021 20:54:17 Pid: 14020 WinNUT : Force Reconnect from menu
01/04/2021 20:54:38 Pid: 14020 WinNUT : Connect To Nut Server
01/04/2021 20:54:59 Pid: 14020 WinNUT : Error When Connection to Nut Host.
01/04/2021 20:54:59 Pid: 14020 String : New Log to CB_Current Log : Connection to Nut Host 192.168.100.4:3493 Failed: Connection Error
01/04/2021 20:55:03 Pid: 14020 WinNUT : Open Pref Gui From Menu
01/04/2021 20:55:03 Pid: 14020 Pref_Gui : Load Pref Gui
01/04/2021 20:55:03 Pid: 14020 WinNUT : Main Gui Lose Focus
01/04/2021 20:55:03 Pid: 14020 WinNUT : Update Icon
01/04/2021 20:55:03 Pid: 14020 Pref_Gui : Pref Gui Opened.
01/04/2021 20:55:14 Pid: 14020 Pref_Gui : Show LogFile

@Gerbildral
Copy link

i also have problems with connecting the latest winNUT client with synology(updated), i keep getting acces denied. i tried everything on this page, put ipv6 in front of the ipv4 addresses, i clicked apply ;) checked the credentials with ssh. i even made a rule in synology to allow port 3493

here are the settings:
image

here are the debug logs:
8-1-2022 22:32:29 Pid: 18760 Pref_Gui : Pref_Gui Params Saved
8-1-2022 22:32:29 Pid: 18760 WinNUT : WinNut Preferences Changed
8-1-2022 22:32:29 Pid: 18760 String : New Log to CB_Current Log : WinNut Preferences Changed
8-1-2022 22:32:29 Pid: 18760 WinNUT : New Parameter Applyed. Force Reconnect
8-1-2022 22:32:29 Pid: 18760 UPS_Network : Connect To Nut Server
8-1-2022 22:32:29 Pid: 18760 UPS_Network : Enter AuthLogin
8-1-2022 22:32:29 Pid: 18760 UPS_Network : Deconnect from Nut Host
8-1-2022 22:32:29 Pid: 18760 String : New Log to CB_Current Log : Disconnected from Nut Host
8-1-2022 22:32:29 Pid: 18760 UPS_Network : Force Disconnect
8-1-2022 22:32:29 Pid: 18760 WinNUT : NotifyIcon Text =>
WinNUT - 2.0
Reconnection In Progress
Try 0 of 30
8-1-2022 22:32:29 Pid: 18760 WinNUT : Update Icon
8-1-2022 22:32:29 Pid: 18760 UPS_Network : Access is denied.
8-1-2022 22:32:29 Pid: 18760 String : New Log to CB_Current Log : Connection to Nut Host 10.234.10.22:3493 Failed: Access is denied.
8-1-2022 22:32:29 Pid: 18760 WinNUT : Parameter Dial Voltage Battery Need to be Updated
8-1-2022 22:32:29 Pid: 18760 WinNUT : Parameter Dial Voltage Battery Updated
8-1-2022 22:32:29 Pid: 18760 WinNUT : Main Gui Has Focus
8-1-2022 22:32:29 Pid: 18760 WinNUT : Update Icon
8-1-2022 22:32:31 Pid: 18760 WinNUT : Force Reconnect from menu
8-1-2022 22:32:31 Pid: 18760 UPS_Network : Connect To Nut Server
8-1-2022 22:32:31 Pid: 18760 UPS_Network : Enter AuthLogin
8-1-2022 22:32:31 Pid: 18760 UPS_Network : Deconnect from Nut Host
8-1-2022 22:32:31 Pid: 18760 String : New Log to CB_Current Log : Disconnected from Nut Host
8-1-2022 22:32:31 Pid: 18760 UPS_Network : Force Disconnect
8-1-2022 22:32:31 Pid: 18760 WinNUT : NotifyIcon Text =>
WinNUT - 2.0
Reconnection In Progress
Try 0 of 30
8-1-2022 22:32:31 Pid: 18760 WinNUT : Update Icon
8-1-2022 22:32:31 Pid: 18760 UPS_Network : Access is denied.
8-1-2022 22:32:31 Pid: 18760 String : New Log to CB_Current Log : Connection to Nut Host 10.234.10.22:3493 Failed: Access is denied.
8-1-2022 22:32:33 Pid: 18760 WinNUT : Open Pref Gui From Menu
8-1-2022 22:32:33 Pid: 18760 Pref_Gui : Load Pref Gui
8-1-2022 22:32:33 Pid: 18760 WinNUT : Main Gui Lose Focus
8-1-2022 22:32:33 Pid: 18760 WinNUT : Update Icon
8-1-2022 22:32:33 Pid: 18760 Pref_Gui : Pref Gui Opened.
8-1-2022 22:32:36 Pid: 18760 Pref_Gui : Show LogFile

@gbakeman
Copy link
Contributor

gbakeman commented Jan 8, 2022

@Gerbildral Could you post screenshots of:

  • ipconfig /all (run it on your host), and show your current network adapter
  • The host access list and UPS config windows from Diskstation Manager

@Gerbildral
Copy link

@gbakeman
image

image

@gbakeman
Copy link
Contributor

gbakeman commented Jan 9, 2022

The address of your host is 10.234.1.101, you need to modify that in Diskstation, click OK then Apply. If you still can't connect, try disabling IPv6 on your adapter.

@Gerbildral
Copy link

huh Thats strange i gave my laptop a static ip of 10.234.10.101, but either way it works now. little dumb of me :)

@officedrone
Copy link

I've just recently set up my UPS (APC Back-UPS Pro) to secure my Diskstations. I've set up UPS monitoring with automated shutdown (to safe mode) in my DS220+ as a server and DS213+ as a client. Now I was looking for a way to include my PCs into this and found this project. Great - love it !!

Actually it took my only one hour to set everything up including configuring Windows NUT client. After some trial & error I did some research and found that only

ups works as a parameter for the UPS Name 3493 as NUT Port, upsmon as Login and secret as password are still the default values in DSM6.x

Thanks for this - the lowcase 'ups' as the ups name got me. The exact combination you described works for me.

@Nakuromi
Copy link

Hi,

Indeed for me, winnut works with this parameters :
login : upsmon or monuser (both work for me)
password : secret
Delay >1 (required)
UPS Name : ups (required else error message is ups name not recognized and cannot connect to ups server)

Thanks for this utiliy 😊

@H3KT1C
Copy link

H3KT1C commented Aug 11, 2022 •
edited
Loading

Try changing your polling interval to 1, login to upsmon and password secret

@LUQ94
Copy link

LUQ94 commented Aug 11, 2022

嘗試將您的輪詢間隔更改為1，登錄upsmon和密碼密碼

Thank you for your reply.
I'm success when I re-install my DSM.

@DrRobC
Copy link

DrRobC commented Nov 26, 2022

Thank you so much @gbakeman for all the help. I've just got my WinNUT connected to my APC Backup-UPS 650MI via my Synology DS218+ NAS.

@gbakeman
Copy link
Contributor

gbakeman commented Feb 5, 2023

Just a reminder to everyone to please follow the continuation of WinNUT at https://github.com/nutdotnet/WinNUT-Client. We've had several pre-releases with may bug fixes.

@witzker
Copy link
Author

witzker commented Jul 11, 2023

So next try on Synology 1522+ running
image
on Windows 10 latest update 11.07.23
Version:
image

Settings:

image

Without PW - if I put their "secret" Connection failed!

Connected but no Data!

image

What have I done wrong?

@gbakeman
Copy link
Contributor

gbakeman commented Jul 11, 2023 •
edited
Loading

@witzker Please see my above comment. This repository is no longer under development, and it's moved to the new repository linked above. Please see there for updated WinNUT versions and more info.

@witzker
Copy link
Author

witzker commented Jul 11, 2023

THX, but I'm confused.
Where to find what?

I only found this:
image

What version is the latest?

Where to download?

Sorry, I'm totally new with this stuff, and got it not working last time.

@StatCombo
Copy link

StatCombo commented Jul 11, 2023 via email

@StatCombo
Copy link

StatCombo commented Jul 11, 2023 via email

@StatCombo
Copy link

StatCombo commented Jul 11, 2023 via email

@gbakeman
Copy link
Contributor

@witzker The new repository is at https://github.com/nutdotnet/WinNUT-Client. There you can find newer versions of WinNUT as well as more discussion if there are any issues. Please consider closing this issue so other people know to find to the new repository. Thank you!

@witzker
Copy link
Author

witzker commented Jul 11, 2023 •
edited
Loading

OK THX but now I found this:
https://networkupstools.org/index.html
version 2.8 stable ??
https://networkupstools.org/download.html

Here, as reported above: https://github.com/nutdotnet/WinNUT-Client
I found prerelease
image

image

Can someone explain the difference, pls.

@gbakeman
Copy link
Contributor

Network UPS Tools (NUT for short) is the system that interacts with the UPS and provides the server that WinNUT connects to. WinNUT versions and NUT versions are totally separate and have nothing to do with each other. Hope that clears things up. 😊

@witzker
Copy link
Author

witzker commented Jul 11, 2023

Ok Got it!
THX

@gbakeman
Copy link
Contributor

You're very welcome, I hope that WinNUT continues to be useful for you. And please do consider closing this issue - I truly believe at this point that that will help future users find the right repository.

@witzker witzker closed this as completed Jul 12, 2023
@witzker
Copy link
Author

witzker commented Jul 12, 2023 •
edited
Loading

Many THX here!
Finally, got it working with prerelease version from
new repository at https://github.com/nutdotnet/WinNUT-Client.

Now closed here

@scalpmonkey
Copy link

Hi all, so after the PC is turned OFF, how do you turn it ON after the power is back?

@KarelBrt
Copy link

KarelBrt commented Aug 6, 2023

For me its suddenly working with UPS name "ups" and username "monuser" I'm going to dig more into it. Otherwise a great piece of code. Thank you!
image
image
Windows:
Edition Windows 10 Pro
Version 22H2
Installed on ‎09.‎05.‎2021
OS build 19045.3208
Experience Windows Feature Experience Pack 1000.19041.1000.0

Karel

@Utodev
Copy link

Utodev commented Feb 14, 2024 •
edited
Loading

Hi! I'm just another one trying to configure WinNUT. At the moment I get the "[Id 21: 14/02/2024 19:17:29] Connection to Nut Host nutserver host:3493 Failed: Connection Error", which looks like a problem to connect with the server but:

  • The IP of my the computer I'm trying to connect from is in the "Permited Synology NAS devices" list in my Synology NAS. Also, the service itself is enabled.
  • I can connect via telnet, and then do "LIST VAR ups" and works. I found a page with other commands and they all work. I don't need to user USERNAME or PASSWORD commands.
  • But WinNut doesn't work with same IP address (the one of my NAS), same port, and credentials I found in /etc/ups/upsd.users (in the NAS). Just checked that to be sure it's the correct ones.

I've tried to reboot the NAS, stop and start network server, but no way.

I also set polling interval to 1.

Can someone please put some light on this?

Thanks!

Please see some pictures and logs below:

Configuration in NAS control panel:
image

Configuration in /etc/ups/upsd.users
image

Connection log

14/02/2024 19:30:00 Pid: 21360 Pref_Gui : Show LogFile
14/02/2024 19:30:05 Pid: 21360 WinNUT : Main Gui Has Focus
14/02/2024 19:30:05 Pid: 21360 WinNUT : Update Icon
14/02/2024 19:30:07 Pid: 21360 WinNUT : Force Reconnect from menu
14/02/2024 19:30:07 Pid: 21360 WinNUT : Connect To Nut Server
14/02/2024 19:30:07 Pid: 21360 WinNUT : Error When Connection to Nut Host.
14/02/2024 19:30:07 Pid: 21360 String : New Log to CB_Current Log : Connection to Nut Host nutserver host:3493 Failed: Connection Error
14/02/2024 19:30:09 Pid: 21360 WinNUT : Open Pref Gui From Menu
14/02/2024 19:30:09 Pid: 21360 Pref_Gui : Load Pref Gui
14/02/2024 19:30:09 Pid: 21360 WinNUT : Main Gui Lose Focus
14/02/2024 19:30:09 Pid: 21360 WinNUT : Update Icon
14/02/2024 19:30:09 Pid: 21360 Pref_Gui : Pref Gui Opened.
14/02/2024 19:30:13 Pid: 21360 Pref_Gui : Show LogFile

@gbakeman
Copy link
Contributor

Hi all,

This repository is no longer active, and work has moved to the NUTDotNet project. Please make sure you are running the latest version of WinNUT, then go here to create further discussions.

@Utodev
Copy link

Utodev commented Feb 15, 2024

Thanks for pointing at that. Just for the records, my issue above was solved as soon as I installed latest version.

@gbakeman gbakeman mentioned this issue Jun 29, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Good for newcomers
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests