• 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
  • Please beaware of a breaking change in the REST API on the next Plesk release (18.0.62).
    Starting from Plesk Obsidian 18.0.62, requests to REST API containing the Content-Type header with a media-type directive other than “application/json” will result in the HTTP “415 Unsupported Media Type” client error response code. Read more here

Recent content by Notanumber

  1. N

    Issue Laravel 9 not recognised by the Toolkit extension

    Did not know: We don't work for Plesk or anything like that. Thanks for responding.
  2. N

    Issue Laravel 9 not recognised by the Toolkit extension

    But it doesn't. A scan results in 0 applications to be attached. reproducing just bij clicking the scan button.
  3. N

    Issue Laravel 9 not recognised by the Toolkit extension

    Final post before bug reporting. This is the folder structure. The structure is setup like required, de public directory is set as root. Artisan is present. Repair fs has been run as reported.
  4. N

    Issue Laravel 9 not recognised by the Toolkit extension

    Due to the lack of respons i can asume that this is een issue
  5. N

    Issue Laravel 9 not recognised by the Toolkit extension

    It is exactly setup as requested in:
  6. N

    Issue Laravel 9 not recognised by the Toolkit extension

    Run the permission check, it fixed the permission but did not solve the problem for me also.
  7. N

    Issue Laravel 9 not recognised by the Toolkit extension

    Hello, i can confirm this issue. Laravel is setup in de proper folders. Artisan is present in the parent directory, public is the root of the site (subdirectory of the parent).
Back
Top