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

Search results

  1. M

    Resolved Host error after update to 18.0.72

    The issue has been resolved after Plesk Obsidian 18.0.72 Update 2 :)
  2. M

    Resolved Host error after update to 18.0.72

    Affirmative, this fixes the issue. If you keep the website as default website, and turn nginx proxy mode off, it also works. This was my previous workaround. Now I have turned nginx's proxy mode back on, and set the default domain to none and it works.
  3. M

    Resolved Host error after update to 18.0.72

    Confirmed, affected domain is set as default (I only have domain, and an alias)
  4. M

    Resolved Host error after update to 18.0.72

    Yes it is. Everything worked perfectly before the latest Plesk Obsidian update. I think it has something to do with Nginx reverse proxy.
  5. M

    Resolved Host error after update to 18.0.72

    Hi all, After the upgrade to 18.0.72 I'm encountering the following problem: My laravel application expects a certain domain to verify if it's routes need to pass to the first or second website. This worked like a charm after the update. After the update, I get a "default-xxxxx" host...
Back
Top