Facebook
Twitter-
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.
Question How to make plesk use Python 3 for fail2ban?
ChristophRo
Regular Pleskian
fail2ban/fail2ban is where you need to deposit that request. (Plesk does not write this piece of software)
But according to Migrate to python3 · Issue #2690 · fail2ban/fail2ban it's not planned to migrate fail2ban to python3 anyway, at least not in the foreseeable future
But according to Migrate to python3 · Issue #2690 · fail2ban/fail2ban it's not planned to migrate fail2ban to python3 anyway, at least not in the foreseeable future
That's just not true.
As seen in the screenshots, it's running on Python 3.9.1;
The question was not "Does it work with Python 3?", but "How do I tell Plesk that it should not use a Python version that is 1 year EOL?" (Title edited to make it fully clear)
ChristophRo
Regular Pleskian
Even if that is the case, you are still in the wrong place here.
The fail2ban package is provided by your OS vendor and if this one does use python2, then you need to talk to CentOS, Ubuntu, Debian or whatever you are using.
If you are bold, you can try to change the shebang line in the file /usr/bin/fail2ban-server yourself (from #!/usr/bin/python2 to #!/usr/bin/python3) and see what happens
Of course this will be without any support from either Plesk nor your OS vendor and whenever there will be an update for the fail2ban package, this file and with it the shebang line, will get overwritten.
The fail2ban package is provided by your OS vendor and if this one does use python2, then you need to talk to CentOS, Ubuntu, Debian or whatever you are using.
If you are bold, you can try to change the shebang line in the file /usr/bin/fail2ban-server yourself (from #!/usr/bin/python2 to #!/usr/bin/python3) and see what happens
Of course this will be without any support from either Plesk nor your OS vendor and whenever there will be an update for the fail2ban package, this file and with it the shebang line, will get overwritten.
