Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 04/01/2020 in all areas

  1. wolstech
    Please clear your cache. I'm able to connect to https://edvicon.org without any sort of error. Your certificate is valid for these domains: DNS Name=edvicon.heliohost.org DNS Name=cpanel.edvicon.heliohost.org DNS Name=edvicon.org DNS Name=mail.edvicon.heliohost.org DNS Name=mail.edvicon.org DNS Name=webdisk.edvicon.heliohost.org DNS Name=webmail.edvicon.heliohost.org DNS Name=www.edvicon.heliohost.org DNS Name=www.edvicon.org
    1 point
  2. wolstech
    That folder is where the system looks for a special file used for domain validation for the cert. Comodo connects to your domain over plain http and expects to find that file there to verify the domain is valid. If you have a redirect of some kind in your document root, the verification won't be able to find the file and you won't get a certificate.
    1 point
  3. wolstech
    You can put the protocol in the name field after the name, separated with a period. For instance, the _sip record with protocol _tls would become _sip._tls and get entered in the Name/Host field From MS's website (here):
    1 point
  4. Krydos
    Remote access enabled.
    1 point
  5. Guest
    If you use Tommy or Ricky, yes. It's automatic. Johnny needs you to manually intervene.
    1 point
  6. wolstech
    We can't troubleshoot or support any site using CloudFlare. Assuming the domain is added to your account, it should just work once you change the name servers back. CF is notorious for causing tons of issues with our service, so it's recommended that you avoid it if possible. The only times I've seen CF be required was when someone needed either the bandwidth support (lots of static content) or advanced DNS functions. 99% of users don't need it.
    1 point
  7. wolstech
    This domain should now be working. Please clear your cache if you still see an error or queued page.
    1 point
×
×
  • Create New...