• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Recent content by jsnrkd

  1. J

    Resolved Update Error - Release does not have a Release file

    Sorry, what I mean is - Does the extended Ubuntu 18 Plesk support until 2024 assume the machine is also using Expanded Security Maintenance (ESM) for 18.04 LTS provided by Ubuntu Pro? My assumption is yes but I wanted to ask for planning purposes.
  2. J

    Resolved Update Error - Release does not have a Release file

    Thank you, @Peter Debik . Has the recent Plesk extended support announcement been tested with the Ubuntu 18.04 PRO extended support? @Hielko Any anecdotal updates from the Plesk announcement on your install? I'm looking to confirm that Ubuntu Pro 18 will function with the latest Plesk update.
  3. J

    Issue MySQL TLS enabled: The localhost is not compatible with enabling a secure connection.

    Correct except that I do want my 2nd attached remote DB to have TLS enabled. I hope that this config will become available in the future for pre-existing non-HA configs. I'm optimistic because It should be a fairly minor tweak to the new feature to support this setup by excluding the localhost...
  4. J

    Issue MySQL TLS enabled: The localhost is not compatible with enabling a secure connection.

    Okay, that makes sense. The centralized DB announcement says I can't migrate the local PSA databases by converting an existing Plesk installation. So, the solution for me and those who want to use MySQL Secure Connections where the Plesk instance runs on a local PSA DB is to create and migrate...
  5. J

    Issue MySQL TLS enabled: The localhost is not compatible with enabling a secure connection.

    @Kaspar Steps: Following these Securing Connections to a Remote MySQL Database Server : Environment (Both machines same VNET): VM 1 - Ubuntu 18.04.6 LTS - VM 1 Plesk/MySQL 5.7.* (mysql added on localhost to Plesk) VM 2 - Ubuntu 18.04.6 LTS - VM 2 MySQL 5.7.* (this remote mysql instance also...
  6. J

    Issue MySQL TLS enabled: The localhost is not compatible with enabling a secure connection.

    Thank you Peter - however I'm not looking for assistance in the new feature request you created but rather the existing feature that was recently added of MySQL secure connection.
  7. J

    Issue MySQL TLS enabled: The localhost is not compatible with enabling a secure connection.

    Thanks @Peter Debik - I see the issue you raise with that feature request although I don't think that's the setup I'm describing. To clarify my setup: I have an Ubuntu VM (1) hosting Plesk and a localhost MySQL instance. I also have another Ubuntu VM (2) running only MySQL that Plesk is...
  8. J

    Issue MySQL TLS enabled: The localhost is not compatible with enabling a secure connection.

    Hi Peter, I realize you're correct that the localhost MySQL TLS connection is unnecessary that I configured. The error code is interesting that it references the localhost as not compatible with enabling a secure connection though. Do you have any idea what context that localhost error may...
  9. J

    Issue MySQL TLS enabled: The localhost is not compatible with enabling a secure connection.

    Hi, I have enabled the mysql configuration on localhost (127.0.0.1) to require secure connections and verified within mysql /s but still get the fatal error from Plesk when tls.enable =true. : [mysqld] ssl-ca=/etc/mysql/certs/ca-cert.pem ssl-cert=/etc/mysql/certs/server-cert.pem...
  10. J

    Issue MySQL TLS enabled: The localhost is not compatible with enabling a secure connection.

    Thanks Peter - I will work through my.cnf config and report back. In the meantime here is a screenshot of the error. In order to restore Plesk operability, I must set tls.enable to false through plesk conf panel.ini
  11. J

    Issue MySQL TLS enabled: The localhost is not compatible with enabling a secure connection.

    Hi, I'm attempting to enable MySQL secure connection on 18.0.52 but when I edit panel.ini with tls.enable to true Plesk gives the following fatal error "The localhost is not compatible with enabling a secure connection." This plesk instance is connected to a localhost instance and one remote...
See more
Back
Top