• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Search results

  1. N

    Resolved Invalid Time Stamps post 18.0.53 Upgrade

    Username: TITLE Invalid Time Stamps post 18.0.53 Upgrade PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk 18.0.5.3, Ubuntu 22.04 PROBLEM DESCRIPTION After upgrading Ubuntu 22.04 to Plesk 18.0.53 from Plesk 18.0.52 Update #3, domain logs are showing log entries with UTC...
  2. N

    Resolved nginx protocol options redefined

    Those are the errors you need to correct. The result of the nginx-t command is telling you the error, the file where it is located, and the line on which it exists. I'm not going to be able to help you fix the errors, but now you know what to fix.
  3. N

    Issue Failed to connect to the Let's Encrypt server https://acme-v02.api.letsencrypt.org.

    If by chance this is a windows server running Plesk, make sure in your IIS configuration for that domain that the HSTS option is checked. I've seen on a windows server with Plesk, this option become un-sync'd from the HSTS option in Plesk and cause this exact error. If not windows, try toggling...
  4. N

    Resolved nginx protocol options redefined

    the nginx -t command is used to check the validity of the nginx config files prior to restarting nginx. It could be you have a syntax error or a conflict in how your ports are defined somewhere in one of your server directives. You can always login to the system with SSH with a user that has...
  5. N

    Resolved Timestamps in Apache logs and Obsidian 18.0.53

    Additionally, you can add a timezone to the system php.ini for say php8.2-fpm, which by default has no timezone set (and shows UTC from the domains phpinfo page generated from the php settings page), and that does not solve the issue either. After that update, the phpinfo page generated form...
  6. N

    Resolved Timestamps in Apache logs and Obsidian 18.0.53

    Can confirm that as soon as we upgrade any Ubuntu 22.04 or CentOS 7 system from 18.0.52 Update #3 to 18.0.53, the time begins to display as UTC in both domain logs, and on other Plesk GUI screens (like the home page), where the last time checked for update time stamp is shown.
Back
Top