• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Search results

  1. G

    Issue error_page in additional nginx directives

    That worked - it was correctly displaying the nofound error doc. But it broke the HTML pages - they were downloaded as files in the browser instead of being displayed. Apparently this is a known issue reported at "Custom error documents" not working when PHP run as a "FPM application" but the...
  2. G

    "Custom error documents" not working when PHP run as a "FPM application"

    I'm having the same issue. Is there any update on PHP-21577?
  3. G

    Issue error_page in additional nginx directives

    I've discovered that if I go to a non-existent page in the root (e.g. www.domain.com/noexist.php) then it delivers a basic "file not found" message. But if I go to a non-existent page in a sub-folder (e.g. www.domain.com/xyz/noexist.php) then it correctly delivers my nice /notfound.php page...
  4. G

    Issue error_page in additional nginx directives

    However, the problem with using the error_docs directory is that it looks like I'm restricted to html files. I would like to have a PHP page displayed so it can include some other files too.
  5. G

    Issue error_page in additional nginx directives

    The fully qualified URL didn't make any difference. I haven't put any of my own .htaccess files on the server if that's what you mean in your second point. I will look at the error documents directory method now.
  6. G

    Issue error_page in additional nginx directives

    It is already set to "FPM Application served by Apache"
  7. G

    Issue error_page in additional nginx directives

    I can't seem to get the error_page directive working in nginx. I have the following directive in the Apache settings which works fine when I go to a non-existent page/folder on the website: ErrorDocument 404 /notfound.php But if I try to go to a non-existent page with a .php extension then...
  8. G

    Plesk 11.5 is very close to release. Last chance for your feedback

    But what about those of us that are not early adopters? When will a stable production release be available?
  9. G

    Plesk 11.5 is very close to release. Last chance for your feedback

    I'd also like to know when 11.5.30 will be released for production use. The last I heard was "mid June".
  10. G

    Plesk 11.5 Preview

    I also saw it in the updater, but now it doesn't seem to be there. Any update on this?
  11. G

    Plesk 11.5 Preview

    Any date for production release of 11.5 yet?
  12. G

    Plesk 11.5 Preview

    OK, thank you.
  13. G

    Plesk 11.5 Preview

    Oh, I didn't realise it was still in preview stage. I need to install on a production server - any idea when it will be officially released for production use?
  14. G

    Plesk 11.5 Preview

    Should Plesk automatically update itself to 11.5.23? My Plesk did an update this morning, but it is still at version 11.0.9. When I go directly to the installer, the "install or upgrade product" is greyed out. What do I have to do to upgrade to this new version?
  15. G

    Incorrect name of CNAME record.

    But it's 11.1 that I need to solve this problem, that's why I'm confused when it seems Parallels are already working on 11.5 but I can't seem to install 11.1 yet.
  16. G

    Plesk 11.5 Preview

    When is 11.1 likely to be released for production use?
  17. G

    Incorrect name of CNAME record.

    Fantastic! But I can't seem to upgrade to this version - is this because it's still a preview version? If so, when is is likely to be be released? I see that there are preview versions as high as 11.5 so not sure if I'm missing something.
  18. G

    Incorrect name of CNAME record.

    Any response to the question above? Is it likely to be implemented?
  19. G

    Incorrect name of CNAME record.

    So are you able to provide any indication of if/when the feature request would be implemented? The shell script sounds like a good workaround in the meantime.
  20. G

    Incorrect name of CNAME record.

    OK, so are you saying that no change will be implemented to allow underscores in CNAME? We're trying to follow Amazon's instructions for SES which requires this.
Back
Top