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

Resolved Plesk firewall (remote redis)

Γιώργος

New Pleskian
Good evening fellas,

I have the following problem, I am trying to expose a redis server to the public in order to allow remote connections from other hosts, and I do manage to succeed this using Plesk firewall

1) Plesk Settings
2) Firewall
3) Add Custom Rule
4) Allow incoming at specific host & port
5) apply.

Then I am able to connect remotely from the given host at the specific host.

the problem is that I cannot do anything else than that.

all ports are blocked through the outside world.
Ping service is blocked. I cannot ping TO the server, or ping FROM the webserver, dns won't resolve,
mySQL won't resolve and in general all comunications goes down. All but the redis port into the given host :)

Any ideas why this might be happening ?
 
You do not need to explicitly open connections via the Plesk Firewall extensions, the Redis instance should already be open to remote connections.

In short, it seems to be the case that you can simply solve the problem by removing your custom firewall rule.

Hope the above helps......
 
This might help.

But want I want is:
all traffic to be allowed exactly as it was before.
All traffic to be allowed on port 6379 on a given IP address / subnet
All traffic to be blocked on port 6379


I Also have custom rule on plesk firewall for allowing incoming traffic on some ports on 50xxx

and ofcourse, disabling firewall makes it all works, but I don't want under any circumstances to disable plesk firewall.
 
Back
Top