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

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Search results

  1. Dork

    Resolved pam_systemd issue

    Yes - I did the yum install and everythig is working fine now.
  2. Dork

    Resolved pam_systemd issue

    # systemctl start polkit.service Unit polkit.service could not be found. (I did a CentOS update too)
  3. Dork

    Resolved pam_systemd issue

    pam_systemd(crond:session): Failed to release session: Die Wartezeit für die Verbindung ist abgelaufen What can I do?
  4. Dork

    Question Problem changing ssh port

    It works now but I think port 2222 is too obvious, isn't it?
  5. Dork

    Question Problem changing ssh port

    Thanks! The supporters should that add to the instructions!
  6. Dork

    Question Problem changing ssh port

    I did all steps of the instructions and taht worked fine but this command semanage port -a -t ssh_port_t -p tcp 2222 leads to: libsemanage.semanage_read_policydb: Could not open kernel policy /etc/selinux/targeted/active/policy.kern for reading. (No such file or directory). OSError: No such file...
  7. Dork

    Issue Not able to renew LetsEncrypt Certficate

    It has worked for years Now I had to disable BIND and it works again. Yes, it took me a lot of nerves and time.
  8. Dork

    Issue Not able to renew LetsEncrypt Certficate

    Thanks, but I don`t use Cloudflare.
  9. Dork

    Issue Not able to renew LetsEncrypt Certficate

    Sory, but it doesnt help. I tied a lot of other articles published by the supporters - but all of them couldn`t resolve the problem: Invalid response from https://acme-v02.api.letsencrypt.org/acme/authz-v3/179910320547. Details: Type: urn:ietf:params:acme:error:connection Status: 400 Detail...
  10. Dork

    Issue Not able to renew LetsEncrypt Certficate

    LetsEncrypt-Error .well-known/acme-challenge/xxxxxxx HTTP 400 But the file exists and is readable via the URL.
Back
Top