• 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!
  • 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 About specifying fastcgi_pass in Plesk

Zoo3

Regular Pleskian
I wondered when I looked into Plesk's nginx.conf file.

Code:
/etc/nginx/plesk.conf.d/vhosts/hostname.com.conf
fastcgi_pass "unix:///var/www/vhosts/system/SUB-DOMAIN/php-fpm.sock";

As described above, in fastcgi_pass, slashes are input consecutively three times like "unix:///var/".
Please tell me the meaning of three consecutive slashes. Is there any difference from the single slash case?
 
It's like `http://`, but `unix://`.
The third slash is the root of the path `/var/www/vhosts/system/SUB-DOMAIN/php-fpm.sock`
 
Does this specification affect performance? This specification looks like Plesk only.
For example, "vi /var/text.txt" and "vi ///var/text.txt" will edit the same file.

In the html source, is it treated to indicate the target with either http or https?
When there is a possibility of making http connection and https connection in the same domain, it may be written like "//img/src/sample.jpg". Is this the same thing?
 
Does this specification affect performance?
No. It is just specification, an indication of how to exchange information. Another example file:///usr/share/doc/packet/index.html
In our case, it is a unix socket but not the file.
 
Excuse me, I can not understand anything. Is this a specification method that only Plesk is unique, and does not need to know the meaning?
 
Back
Top