• 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

Recent content by Martin Allen

  1. M

    Issue Latest update on "Laravel Toolkit" causes Errors

    I have added to Reports https://talk.plesk.com/threads/laravel-toolkit-generates-laravel-exception-whenever-used.368407/
  2. M

    Forwarded to devs Laravel Toolkit generates Laravel Exception whenever used

    Username: TITLE Laravel Toolkit generates Laravel Exception whenever used PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Laravel Toolkit, Version 1.4.2-221, AlmaLinux 8.7 (Stone Smilodon) PROBLEM DESCRIPTION Whenever an action within the Laravel Toolkit is triggered e.g...
  3. M

    Issue Latest update on "Laravel Toolkit" causes Errors

    Seeing exactly the same issue - we have automated error reporting sending emails to us, and we receive multiple emails detailing this error whenever we navigate to the Laravel extension page.
  4. M

    Issue Amazon S3 Backup - Backup Failed - Harness not finished running Error

    The workaround says to use a directory with no space symbol in the directory name - we already have no space sysmbol in the directory / bucket name (as using Amazon S3)
  5. M

    Issue Amazon S3 Backup - Backup Failed - Harness not finished running Error

    Recieved the following error from one a couple of our servers which are using Amazon S3 Backup Extension Harness not finished running at /usr/local/psa/PMM/agents/shared/Storage/ArchiveStorage.pm line 196. This has occured on 2 seperate servers. On one of the servers all subsequent backups...
  6. M

    Question How to set Nginx try_files directive on a domain?

    We have an issue with a Joomla website that is being hosted on CentOS Linux 7.3.1611 with Plesk Onyx Version 17.5.3 - the site is displaying issues when using nginx as a proxy - when we try tro access the domain https://example.com/administrator we are receiving a nginx 502 Bad Gateway error...
  7. M

    Resolved Unable to access login page - due to failed update?

    After some help from 1&1 and Plesk Technical support the issue has now been resolved - their solution is below
  8. M

    Resolved Unable to access login page - due to failed update?

    We are unable to access the Plesk login page for our server (https://77.68.11.162:8443/) running Plesk Onyx on CentOS 7 eventually receiving a 504 Gateway timeout - this was working correctly up to yesterday. All the Plesk Services are running #systemctl status sw-engine #systemctl status...
  9. M

    Issue Backup error emails after update from 17.0 to 17.5

    Hi we are seeing the same error email being sent each day, but the backup has correctly uploaded to FTP storage, and when viewing the Backup Manager, there is no error logged for the backups. We're using Plesk Onyx Version 17.5.3 Update #25
Back
Top