• 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.

Recent content by Burak

  1. B

    PHP 7.0 ->7.0.1 update via MU kills all WP websites

    In my server, I already installed 7.0.2 via yum therefore I see 7.0.2 but Plesk did not officially release a new version (http://docs.plesk.com/release-notes/12.5/change-log/)
  2. B

    PHP 7.0 ->7.0.1 update via MU kills all WP websites

    You should not consider this as a blaming. I am trying to push them to get an action for the fix asap.
  3. B

    PHP 7.0 ->7.0.1 update via MU kills all WP websites

    In my opinion, Plesk should handle every detail for standard users. The users must not be involved with CLI any more. If I have not done the update as @webbing offered, I would not able to solve my issues with PHP 7.0.1. There can be lots of different people with these problems but do not forget...
  4. B

    PHP 7.0 ->7.0.1 update via MU kills all WP websites

    @webbing I did what you said and all my problems have gone! The sites are working super fast!!! Thank you very much ! @trialotto As webbing and I have stated before it was not our mistake nor WP' s. It is the fault of buggy PHP 7.0.1 on Plesk! @IgorG You must make a very quick fix to upgrade...
  5. B

    PHP 7.0 ->7.0.1 update via MU kills all WP websites

    How did you upgrade to 7.0.2? I have very limited knowledge about using yum. Did you remove 7.0.1 completely? Can you write the steps briefly please?
  6. B

    PHP 7.0 ->7.0.1 update via MU kills all WP websites

    @trialotto I can not see psa... [root@server opt]# pwd /opt [root@server opt]# dir drweb kav plesk rh [root@server opt]# cd plesk [root@server plesk]# dir php [root@server plesk]#
  7. B

    Plesk update for PHP 7.0.2

    How can I be informed about this microupdate ?
  8. B

    Plesk update for PHP 7.0.2

    As mentioned here, last PHP version 7.0.1 hit most of the WP users with Fast CGI. It is announced that PHP 7.0.2 is out, when will Plesk team put the new version to the updates. I do not want to install and mix everything up. There are huge performance differences between PHP 5.6 and PHP 7.x...
  9. B

    PHP 7.0 ->7.0.1 update via MU kills all WP websites

    @trialotto Can you please write the uninstall and reinstall command for PHP 7. I have the same problem (@webbing)
  10. B

    FASTCGI error after upgrading to PHP 7.0.1 from PHP 7.0.0

    @trialotto OK, just a simple question. Did you ever manage to run 7.0.1 at FASTCGI mode ???
  11. B

    FASTCGI error after upgrading to PHP 7.0.1 from PHP 7.0.0

    I think there are no major problems here...
  12. B

    FASTCGI error after upgrading to PHP 7.0.1 from PHP 7.0.0

    @trialotto Please take into account that there are also simple noWP websites. Even <?php phpinfo(); ?> gives 500 error on these websites while fastcgi is selected at PHP 7.0.1. All the setup was same at 7.0.0 and I have had no problem. I am waiting for PHP update or asking for a way to downgrade...
  13. B

    FASTCGI error after upgrading to PHP 7.0.1 from PHP 7.0.0

    I have both Wordpress sites and Non WP sites on my VDS. They were all running fine with Fastcgi selected in PHP settings page at version 7.0.0. A few days ago, I upgraded my Plesk panel and also PHP version. After the installation, none of my sites run properly. Both WP and other sites began to...
  14. B

    PHP 7.0 ->7.0.1 update via MU kills all WP websites

    I have the same annoying issue. All the WP pages have 500 error. I changed the FASTCGI to the other option in Plesk PHP settings page, then the sites began to respond but if you add / to the end of the address, 500 error still splashes. There was no problem at 7.0.0, I searched lots of threads...
See more
Back
Top