• 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. S

    Question Plesk Health Monitor is not more in Obsidian?

    Hehe in Onyx i also use "a box with a little heart". But have you read Obsidian documents and Highlights before you upgraded? Obsidian have new thing called "Advanced Monitoring". It does everything Plesk Health Monitor in Onyx did + more + it's nicer and more informative (uses Grafana). Here...
  2. S

    Issue upgrading to obsidian - websites not accessible

    Have you tried to restart your server completely after upgrade? Maybe some service isn't running properly. I've seen few people reporting errors but once server is restarted Obsidian and all websites/subscription start to working properly.
  3. S

    Question Upgrade MariaDB

    Seeing that MariaDB 10.3 works in Onyx even though it's not officially supported - i wonder did any of you guys tried to upgrade MariaDB 10.3 (which is shipped with CentOS 8) to MariaDB 10.4 before Obsidan installation ? I am trying to understand why Obsidian is not supporting 10.4 but 10.3 is...
  4. S

    Resolved Advanced Monitoring graphs seem out of scale after upgrading VPS

    I am guessing here but when working with VPS infrastructure sometimes you need to turn off server completely and then start again - for new additional space to be mounted correctly. I understand from your second screenshot that Plesk detected additional space correctly in Settings but have you...
  5. S

    CentOS 8 support

    Wow you see. That makes it A LOT better for me. Even if you delay CentOS 8 support for a month or two it still better to know this for setting out our plans (instead of - soon). Keep up the good work and good luck with everything.
  6. S

    CentOS 8 support

    I wish there is at least rough estimate on this. Saying to your users "soon" or "just monitor changelog" - is not doing any good. But saying in Q1 od 2020 or Q2 of 2020 would make it far more fair. We have ongoing projects, plans need to be set and so on. I would really like someone give us...
  7. S

    Resolved SNI Enabled but Aliased Domain not in Mail Cert?

    From their FAQ MailEnable 10.20 and Postfix 3.4 support SNI for mail. FAQ for Plesk
  8. S

    Resolved SNI Enabled but Aliased Domain not in Mail Cert?

    But they changed it in Obsidian?! That fact you are seeing his screenshot doesn't convince you? If you don't see same options like GJ Piper then some option may be disabled at your installation. Especially if you run upgrade from Onyx instead of clean install. Check their documents. I can't...
  9. S

    Question Autodiscover

    This is great thank you!
  10. S

    Resolved Let's Encrypt: Domain validation failed, but CAA records are correct

    You should mark it as solved then? Just to keep things clean in the beginning. We all browse eagerly Obsidian forum these days :)
  11. S

    Question Autodiscover

    If "example.com" is working without any error i couldn't care less for "smtp.example.com". IMHO example.com is even more straightforward from the client perspective. He doesn't have to remember all these imap,pop etc things. So if that works without any error then that's fine. But my stand is...
  12. S

    Question Autodiscover

    But that mean you are using your server certificate (top certificate so to speak) - not user domain certificate. That's why you don't have error. This is working same as in Onyx. It's not wrong way of doing it but i would like to use new SNI feature and i want my users can use their domain names...
  13. S

    Kernel warning when cloning a website

    Thank you.
  14. S

    Kernel warning when cloning a website

    Hello. Since i also use CX41 at Hetzner for some of my projects i would like to know to what system they (Hetzner) switched you and from what exactly? From KVM to ? I am sure other will also benefit from your response. IgorG i am using Onyx at CX41 (KVM) on CentOS 7 and it's working perfectly...
  15. S

    Resolved Let's Encrypt SSL issue on shared hosting (when using port 8443).

    Thanks for your valuable input. Greatly appreciated. I am going to stay away from deep digging solutions (solutions you posted initially above). Not because i wouldn't know how to do it (i can easily restore complete server snapshot if i mess something on the server) but because from my...
  16. S

    Resolved Let's Encrypt SSL issue on shared hosting (when using port 8443).

    Btw i am interested to hear your opinion about multidomain Lets Encrypt certificate. What do you think about this? Wouldn't that solve case B issue until Plesk deal with it. So my theory is that when i am creating Let's Encrypt certificate at my Plesk - Tools and Settings, SSL/TLS for securing...
  17. S

    Resolved Let's Encrypt SSL issue on shared hosting (when using port 8443).

    Guys...Monty, Ales and learning curve (haha what a great username) - thank you all. Really valuable info. I just read these articles you linked. Until this is resolved by Plesk itself i guess i'll have to deal it by myself (like you did) I haven't realized Postfix was without SNI until...
  18. S

    Resolved Let's Encrypt SSL issue on shared hosting (when using port 8443).

    No it's not. This issue goes deeper then just not being able to access Plesk user area over their own Lets Encrypt certificate. I mean this goes deeper then not being able to use https://www.domain1.com:8443 even though Lets Encrypt is PROPERLY installed and assigned. Let me give you another...
  19. S

    Resolved Let's Encrypt SSL issue on shared hosting (when using port 8443).

    Thanks for your response. No i don't have separate IP for each domain. But my case isn't exactly rare case right? Many many web hosting services use single IP on multiple domains on shared hosting. And again thanks for your contribution. As i said i see script that you linked is not centos...
  20. S

    Resolved Let's Encrypt SSL issue on shared hosting (when using port 8443).

    Thanks. What are you suggesting that there is a solution to my problem? What do you mean when yo usay "It can be configured which one under "Tools & Settings" -> "SSL/TLS Certificates" -> "Certificate for securing Plesk". can you please clarify? There i can select only one certificate and if i...
Back
Top