• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • 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.

Search results

  1. Jürgen_T

    Question Unwanted permanent redirct of a new subdomain

    I have some subdomains which work without problems. But a new one test.domain.tld redirects continously to my www.domain.tld wihout having this applied. Is there any idea where the error comes from?
  2. Jürgen_T

    Question Nextcloud nginx only

    Adding this to the NGINX configuration could solve your problem.
  3. Jürgen_T

    Resolved ModSecurity configuration files and directives remain on the server after its removal

    Thank you for checking this issue. I removed the modsecurity rests and found also modsecurity-files in each /var/www/vhosts/sytems/xxx.domain.tld/conf/ Just to complete the information. I removed all files with an impact to nginx and it works. Now the error has gone.
  4. Jürgen_T

    Resolved TLS versions for nginx

    Thank you for the confirmation that it is used for internal com. Then I‘ll leave it unchanged.
  5. Jürgen_T

    Resolved TLS versions for nginx

    My ssl.conf file in /etc/nginx/conf.de/ contains the following: Why do I have the old and weak TLS-versions TLSv1 TLSv1.1 automaticly installed for proxy_ssl_protocols. Does this make sense or can I remove it?
  6. Jürgen_T

    Resolved ModSecurity configuration files and directives remain on the server after its removal

    After some problems with Modsecurity I removed it using Plesk installer (web interface). This seemed to work and now it is indicated as removed However in /etc/nginx/conf.d/ modsecurity.conf still exists with the following content: So it says Modsecurity is on and receives the configuration...
  7. Jürgen_T

    Resolved Error fail2ban since update to 18.0.63

    I just got an update to some features of Plesk including fail2ban. Now it seems to work! Thanks to you and to the developer for the quick solution!
  8. Jürgen_T

    Resolved Error fail2ban since update to 18.0.63

    I will do so and I've sent you a pm with a proposal how to proceed.
  9. Jürgen_T

    Resolved Error fail2ban since update to 18.0.63

    The Plesk Obsidian 18.0.63 Update #3 tonight did not help. Trying to configure fail2ban through plesk UI led again to error 500 together with the message: [plesk-one-week-ban] would be missing. To solve this error I added to the new jail.local the following entries where [XXX] stands for you...
  10. Jürgen_T

    Resolved Error fail2ban since update to 18.0.63

    Now everything works fine also the manual banning feature! Thank you for your help!
  11. Jürgen_T

    Resolved Attempt to change status of non-configured mail service. [domain_id = 28]

    Cool, this helped! Thank you.
  12. Jürgen_T

    Resolved Attempt to change status of non-configured mail service. [domain_id = 28]

    I have read the article but hesitate to use this recipe until I have found out which domain/subdomain is meant by domain_id=28 in my case. What do I have to do to get more information about ID=28 before I delete belonging entries in the plesk-DB?
  13. Jürgen_T

    Resolved Attempt to change status of non-configured mail service. [domain_id = 28]

    Thank you, I`ll report if I succeed with this information.
  14. Jürgen_T

    Resolved Error fail2ban since update to 18.0.63

    To give the developers an additional input. I suppose, that in my case the following influenced the upgrade. On an earlier stage I used modsecurity. During the installation also a modsecurity jail was added to plesk.conf. Due to some reasons I had to remove modsecurity but the jail of fail2ban...
  15. Jürgen_T

    Resolved Error fail2ban since update to 18.0.63

    Thank you for this hint. In my case grep -R plesk-one-week-ban /etc/fail2ban/ does not bring up something except my own and new modifications to get fail2ban work. In addition I do not find a filter called plesk-manual.conf Could you please also provide the content of this filter, too? Then I...
  16. Jürgen_T

    Resolved Attempt to change status of non-configured mail service. [domain_id = 28]

    Suddenly after upgrade to Plesk Obsidian v18.0.63 I found this error message in the Plesk protocols: Attempt to change status of non-configured mail service. [domain_id = 28] How can I solve this?
  17. Jürgen_T

    Resolved Error fail2ban since update to 18.0.63

    To get access again you could try to add this to your jail.local: [plesk-one-week-ban] enabled = false Probably you will get then another error, what you can solve in a similar way by adding [plesk-permanent-ban] enabled = false (Do not forget to restart fail2ban after modifying the...
  18. Jürgen_T

    Resolved Error fail2ban since update to 18.0.63

    Thank you for your attention but I didn't contact your support. Instead I switched back to the old version of fail2ban, as the re-installation (plesk installer --select-release-current --install-component fail2ban) did not work as expected. I.e. only the directory /etc/fail2ban had been created...
  19. Jürgen_T

    Resolved Error fail2ban since update to 18.0.63

    After reinstallation of plesk-fali2ban no files are available in /etc/fail2ban . I am currently using the old version again but I cannot manage it using the plesk panel as the error appears as described above.
  20. Jürgen_T

    Resolved Error fail2ban since update to 18.0.63

    Anything else?
Back
Top