Search results

Not very useful and will most likely never be supported by Plesk, as this is not a solution that would work in a broad environment. what about users that use Apache2 only, without having Nginx installed? or users with Litespeed? or users that wanna block FTP or Email access?

You can use this as a blueprint: # list existing block devices fdisk -l --> /dev/vdb # partition the new block device fdisk /dev/vdb n p <enter> <enter> w # format the new partition mkfs.ext4 /dev/vdb1 # disable automatic fs-check every X days/mounts tune2fs -c0...

It may help if you manually remove the expired "DST Root CA X3" root certificate from the files /etc/ssl/certs/ca-bundle.crt and /etc/ssl/certs/ca-bundle.trust.crt You can open these files in your editor and search for it. (either it's name or this string...

@Monty I really don't get these LetsEncrypt guys... They insist on keeping the old chain alive and you can read statements like these from many involved people: But, but, but.....I mean, the old chain and root expired two days ago, so these certificates are no longer valid on the old Android...

remove the following lines/certificate (should be on the bottom) from within the file /etc/postfix/postfix.pem and restart your postfix -----BEGIN CERTIFICATE----- MIIFYDCCBEigAwIBAgIQQAF3ITfU6UK47naqPGQKtzANBgkqhkiG9w0BAQsFADA/ MSQwIgYDVQQKExtEaWdpdGFsIFNpZ25hdHVyZSBUcnVzdCBDby4xFzAVBgNVBAMT...

Addendum, yes on brand new servers you don't need a manual workaround, because OpenSSL has some built-it filter that explicitly masks the offending LetsEncrypt chain certificate if it encounters it. I did not read into the details on the OpenSSL Dev List, but there may even be some...

Guys, just be aware that even newly issued LetsEncrypt certificates are still dual/cross-signed with the old and now expired R3 certificate and a properly configured server will send this expired intermediate to the client. (alongside the domain certificate and the proper/new intermediate )...

Linux does not (always) automatically detect size changes on the virtual disk, nor does it resize the partition. For the first step to happen, you need to either reboot the server, or execute "echo 1 > /sys/class/scsi_device/x:x:x:x/device/rescan" for the appropriate device on the command line...

What you are looking for can be found/configured on "General Settings" --> "Customize Plesk URL" Here you need to set it to "No custom URLs. Only https://<server-IP-or-hostname>:8443" After that, requests to the IP address will no long show the login page.

We've had a similar (because you did not provide any details, I can only guess though) problem and the complete error message from the "failed" backup was: WARNING: (Database object 'mydomain_wordpressdb') Unable to make database dump. Error: Failed to exec mysqldump: Exit code: 3: mysqldump...

TSL/SSL version and ciphers are per IP/PORT combination. So you could use different settings for domains/virtual-hosts on different ip addresses and/or ports. Of course, the later is quite moot, as in general you are required to use port 443 anyhow. But if you have multiple ip addresses, then...

This cannot be done You ask why? because TLS version are determined between client and server, before the connection reaches the webserver. If you use different IP addresses for each domain/virtual-host, then you could do that, see also https://support.f5.com/csp/article/K84508595

You may also wanna check if PHP 7.2 is enabled at Tools & Settings -> General Settings -> PHP Settings

Just let SSH run on port 22 and your custom port xxxx Then firewall port 22 so it's only available from localhost and you are fine

Well, imagick does know multithreading (since v3.2) and you can change those limits. (PHP: Imagick::setResourceLimit - Manual) It's reasonable to assume that somehow the jpg conversion does only work singlethreaded while png does use more/many threads. (maybe more than two, but your server does...

As far as I know, this max_execution_time value is computation time and if your task runs multithreaded on say two CPU cores, you can get the behavior you are seeing. The same thing can happen the other way around, when PHP scripts run way longer than this max_execution_time. This is because...

Shopware is currently NOT compatible* with all the latest releases of: MariaDB 10.3, MariaDB 10.4, MariaDB 10.5, MySQL 8.0 (* due to some dumb table create statements in the installer) So, a simple downgrade to MariaDB 10.3 will not help here, as you most likely get v10.3.29 that way. It's...

better fix or update your software, in order to be compliant to newer MariaDB versions (possibly newer MySQL is also affected) see here: Workaround for MariaDB >= 10.2.7 compatibility by samuelvogel · Pull Request #1396 · shopware/shopware

It's not a security risk, because this root user does use socket based auth, instead of a password - heck it's considered to be even more secure than using a password after all. This behavior is also the default for any Debian 9 or 10 you install MariaDB on, regardless of Plesk or not. It's...

just "pdnsutil delete-zone blaablaa.com" on the secondary(s) to delete/purge the zone After that the secondary(s) will accept this zone again from any "master"