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

    Question resolv.conf problems with Ubuntu 22.04 LTS

    The default IONOS Plesk installation uses DHCP, at least with Debian installations. The DHCP-client requests, on default, DNS-servers from the DHCP-server, which are IONOS-servers. After editing the /etc/dhcp/dhclient.conf and removing the entry "domain-name-servers" I was able to edit the...
  2. F

    Issue 2 "To:" fields in email header - After upgrade to 18.0.37

    Addition: This happens only for mails, coming from external mail client like thunderbird etc. Sending mails through the webmail service works and hast only 1 "To:" field.
  3. F

    Issue 2 "To:" fields in email header - After upgrade to 18.0.37

    I got the issue, that there are 2 similar "To:" fields in my Email headers in outgoing mail. So the mails are marked as spam or are unable to deliver. Does anyone know anything about that behavior? To: mail@example.com To: mail@example.com From: "mail@example.com2" <mail@example.com2> Subject...
  4. F

    Resolved Plesk firewall custom rule Allow incoming from all on all ports

    possible is everything ;) but, security is not only about good firewall rules. The rules you are using are very strict and do for sure a good job. But you should think about service security as well. What I mean, take care how you configure a service, use long and secure passwords in combination...
  5. F

    Resolved Plesk firewall custom rule Allow incoming from all on all ports

    you can also check the documentation -> http://www.proftpd.org/docs/directives/linked/configuration.html
  6. F

    Resolved Plesk firewall custom rule Allow incoming from all on all ports

    Yes, try to create the file 55-passive-ports.conf with the content from the post above in /etc/proftpd.d/ Also ensure that you can find the line Include /etc/proftpd.d/*.conf in your /etc/proftpd.conf dont forget to open the ports in the firewall you used in the ports.conf then restart the...
  7. F

    Resolved Plesk firewall custom rule Allow incoming from all on all ports

    The FTP-passive mode uses a address range to communicate with the client. To communicate with the server in passive mode, the client "asks" the server for a port (after being connectet via port 21), on which it can connect to the server to do some data-stuff. The client then tries to connect...
  8. F

    Issue new created mail account, with full password length (255), not automatically inserted into authentication database

    Whenever I create a new mailaccount via GUI, with full password length (255 upper, lower, digits, specials !@#$%^&*?~ ) on my Plesk Obsidian (18.0.36) !OR! Plesk Onyx (17.8.11) the account is created without adding it automatically to the authentication database...
Back
Top