• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Firewall bug (int16)

shall

Regular Pleskian
Attempting to set an allow rule in the firewall for ports over 35000 results in the following error (that also prevents me from ever managing the firewall via Plesk again!):

===================================================
winfwmng failed: Value was either too large or too small for an Int16.
---------------------- Debug Info -------------------------------
0: C:\Program Files\SWsoft\Plesk\admin\plib\common_func.php3:151
psaerror(string 'winfwmng failed: Value was either too large or too small for an Int16.')
1: C:\Program Files\SWsoft\Plesk\admin\plib\firewallmng.php:35
firewallmng->_call(string '<command><show><portopenings/><interface guid="{96CF2579-43C1-4A62-89C7-0D984ABB34E2}"/></show></command>')
2: C:\Program Files\SWsoft\Plesk\admin\plib\firewallmng.php:174
firewallmng->get_rules(string '{96CF2579-43C1-4A62-89C7-0D984ABB34E2}')
3: C:\Program Files\SWsoft\Plesk\admin\plib\firewall\RuleList.php:46
RuleList->fetchRuleList()
4: C:\Program Files\SWsoft\Plesk\admin\plib\class.cList.php3:96
cList->fetchList()
5: C:\Program Files\SWsoft\Plesk\admin\plib\class.cList.php3:115
cList->init()
6: C:\Program Files\SWsoft\Plesk\admin\plib\firewall\FirewallInterfaceForm.php:37
FirewallInterfaceForm->assign(array, string '')
7: C:\Program Files\SWsoft\Plesk\admin\htdocs\server\firewall_interface.php:104
===================================================

Apparently Parallels isn't aware that using an int16 to manage a range from zero to 64k would require it to be unsigned. This is a BUG and I would really like it to be fixed. Meanwhile, I have to go dig through the PSA database to see if I can access the data so I can gain access to the firewall config in Plesk again. Sigh.
 
Meanwhile, I have to go dig through the PSA database to see if I can access the data so I can gain access to the firewall config in Plesk again. Sigh.

Nothing found in the psa db or the file structure. The firewall settings have to be stored as an XML format in order to return this type of error - but I am not seeing anything edited on the server in the last 24 hours that is related.

Anyone know where the firewall config is stored? The file "winfw.conf.xml" from %PLESK_BIN% looks like it may be the original, but no modified version is found. Heck, even an option to reset the firewall to the original settings (I'll just re-add the dozen mods I've made already) would be fine.
 
This was reviewed by my colo, where they've determined it is indeed a bug in Plesk (they were able to easily recreate the problem). It has been escalated to Plesk. I'll let you know if they fix it or what they've done.
 
Same here.

Just added 15 ports via a range and now get this same error when attempting to access Plesk firewall.

Although ports were successfully created and are operational.

Didn't spot this post, but have sent support request...

Lea
 
Back
Top