• 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.

plesk 12.5.3 Firewall rule

N

nantucket

New Pleskian
I am having and issue that when ever I add a custom rule to the firewall such as a rule allow ip xx.xxx.xxx.xxx that when i preview the code there is a deny tcp anywhere , anywhere injected under the rule. This happens to every custom rule i add.

I can confirm this in the firewall-active.sh and on the Iptables. looking in to the plesk database I can see the deny injected after the custom rules but i don't have a clue where or how it is being introduced. This is a fresh install on a new server.
 
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Parallels Plesk Panel 12.5 MU #8 CentOS 6.4 (Final) 64bit



PROBLEM DESCRIPTION
We are having exactly the same issue with the same version of Plesk, adding a "deny" custom rule denies all incoming traffic rather than just the single IP we are trying to block


STEPS TO REPRODUCE
Add or edit a custom rule in the Firewall - allowing or denying a specific IP address


ACTUAL RESULT
Firewall denies all incoming traffic, so nobody can access their websites from any location (blocks DNS as well)


EXPECTED RESULT
Service should continue as normal with just the specified IP address blocked


ANY ADDITIONAL INFORMATION
 
Last edited:
Update : We have logged this issue with Odin and they have confirmed there is a bug in the firewall that creates a full deny when adding single IP addres custom rules. They have managed to replicate this issue on their test server as well as ours.
 
Experienced same issue today on the 12.5 plesk. As soon as I added IP which was allowed to all ports, everything else got banned from server.

Is there any ETA for fix/patch ?
 
You must log in or register to reply here.

Similar threads

A
Question Plesk firewall - CrowdSec iptables interaction
Replies
3
Views
407
andg
A
J
Question Plesk Firewall is blocking requests even with configured rules
Replies
2
Views
1K
Johnny9977
J
A
Resolved Plesk Firewall and Samba
2
Replies
22
Views
3K
Raul A.
R
S
Issue Cant activate the plesk firewall
Replies
5
Views
2K
martinez.marcias@gmai
M
P
Issue plesk firewall 2.1.5-412 still has problems
2
Replies
20
Views
4K
PeterKi
P
Back
Top