• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Search results

  1. Hangover2

    Resolved Smart static files processing is only working for lowercase file extensions

    Maybe as a little addition: the location directive does not change the filename that will be processed. So it doesn't matter what file system is used. Right now try_files is not even called because of the strict regular expression for capital letters in the extension part that forbids any match...
  2. Hangover2

    Resolved Smart static files processing is only working for lowercase file extensions

    I think there is a misunderstanding of the problem. Files like: - MyStaticFileWithUppercaseLetters.txt are working already with the current location rule Only files with uppercase letters in the extension are handed over to Apache: - MyStaticFileWithUppercaseLetters_InTheExtension.TxT If you...
  3. Hangover2

    Input Plesk Obsidian 18.0.59 - stable enough for live deployment?

    Hello @Kaspar , thanks for you annotations. The problem with the "bug free updates" we also see since over one year. In the past we did update our servers immediately - we did even activate the auto-updates option till we had some serious business incidents with our clients and broken systems or...
  4. Hangover2

    Input Plesk Obsidian 18.0.59 - stable enough for live deployment?

    Hello, I did open this thread to provide and get information, if the current Plesk Obsidian 18.0.59 release is stable enough to deploy it on live systems with hundreds of clients. To make sure everything runs smoothly and risks are minimized we already have a 3-step roll-out plan, when Plesk...
  5. Hangover2

    Resolved Smart static files processing is only working for lowercase file extensions

    Username: TITLE Smart static files processing is only working for lowercase file extensions PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Obsidian 18.0.59 Update #1, Debian 11.9, x86-64, PROBLEM DESCRIPTION The "Smart static files processing" under "Apache & nginx...
  6. Hangover2

    Resolved Protected directory not working for php files

    For all Plesk users that want to roll-out the current release 18.0.59 #1, there is now maybe one more thing to consider. As described in this thread, the password protection for Nginx did not work at all for at least 18.0.58 and 18.0.57. As a side effect e.g. the backends of Shopware 6 systems...
  7. Hangover2

    Resolved Protected directory not working for php files

    Unfortunately the patch doesn't work out of the box. For the ones who ended up here asking why: you will need to manually regenerate the nginx.conf files for all affected websites in one way or another. If you are not sure how to do, the Plesk repair utility for web is the way to go.
  8. Hangover2

    Resolved Protected directory not working for php files

    @kpushkarev Sure, you have the full insights to the existing logic and which solution fits the best. I did only some blackbox testing to support a fast patch. But the location / I did not touch. It's the same syntax as before / current .59 release. If the location ~* optimization is not...
  9. Hangover2

    Resolved Protected directory not working for php files

    Correct if the password protection is not on the root level as it was in my example. In my posting above I did clarify it. There is always space for optimization^^
  10. Hangover2

    Resolved Protected directory not working for php files

    @kpushkarev Your solution is also one way to go. This part of the config file exists only for the option "Serve static files directly by nginx". I would prefer the @fallback solution with only one location directive, means without the "outer one". Here is the current buggy nginx.conf as...
  11. Hangover2

    Resolved Protected directory not working for php files

    We did investigate the mentioned problems deeper. Actually we are talking about two different problems, depending on your Plesk version in use. We checked some of our "older" Plesk servers with Plesk versions 18.0.58.2 and 18.0.57.3. And one test server with the latest 18.0.59. For versions...
  12. Hangover2

    Forwarded to devs SSL It! breaks renewal and usage of Let's Encrypt wildcard certificates when subdomains are involved

    This bug is super annoying. Since end of December we are forced nearly daily to manually create and clean-up the certificates for our hosting clients on all of our servers as otherwise warning emails are sent to our clients and/or the websites get non accessible after the certificates finally...
  13. Hangover2

    Forwarded to devs Migrator fails to migrate password protected directories

    The whole migrator seems not to have a high priority anymore as it has a lot of serious open bugs. We stopped using it whenever possible. We did not have one single migration in the past that was ok out of the box. Data was missing, settings were not transferred, [the list is endless]. I...
  14. Hangover2

    Input Warden Antispam & Virus Protection Extension for Plesk

    This is what we are doing already. But since the latest update, the lowest value in the dropdown we can set is 3 for a mailbox in block mode. That is not enough. So how can I now set a spam level of 0 or 1 or -0.1 for a specific mailbox with spam action = "block"?
  15. Hangover2

    Input Warden Antispam & Virus Protection Extension for Plesk

    @danami Then please integrate a setting to make this feature accessible again if the server admin wants so. We have a lot of users that are using spam levels of 1 or 2 for their mailboxes and they need this values because they are under high loads of incoming spam. Our servers are configured...
  16. Hangover2

    Input Warden Antispam & Virus Protection Extension for Plesk

    @danami Our clients like to set their own spam levels. Here are the values for one of our smaller servers with 150 mailboxes: SELECT DISTINCT(`spam_tag2_level`) FROM `policy`; 1 null -0.1 7.5 2 3 0.9 -2 0 5 -1 2.5 3.5 5.5 We got already the first support tickets asking why this feature is not...
  17. Hangover2

    Input Warden Antispam & Virus Protection Extension for Plesk

    @danami Since the latest release we cannot set our own individual "Spam level" and "Spam kill level" anymore. Only the default values from the dropdowns can be chosen. Please revert this change and make the input fields editable again. Right now we can only make our own settings by editing...
  18. Hangover2

    Forwarded to devs SSL It! breaks renewal and usage of Let's Encrypt wildcard certificates when subdomains are involved

    @Peter Debik The affected servers have reseller licenses without direct support by Plesk. Maybe @Bobbbb has a proper license to open a ticket.
  19. Hangover2

    Forwarded to devs SSL It! breaks renewal and usage of Let's Encrypt wildcard certificates when subdomains are involved

    Username: TITLE SSL It! breaks renewal and usage of Let's Encrypt wildcard certificates when subdomains are involved PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Obsidian 18.0.57 Update #5, Debian 10.13, x86-64, SSL It! 1.14.5-1856 PROBLEM DESCRIPTION Since mid of...
  20. Hangover2

    Resolved Dist-Uprade Debian 11 to 12

    @kpushkarev Thanks for clearance. We did already use just "mariadb-server" as default value for our external sources. If other Plesk users are also using MariaDB repositories from the MariaDB Foundation this is the way to go (+ update /etc/apt/sources.list.d/mariadb.list before to bookworm).
Back
Top