• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Search results

  1. F

    Resolved Curl error: (6) Couldn't resolve host name

    Hi, glad you found out and fixed the issue.
  2. F

    Resolved Curl error: (6) Couldn't resolve host name

    Hi, you're facing different issue than mine. My DNS-Server requested the wrong NS so it was not temporary failure in name resolution. Maybe you should start there...
  3. F

    Resolved Nextcloud installation and scheduled tasks throw "Php handler does not exists"

    Hi Peter, thank you for forwarding the issue to devs. Do you have ticket system which is public an we can track the ticket EXTPLESK-5258? Or is the ticket system closed? Are there workaround how I can install nextcloud on plesk since I have to show a customer how nextcloud looks like on our...
  4. F

    Resolved Curl error: (6) Couldn't resolve host name

    Hi, sorry for the late reply. The issue has been resolved, and it was due to the wrong nameserver (authoritative), which I replaced with the correct one (recursive). Since then, all DNS-related issues have been resolved. Thank you for your replies. Best regards, Floh
  5. F

    Resolved Nextcloud installation - Php handler does not exists.

    Hi everybody, I just tried the Nextcloud extension. Unfortunately, I cannot install the Nextcloud instance because the installation failed at the preparation stage with the error "Php handler does not exists." I attempted the installation on a subdomain with PHP 8.2.13 (FPM-Application Apache)...
  6. F

    Resolved Curl error: (6) Couldn't resolve host name

    You mean /etc/resolv.conf should have those both lines: Not sure if it matters, Plesk is running as primary Nameserver (synced with 2 secondary nameserver on different machine) for the Domains hosted by Plesk. Does it matters? I'll try that at weekend because currently there is a live-event...
  7. F

    Resolved Curl error: (6) Couldn't resolve host name

    Hi, I'm facing multiple issues with the Plesk Server that it cannot resolve while performing daily tasks, such as creating backups. The recurring problem seems to be related to Curl's inability to resolve. For instance, here's an example of the issue I'm encountering: I've already...
  8. F

    Resolved Unintended Additional A/MX DNS Records

    With the help from Plesk support everything is fixed now after he repaired my dns database. Also following command is useful if you want find out which domain contain a record: plesk db "SELECT host, dns_zone_id, type, val, opt FROM dns_recs WHERE type = 'MX' and host LIKE '%example.com%'" Now...
  9. F

    Resolved Unintended Additional A/MX DNS Records

    Hello Peter, thank you for clarifying. As you can see in the screenshot, the DNS service is disabled for the business subdomain. Or did I overlook/misunderstand anything? Should I enable the dns service for that subdomain and see if there is MX record and delete it before disable it again? (In...
  10. F

    Resolved Unintended Additional A/MX DNS Records

    Unfortunately, I'm having difficulties with the tech support. They are testing with the current valid nameserver, which is not the Plesk server itself. I have already told them twice to perform the request directly at the Plesk server. Now they are asking me to contact my domain registrar or...
  11. F

    Resolved Unintended Additional A/MX DNS Records

    Found the ticket request page. Will fill in now.
  12. F

    Resolved Unintended Additional A/MX DNS Records

    businesscard.mydomain.com is a valid subdomain and there the dns-page is disabled as you can see in following screenshot: But this subdomain doesn't matter for this issue for now. This is the dns-page of mydomain.com (it's actually a .de domain but here I masked to mydomain.com due to privacy...
  13. F

    Resolved Unintended Additional A/MX DNS Records

    Hello Peter, root@hosting:~# plesk db "UPDATE dns_recs SET opt = '5' WHERE type = 'MX' AND val = 'mydomain-com.mail.protection.outlook.com.'" root@hosting:~# plesk db "SELECT type, val, opt FROM dns_recs WHERE type = 'MX' AND host LIKE '%mydomain-com%'"...
  14. F

    Resolved Unintended Additional A/MX DNS Records

    Hi Peter, just to be sure you mean change the opt-value by MySQL-UPDATE command'?
  15. F

    Resolved Unintended Additional A/MX DNS Records

    Nope, it has different FQDN.
  16. F

    Resolved Unintended Additional A/MX DNS Records

    Ok, I did it. I hope I didn't overwrite customers dns settings. :D root@hosting:~# plesk repair dns Checking the DNS configuration file ................................. [OK] Checking the user DNS configuration file Restore the user DNS configuration file from the template? [Y/n]...
  17. F

    Resolved Unintended Additional A/MX DNS Records

    Hi Kaspar, thank you for your quick reply. The first plesk command looks good, but the database query is weird. The first line shouldn't exist. The second line is for a subdomain businesscard and there the dns and email-service are deactivated but shouldn't matter for mydomain.com, I think...
  18. F

    Resolved Unintended Additional A/MX DNS Records

    Hi Peter, No, I cannot test with mxtoolbox.com because I haven't changed the nameservers yet due to the ongoing issue we're discussing. Instead, I am using the following online tester: https://manytools.org/network/query-dns-records-online/ This tool allows me to specify which nameserver to...
  19. F

    Resolved Unintended Additional A/MX DNS Records

    Hello everybody, I have configured the domain settings for a domain. I set up a single MX-Record as follows: mydomain.com. 86400 IN MX 0 mydomain-com.mail.protection.outlook.com. However, when I checked using dns-checker, I noticed two MX records from the Plesk server: mydomain.com. 86400 IN...
  20. F

    Resolved run-parts: /etc/cron.daily/60sa-update exited with return code 4

    Fixed it with following commands: wget http://spamassassin.apache.org/updates/GPG.KEY sa-update --import GPG.KEY But do you know why this happened? And why doesn't plesk-update script check if the key is still valid and try to repair itself by updating the gpg key? Best regards Floh
Back
Top