• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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. Polli

    Issue Zend_Http_Client_Exception: Error in cURL request:

    The error still exists. I am now on a freshly installed server. This is currently the only error. Zend_Http_Client_Exception: Error in cURL request: Failed to connect to updates.nextcloud.com port 443 after 30000 ms: Timeout was reached in...
  2. Polli

    Resolved [MailQueueList.Filter.Status.maildrop] since last update of Plesk Email Security

    I think there is a new bug in the log browser. See the screenshot attached.
  3. Polli

    Issue Mails only possible with a wildcard certificate

    mail.vlowee-vanlife.de is just an A record and the MX entry at my primary domain. The primary domain is vlowee-vanlife.de. I wrote this just to make clear that there might be a misconfiguration. I just get around this issue with a wildcard, wich I don't want. There are a lot more domains on my...
  4. Polli

    Issue Mails only possible with a wildcard certificate

    Sorry for confusing you. English is not my native language. I moved my server to another one. I made a migration from Plesk to Plesk. I set every config the same as on my old server. But I get issues with the certificate. I then removed MTA-STS, DNSSEC and DANE to find out if this was the...
  5. Polli

    Issue Mails only possible with a wildcard certificate

    I have made a server move. This has worked so far. My server is running as a hidden primary DNS which was set up without any problems. Plesk is set up with one of my domains as FQDN. However, this only runs with a wildcard certificate although all entries seem to be set correctly. One of my...
  6. Polli

    Issue Getting DANE working

    I´m still struggling with the "untrusted TLS connection" issue. Ist there something that I can do to test the configuration and find the error? Thanks for your help
  7. Polli

    Question DANE support and IMAP Port 143

    I know it´s an old thread but same issue to me on a Debian 12. No entry for port 143 for imap are made by plesk. This should be a default entry, I think.
  8. Polli

    Issue Getting DANE working

    Thank you for your feedback. The steps that helped you do not work for me. Although all test pages show that my configuration is correct, it simply does not work. There is definitely room for improvement on the part of Plesk. But apparently there is no feedback from an employee of Plesk who...
  9. Polli

    Issue Getting DANE working

    Someone sent me an error message today because they were unable to send me an e-mail. Achtung: Die Mail konnte noch nicht versendet werden seit: 1 Stunde. Es wird weiter versucht die Mail auszuliefern bis Donnerstag, 20. Februar 2025 18:31:48 +0100 (CET). Der folgende Empfänger ist betroffen...
  10. Polli

    Input Enormous price increases yet again for 2025

    I find this statement a little arrogant. This is a slap in the face for all hosters who offer Plesk. They also suffer from the bad support of Plesk. This is probably how this statement should be interpreted. Then it can only be in the interest of Plesk to improve the “bad” support of the...
  11. Polli

    Input Enormous price increases yet again for 2025

    Yepp. Another point that I have not yet addressed. The support is unfortunately poor. My requests are often not understood and/or the answers do not match my question in the forum. I do not have a direct license from Plesk but through my server provider. If I have a problem, I have to talk to...
  12. Polli

    Resolved Local NS list does not match Parent NS list

    Ok. Got it now. I deleted the two entrys in Plesk (ns.inwx.de and ns2.inwx.de) and the error is gone. It was a bit confusing to me because mxtoolbox mentioned that these entry are missing. In the end it was just a propagation issue. I had the correct settings from scratch and added the "missing"...
  13. Polli

    Resolved Local NS list does not match Parent NS list

    I think I need to formulate my posts a little more precisely. As I wrote in my first post, the website is up and running, it is accessible. There is only this error message that I would like to fix. My registrar has told me that I have to make these entries in Plesk. But unfortunately this is...
  14. Polli

    Resolved Local NS list does not match Parent NS list

    I've set those entry already. Without these entry's my domain is not reachable. Please read my first post again? It's all done already. I need to get the missing entry's on my Plesk server. What do I have to do to correct this error?
  15. Polli

    Resolved Local NS list does not match Parent NS list

    Yes I know. But how can I solve this? Plesk has no option for this Glue-Record because inwx.de is not my domain. I can only set A records for my domain. Is there another way to set these entrys in my DNS configuration?
  16. Polli

    Resolved Local NS list does not match Parent NS list

    I have my server running as primary DNS and my registrar as secondary DNS. This also works so far. However, there is still an error message. Local NS list does not match Parent NS list 192.174.68.104 was reported locally, but not by the parent<br/>176.97.158.104 was reported locally, but not by...
  17. Polli

    Issue Zend_Http_Client_Exception: Error in cURL request:

    There is no connection issue. I can ping all necessary domains and ip´s with no issue. The error appears since the last update for the nextcloud extension and/or bind9 updates. This is just a few days ago.
  18. Polli

    Issue Zend_Http_Client_Exception: Error in cURL request:

    I´ve now found out that this error exist since the last update of the nextcloud extension. This error appears every hour. Along with this update of the nextcloud extension, there was also an update of bind9. Zend_Http_Client_Exception: Error in cURL request: Failed to connect to...
  19. Polli

    Issue PHP Warning: gzinflate()

    The gzinflate() error is gone with the update. But the new one seems to me that it is come with the last bind9 update. But I´m not sure. My Nextcloud is always the newest. Also my server is always up to date. I look for updates every day as a routine for me.
  20. Polli

    Resolved [MailQueueList.Filter.Status.maildrop] since last update of Plesk Email Security

    I´ve now removed Plesk Mail Security and the error still persist. So it is not the extension as you mentioned.
Back
Top