henrygd
[Feature]: 什么时候支持win系统？？会支持win系统吗?
Describe the feature you would like to see
什么时候支持win系统？？包括win server win10 win11等 尤其是amd的apu核显监控 我使用其他人的办法安装成功，但是hub显示agent离线
Describe how you would like to see this feature implemented
支持win和apu核显监控
We have a Scoop package: https://beszel.dev/zh/guide/agent-installation#scoop-windows
There's also a WinGet package but I haven't added it to our service installation script yet.
AMD APUs and GPUs should work fine on Linux with rocm-smi but I'm not sure about Windows yet. We may need to add support for amd-smi first.
We have a Scoop package: https://beszel.dev/zh/guide/agent-installation#scoop-windows
There's also a WinGet package but I haven't added it to our service installation script yet.
AMD APUs and GPUs should work fine on Linux with
rocm-smibut I'm not sure about Windows yet. We may need to add support foramd-smifirst.
我安装成功了，设置了密钥，但是hub显示离线，win查看45876端口是被监听的
We have a Scoop package: https://beszel.dev/zh/guide/agent-installation#scoop-windows
There's also a WinGet package but I haven't added it to our service installation script yet.
AMD APUs and GPUs should work fine on Linux with
rocm-smibut I'm not sure about Windows yet. We may need to add support foramd-smifirst.
是不是必须agent所在的win要能访问到我的hub所在的机器？？？
We have a Scoop package: https://beszel.dev/zh/guide/agent-installation#scoop-windows
There's also a WinGet package but I haven't added it to our service installation script yet.
AMD APUs and GPUs should work fine on Linux with
rocm-smibut I'm not sure about Windows yet. We may need to add support foramd-smifirst.
我测了了3台win机器，不同区域的，没有一台是成功的
是不是必须agent所在的win要能访问到我的hub所在的机器？？？
No, but the hub has to have a route to the agent system. See here for troubleshooting: https://beszel.dev/zh/guide/common-issues#%E4%BB%A3%E7%90%86%E7%A8%8B%E5%BA%8F%E6%9C%AA%E8%BF%9E%E6%8E%A5
我测了了3台win机器，不同区域的，没有一台是成功的
I am happy to fix any issues with the install script, but I need more information. What did it output? What was the error?
You can see more information about this here: https://github.com/henrygd/beszel/discussions/739
Can you provide more details on why you think it's too complicated? We have winget and scoop packages now. You should be able to just copy from the 'Add System' dialog and paste into powershell.
WinGet is installed by default on Windows 11 and updated Windows 10.
https://beszel.dev/zh/guide/agent-installation#winget-scoop-windows
现在部署已经足够简单了，指南都提供了一键脚本。 我此前通过nssm创建服务直接运行二进制文件，设置的时候的确踩过坑，key似乎需要作为环境变量而不是参数传入。
现在部署已经足够简单了，指南都提供了一键脚本。 我此前通过nssm创建服务直接运行二进制文件，设置的时候的确踩过坑，key似乎需要作为环境变量而不是参数传入。
环境变量的名称就填key??
是不是必须agent所在的win要能访问到我的hub所在的机器？？？
No, but the hub has to have a route to the agent system. See here for troubleshooting: https://beszel.dev/zh/guide/common-issues#%E4%BB%A3%E7%90%86%E7%A8%8B%E5%BA%8F%E6%9C%AA%E8%BF%9E%E6%8E%A5
我测了了3台win机器，不同区域的，没有一台是成功的
I am happy to fix any issues with the install script, but I need more information. What did it output? What was the error?
You can see more information about this here: #739
no error , just hub can't connect my win agent
Have you tried running the install command available in the hub?
你们的逻辑不对，其他类似的软件，都是只要agent能访问hub就行，而你们相反，必须要hub可以访问agent才行，我通过frp穿透端口，让hub可以访问agent就行了 什么时候添加win的agent的gpu监控？？win上可以用系统提供的api查看gpu的温度功率显存占用率
I'm not sure I understand everything you're saying after translating.
Agent to hub communication is coming in the near future.
Nvidia GPUs should work fine on Windows. AMD may have an issue because rocm-smi is being deprecated and I haven't had time to look into amd-smi.
What Windows system API are you referring to that can provide all those metrics for GPUs? If this exists then it would be very useful. Can you provide further details?
您是否尝试过运行中心中提供的 install 命令？
你们的逻辑不对，其他类似的软件，都是只要agent能访问hub就行，而你们相反，必须要hub可以访问agent才行，我通过frp穿透端口，让hub可以访问agent就行了 什么时候添加win的agent的gpu监控？？win上可以用系统提供的api查看gpu的温度功率显存占用率
我觉得这样也是有好处的， 方便hub在内网环境中部署， 同时环境也更安全。
@yunjisuan-209 Realistically I'm not sure I'll be able to do that. At least any time soon. You can try downloading the exe and setting it up manually: https://github.com/henrygd/beszel/releases/latest
The script sets it up with NSSM to run in the background. You can set the env vars in the NSSM service configuration: https://nssm.cc/usage