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

Recent content by javierllinas

  1. javierllinas

    Resolved https://mydomain.com:8447 not resolving

    Hello, Just an update on this: the only way I could make this work was using the hostname, in my case https://mail[dot]mydomain[dot]com:8447 Thanks @UFHH01 for your willing to help. Best, Javier
  2. javierllinas

    Resolved https://mydomain.com:8447 not resolving

    Yes, all Plesk ports are open. I also use Fail2ban, and have my IP whitelisted, and I guess localhost is added correctly 127.0.0.1/8 I'll try what you've just suggested, thank you very much
  3. javierllinas

    Resolved https://mydomain.com:8447 not resolving

    Thanks for the clarification, UFHH01. Unfortunately, killing the processes did not have effect on the issue: still can't load Updates and Upgrades URL using domain. Also, it seems that Plesk is running processes constantly, so they keep appearing. This process, in particular, keeps and keeps...
  4. javierllinas

    Resolved https://mydomain.com:8447 not resolving

    You did, but I'm afraid I'm not used to the syntax: is it kill 13924 0.1 1.8 153328 34392 ? How long is the ID? Is it like this (bold/red characters) -> root 13925 0.0 0.1 109716 2748 ? S 16:07 0:00 /var/[...] Please, excuse my ignorance.
  5. javierllinas

    Resolved https://mydomain.com:8447 not resolving

    Hi again, @UFHH01 It seems there are some processes going on: root 1392X X.X X.X XXXXXX XXXXX ? S 16:07 0:00 /var/cache/parallels_installer/parallels_installer_CentOS_7_x86_64_3.21.2 --service-mode --enable-xml-output --ssl-cert /usr/local/psa/admin/conf/httpsd.pem --branch...
  6. javierllinas

    Resolved https://mydomain.com:8447 not resolving

    Thanks for the feedback, UFHH01 Then, what's happening is that "https://<myDomainName.tld>:8443/admin/update/product/" isn't working: HOME > Tools & Settings > Updates and Upgrades has never worked if logged via domain, does that make any sense? Best, Javier
  7. javierllinas

    Resolved https://mydomain.com:8447 not resolving

    Hello, Just to clarify: https://<myIPAdress>:8443 -> Ok https://<myIPAdress>:8447 -> Ok https://<myDomainName.tld>:8443 -> Ok https://<myDomainName.tld>:8447 -> NOT resolving I'm trying to make this work with no success, appreciate any guidance. Best, J
  8. javierllinas

    Resolved https://mydomain.com:8447 not resolving

    Hello, I just want to know if its possible to reach updates via domain (https://mydomain.com:8447). I've secured Plesk with Let's Encrypt and have no issues accessing port 8443, but 8447 has never worked via domain URL, and I have to use the IP. Not a big deal but maybe someone has run into...
See more
Back
Top