Where does it say that? I understand the article as if it was consisting of three parts: the first "For Plesk 17.0 and higher", the second "For Plesk 12.5 and below" and the third, common to both Plesk 17.0 and up and Plesk 12.5 and below (beginning with "To redirect HTTP and HTTPS...
@Ales, thanks for offering a solution for this issue. I think I can see where this is coming from and how it can perhaps be adjusted but I've sent you a PM to verify.
Just to make something clear, we aren't "hiding" anything from our customers. They are fully aware that they are being hosted on...
What you are saying is simply incorrect. Factually incorrect. Red Hat Enterprise Linux PHP 5.3.16-xx.el7 is fully supported at the moment, and will continue to be for a long time.
Red Hat - Backporting Security Fixes
Red Hat - Red Hat Enterprise Linux Life Cycle
Once Red Hat 8 comes out, and...
I'd like to discuss this before perhaps reporting it as a bug.
For example, on a fully updated CentOS 7 system:
# php -v
PHP 5.4.16 (cli) (built: Oct 30 2018 19:30:51)
# rpm -q php
php-5.4.16-46.el7.x86_64
Note above, this is not a vanilla PHP 5.4.16, this is Red Hat's 5.4.16-46.el7 (rebuilt...
No IPv6 on this server, correct.
The hostname of the physical host is different than the hostname of the Plesk VM, but that's to be expected. It would make no sense to have same hostnames on what are basically two different servers (albeit one of them is virtualized).
PTRs are set, A records...
Thanks for helping!
Well, everything looks right to me (redacted of course, just to mention so that someone won't think otherwise, hah):
# hostname -f
server.example.com
# hostname -d
example.com
# hostname -a
server
# grep hosts /etc/nsswitch.conf
hosts: files dns
# cat /etc/hosts...
Hi everybody!
I'm configuring a new Plesk 17.8 server on CentOS 7 and need some assistance.
Let's say there is one hosted domain on the server, example2.com. The server has a FQDN hostname server.example.com and is secured with a Let's Encrypt certificate, set to be used for the Plesk...