Search results

php5.3 is a bitch to compile on Ubuntu 18.04, due to SSL incompatibilities. requires manual patching of source files and even then it's a pita to do, at least it you need modules like curl or imap that require SSL support. we have php5.3 packages built and running for Debian9 servers, but with...

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

Many thanks for v2.06 and adding the possibility for mail users to change their own settings. That was (for us) the only drawback when using Warden instead of the vanilla Plesk solution or their premium antispam/virus extension.

Most likely the low TTFB on CPanel simply comes from disabled output buffering On Plesk this is enabled (at least if you let Apache2 handle the php-fpm stuff and use nginx in proxy mode) as the proxy_fcgi module will buffer everything from the php-fpm process till the script has completed...

yeah, we see this problem as well seems to happen for databases that are (correctly) assigned to a subdomain of a subscription

Yeah, PHP 8.0 may sound nice and shiny, but so many people will be disappointed pretty fast, when they realize that literally no existing PHP based project/application will run with it yet. (and may not do so for a long time forward)

I'd like to have a toggle for that. But just a heads up for all that vote on this feature - the removing of digest-md5 on running systems will break many existing account configurations in certain Outlook versions, Mac Mail and other programs and affected customers will need to re-setup their...

I beg to differ here Email passwords are stored in a reversible manner and you can see them in plain text via the CLI command /usr/local/psa/admin/sbin/mail_auth_view This is done, because Plesk still does need/want to support CRAM-MD5 authentication for mail clients. (POP/IMAP/SMTP)

It's not possible and not supported. Plesk requires root permissions for so many things it does (think of installing/removing software packages, creating/deleting system users, configure/restart services and much more) that it's not worth to hassle around with sudo or other workarounds to make...

We are using Resellers for quite some years now (so Onyx and Obsidian) and grant them the permissions to allow chrooted SSH access. And so far we never had a problem with that, i.e. they were never able to configure a non chrooted access. (and that is also consistent with our internal testing)...

This is something that will never work anyway, as a wildcard ssl certificate does only cover one level of subdomains. So let's say you have a wildcard cert *.mydomain.com, then this this will be valid for something like aaa.mydomain.com or bbb.mydomain.com, but not ccc.aaa.mydomain.com

Dave is correct Your server will offer StartTLS on port 25 and 587 for SMTP, 110 for POP3 and 143 for IMAP On the ports 465, 993 and 995 however, you are forced to use an SSL/TLS connection before issuing any commands.

Just checked the logfiles on our Debian9 server as well, and here we see the duplicate entries also. And this for sure has nothing to do with a dist-upgrade, as this server was Debian9 from the get-go and this problem must be relatively new. (because I remember/know this was not always the case)...

nginx does not support this on a global/server level and you have to add this configuration for every virtualhost. So what you could do is: 1) create a file named /etc/nginx/baduagent.conf and put in what IgorG linked 2) create a custom template...

Yeah, the Docker daemon acts as a network device (i.e. Router) and the containers get/learn their IPv6 address via IPv6 autoconfiguration from this daemon. Just similar like you would configure a DHCP service on the Docker daemon (or Router) for IPv4 and the clients/container then get their IPv4...

You cannot configure IPv6 ranges on a server, that is not something that is supposed to work. And Plesk really works and behaves the same way with IPv6 as every other software does. You cannot add the IPv6 Adresse 2a01:4f9:2b:f810:: with Subnet Mask /64 to your server, as this is the "network"...

You did not add an IPv6 range to the server, but the single IPv6 address 2a01:4f9:2b:f810:0:0:0:1 And the same way an IPv4 subnet mask of 255.255.255.0 does not mean you added 256 IP addresses to your server, a /64 subnet mask for IPv6 does not do that.

What does going offline mean exactly? Just not processing requests anymore or going into the "stopped" state? If it's the latter you may wanna check the Windows eventlog and see if this behavior is possibly triggered by the rapid fail protection of IIS. In that case you could either increase...

Reseller Management is so much more than being able creating some pseudo personal name server for a reseller. - Would I love to see a custom/personal DNS template for a reseller? For sure - Would I love to see custom (names for) name server for a reseller? well, I don't need it and would make...

Such an option does not exist in Plesk and ist most likely never to come. (one of then reasons is that such a thing does not follow RFC guidelines for DNS configurations, though technically it does not matter)