For our monitoring environment we want to use the pm.status_path, ping.path and ping.response settings for all PHP-FPM pools globally.

At the moment the only way to set these settings is by adding the following in Domain -> PHP Settings -> Additional configuration directives:
[php-fpm-pool-settings]
pm.status_path = /php-fpm-status
ping.path = /php-fpm-ping
ping.response = pong

Unfortunately there is no way to set this globally, not by changing the plan nor by utilizing event handlers (because we're unable to set this through /usr/local/psa/bin/php_settings -u).

I've also been unable to find the template for the PHP-FPM pool settings, so also unable to change this by using a custom template.

Hi,

Please consider add SSH2 extension to PHP default available extensions.

To be able to use FTP over SSH (SFTP) the SSH2 extension must be installed on PHP.

IN SHORT: SFTP (SSH2 EXTENSION) = SECURITY

SFTP means secure file transfer via Secure Shell (or SSH), hence the name SSH File Transfer Protocol (SFTP). The two devices (server and client) communicate via a single channel, that of SSH, in which the remote file management commands are sent and where the file transfer takes place. By default, the only port required for SFTP is 22, the same as SSH.

SFTP implements the same specifications at the cryptographic level supported by SSH, also TLS 1.3.

WHAT ARE FTP AND SFTP:

FTP is the traditional file transfer protocol. It’s a basic way of using the Internet to share files. SFTP (or Secure File Transfer Protocol) is an alternative to FTP that also allows you to transfer files, but adds a layer of security to the process. SFTP uses SSH (or secure shell) encryption to protect data as it’s being transferred. This means data is not exposed to outside entities on the Internet when it is sent to another party.

Businesses often choose SFTP solutions due to enhanced security. However, many others still rely on FTP to facilitate data transfers. To better understand which file sharing option can meet your company’s needs, let’s look at the differences between SFTP vs. FTP. Understanding how these file transfer options differ will help you choose which option is best to transfer your data. There are three key areas in which SFTP vs. FTP differ: encryption, firewalls, and potential vulnerabilities.

ENCRYPTION:

Transferring data is a vital, day-to-day task for many businesses. While some data transfers may not require protection, other files may house sensitive information – information that is too sensitive to fall into the wrong hands. This is why encrypting your data is essential. Encryption scrambles data, making it decipherable only by the sender and the recipient, ensuring that even if a file is intercepted, it won’t be intelligible to any unintended parties.

So, how does encryption impact your choice between SFTP vs. FTP? The traditional file transfer protocol (FTP) is a simple way of transferring data, but it offers nothing in terms of data protection. Files are transferred without encryption, making data readable for anyone who intercepts it. While this is fine if you’re just sending unimportant files, this could lead to major data compromises if you’re sending crucial data.

SFTP, in contrast, offers a secure shell protecting files. Because files are encrypted, you don’t have to worry about data falling into the wrong hands. This is the ideal mode of transfer for any file that you want to protect. SFTP uses an encrypted type of fingerprint technology to first verify host keys before any data transfer has taken place.

In terms of compliance, encryption makes a huge difference. If your organization is subject to compliance standards (including, but not limited to, the ones listed below), you could face serious consequences if you fail to encrypt data:

HIPAA
ITAR
PCI-DSS
SOX
GLBA

Encryption isn’t just a feature offered by SFTP that’s nice to have. It’s an essential step you should take to protect your data. If you fail to comply with these standards, your business could be subject to some serious fines.

FIREWALLS:

Another way in which FTP and SFTP differ is how channels are used. When you send files via FTP, this protocol needs to open multiple channels in order to complete the transfer. While the client and software negotiate these channels automatically, the client-side firewalls need to open multiple ports. Opening multiple channels can also open the client’s firewalls to vulnerability.

SFTP presents a more secure process for the client-side firewall. Only port 22 will need to be open to send and receive data. This simplifies firewall configurations and is a better choice in terms of file sharing security.

VULNERABILITIES:

In addition to encryption and firewalls, SFTP beats FTP in terms of potential vulnerabilities, too. Any vulnerability can potentially be exploited and turned into a data breach. When it comes to inherent vulnerabilities in the file transfer process, FTP has a number of prominent ones.

The first vulnerability is that FTP is prone to human error. Sending a file to the wrong recipient or sending the wrong file altogether can lead to some serious problems for your company. With a greater level of security provided by SFTP, you can minimize the potential for human error. You can also take steps to promote a culture of security awareness within your business to reduce the potential for human error.

Intercepting data is simple with FTP, too. All it takes is the right tools and a little bit of knowledge to take advantage of these vulnerabilities. Even the most amateur hackers can intercept an FTP transfer. Sensitive data is often worth too much to risk a breach.

Again, host keys can present vulnerabilities. Unlike SFTP which uses host keys to verify a recipient's identity before a transfer takes place, FTP does not. This is yet another way FTP transfers are less secure. All it takes is one accidental transfer to a wrong recipient for a file to be compromised.

When it comes to secure data transfers, SFTP is your best option. You can feel confident that encryption measures are up to compliance standards, and you’re avoiding the inherent vulnerabilities of FTP transfers.

Thanks to ftptoday(dot)com for this documents:
- What are FTP and SFTP;
- Encryption;
- Firewalls;
- Vulnerabilities.

Thanks in advance for the support.

Restart interval should be implemented for PHP-FPM services like it is done for Apache.
At the moment, each time when domain's PHP Settings are updated, PHP-FPM service is reloaded which causes the error 503 on websites.

If every person decided to make a small change in php settings daily it would mean 500 x 503 errors for all users daily. We host like 30 active sites and customize a few of them as developers so a few php changes (less than 10) is a daily occurence. Customers never fail to mention this to us because they may be saving products they edited or do mass updates on products which means making some actions that take quite a few seconds.

When their session is killed by the restart, they have to redo the task which can be really annoying.

It must be tremendously annoying for the users of larger hosting providers.