• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

Search results

  1. D

    Forwarded to devs Let's Encrypt wildcard cartificates cannot be renewed automatically

    Sorry cepesh, i saw this post too late - i have since removed SSLit completely in the hope renewal would work again today. Unfortunately it seems like it hasnt tried renewing the wildcards today at all, e.g. no error no success. Only non-wildcards have been renewed. Earlier this worked just fine...
  2. D

    Forwarded to devs Let's Encrypt wildcard cartificates cannot be renewed automatically

    Hello cepesh84, i've already done these steps (as mentioned in the OP) several times, the issue persisted through any renewals nontheless. These workarounds / fixes are ineffective, removing the orders will lead to the renewal failing with the same error the next time it's supposed to be renewed...
  3. D

    Issue Let's Encrypt Issues with Renewal

    Thanks, i tried. Given everything implies that this should work and i cannot get it to work on a new Plesk instance either, i have hopes devs might find something.
  4. D

    Resolved Let's Encrypt doesn't work if hosting type Forwarding is selected

    Having the same issue. The old Let's Encrypt certificate can be kept, but no new can be received.
  5. D

    Forwarded to devs Let's Encrypt wildcard cartificates cannot be renewed automatically

    User name: D3nnis3n TITLE Let's Encrypt wildcard cartificates cannot be renewed automatically PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE Plesk Obsidian 18.0.28 Update Nr. 3, Ubuntu 18.04.4 LTS, AMD64 PROBLEM DESCRIPTION When activating the auto-renewal of Let's Encrypt Wildcard...
  6. D

    Issue Let's Encrypt Issues with Renewal

    So, how can i report a bug to Plesk? Typically a staff guy watched the threads and created one on their own, but they didn't this time.
  7. D

    Resolved Backup fails since update to Plesk Obsidian 18.0.26: "Unable to validate the remote backup"

    I did get an error today, but a different one than last time. Activating TLS 1.2 again.
  8. D

    Issue Let's Encrypt Issues with Renewal

    The CLI is broken for me, it yields this no matter what i do.
  9. D

    Issue Let's Encrypt Issues with Renewal

    But the message was totally irrelevant to my issue. That's like when i go to some random thread in the forums and ask "How much does the fish cost, if you wanted to buy one?". I wonder how'd you feel if someone posted that to your thread? I was clearly pointing out a bug in the software as i got...
  10. D

    Issue Let's Encrypt Issues with Renewal

    No, my mind is not ****ing me, see attachment. So, this is a bug. What's gonna be done about it?
  11. D

    Issue Let's Encrypt Issues with Renewal

    If you read my OP again, you will see that i stated that Plesk is controlling my main DNS. Hence your whole post assumed something that is not true. Afaik i read that on a different changelog (one solely for the extension) that seems to be no longer available. It was last year, though. Renewing...
  12. D

    Issue Let's Encrypt Issues with Renewal

    Hello, thanks for your post. That's weird. The changelog of the extension stated some time ago that renewing wildcard certificates automatically is now supported. Wonder when that's going to be fixed, if its a known issue? Sure, it's easier. But i still forget it, lol.
  13. D

    Resolved Backup fails since update to Plesk Obsidian 18.0.26: "Unable to validate the remote backup"

    I've disabled the config option to set to 1.2 and will see if it works for my Hetzner Storage Box this night.
  14. D

    Issue mxtoolbox DKIM: Body Hash Did Not Verify

    Unfortunately "should" often doesn't correspond to "is". Thankfully the issue solved itself over time, though. So probably some caching issue somewhere.
  15. D

    Issue Let's Encrypt Issues with Renewal

    I'm using Let's Encrypt to secure my domains via wildcard certificates. It's set to renew the first day of every month, no matter how old the certificate is. Unfortunately that hasn't been working for quite a while now and i'm tired of manually renewing now. I get the following via mail for all...
  16. D

    Resolved Backup fails since update to Plesk Obsidian 18.0.26: "Unable to validate the remote backup"

    That indeed worked, weird, i had restarted Plesk after the changes.
  17. D

    Resolved Backup fails since update to Plesk Obsidian 18.0.26: "Unable to validate the remote backup"

    Well, then the issue is persistent for me. Probably rebooting the whole server after a few hundred days of uptime and seeing if it works after that.
  18. D

    Resolved Backup fails since update to Plesk Obsidian 18.0.26: "Unable to validate the remote backup"

    I did not have ftpForbidReuseConnection = 1, it wasn't introduced to fix it, is it required?
  19. D

    Issue mxtoolbox DKIM: Body Hash Did Not Verify

    I'm not really willing to pay for something that is most likely a bug (as with all the other possibilitites mentioned here already), i already rent a license, sorry.
Back
Top