• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Search results

  1. L

    Issue Redirect from example2.com:8443 to FQDN hostname server.example.com:8443 fails

    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...
  2. L

    Issue PHP by OS vendor marked outdated, but it isn't

    @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...
  3. L

    Issue Redirect from example2.com:8443 to FQDN hostname server.example.com:8443 fails

    plesk.conf-orig: server_names_hash_bucket_size 64; server { listen 8443 ssl; listen 8880; listen 127.0.0.1:8880 default_server; include conf.d/*ipv6_ports.inc; ssl_certificate...
  4. L

    Issue PHP by OS vendor marked outdated, but it isn't

    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...
  5. L

    Issue PHP by OS vendor marked outdated, but it isn't

    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...
  6. L

    Question Does running PHP 5 on Plesk Version 17.8.11 Update #50 have security risk?

    Are there any known vanilla PHP 5.6.40 vulnerabilities out there? I know that the official upstream support ended with Dec 31st, 2018.
  7. L

    Issue Redirect from example2.com:8443 to FQDN hostname server.example.com:8443 fails

    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...
  8. L

    Issue Redirect from example2.com:8443 to FQDN hostname server.example.com:8443 fails

    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...
  9. L

    Issue Redirect from example2.com:8443 to FQDN hostname server.example.com:8443 fails

    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...
Back
Top