MXS

Members
  • Posts

    3
  • Joined

  • Last visited

Posts posted by MXS

  1. 21 minutes ago, HAMANY said:

    وعليكم السلام ورحمة الله

     

     OpenVPN يغنيك عن WireGuard

    https://unraid.net/blog/wireguard-on-unraid

     

    TeamViewer عليه برنامج Windows 10 VM بالنسبة لي عندي

    يسمح لي ادخل عليه من برع

    توني ادري عن WireGuard 

    شكرا لك

    احتاجه انا عشان اتصل بالسيرفر من اي جهاز 

     

  2. السلام عليكم .

    هل يوجد طريقة للاتصال بالسيرفر من خارج الشبكة ؟

    مثلا احتاج اغير اعدادات أو اعيد تشغيل السيرفر وأنا خارج المنزل .

    حاولت استخدم طريقة 

    openvpn 

    بس الموقع الخاص فيهم محجوب في منطقتي فما أقدر اضبط الاعدادات .

     

    اذا في حل اتمنى المساعدة

  3. On 10/19/2020 at 4:48 PM, Gnomuz said:

    Hi all,

     

    I wanted to report an issue I have with my brand new APC UPS SMC1000IC (tower model) on my DIY Unraid server (6.9.0 beta 30).

     

    I first updated the UPS to the latest firmware (v 04.1) and enabled ModBus communication protocol via the LCD display. It is disabled by default, even though the operation manual states the contrary ...

    After setting up apcupsd accordingly (UPS cable USB, UPS type ModBus), I plugged the UPS in the server (USB-A to USB-A), and all information were properly populated, especially the nominal power and load percent. So far, it was plug and play, what a good surprise after the various posts I had read in this forum !

     

    But, there's a but, as you may have guessed ... After a reboot, all info were wrong, except for "runtime left" : a fully charged battery was reported as 6% charged, no nominal power nor load percent, and many other tags were absent or totally out of range, including an output voltage of 400+ volts ...

     

    After many attempts stopping and starting the daemon, with the UPS plugged or unplugged, I finally reached a stable behaviour :

    - when the server boots with the UPS plugged in, the daemon gets fanciful information, and the workaround is to unplug the UPS, restart the daemon, plug the UPS back, and everything is back to normal

    - when the server boots with the UPS unplugged, and I plug it after the boot process is over, communication with the UPS is established, and all information are correct at first sight

     

    So, I highly suspect the apcupsd dameon establishes the communication "a bit" too early, at a stage where the USB "stack" on my server is not totally ready (sorry for the improper words, I'm not an Unraid/Linux expert...). To try and sort it out, I thought that delaying the launch of the apcupsd plugin / daemon might be a solution, but I didn't find any setting or thread on this forum to do so.

     

    Thanks in advance for your thoughts and help on this issue.

     

    i have the same issue , thank you for the solution :) .

    i hope they fixit .

    my UPS is SMT1500