Tony

Administrators
  • Posts

    2,435
  • Joined

  • Last visited

  • Days Won

    158

Everything posted by Tony

  1. The software has evolved a lot in two years and since then a lot of the scenarios where it was a 403 instead of a captcha have been resolved. If this is still happening now I'd encourage you to open a new ticket and ask it to be escalated as that sounds like a bug.
  2. On all our shared/reseller/semi dedicated servers it should be giving a captcha in the event an IP is on our blacklist. I'd recommend opening a ticket and linking to this forum post so that our team can investigate why it's not working for your site.
  3. In cPanel if you click server information and the kernel version starts with 3.10- then you're on a CL7 server. It's unlikely many users are on CL6 at this point as all servers in Dallas, Los Angeles and New York are running CL7. The majority of servers in Singapore are now CL7 with our plan to eventually move everyone to CL7. We're currently migrating everyone in Amsterdam and that will be completed within the next month or so. Our Hong Kong location we hope to start the migration process in the next 2 months and similarly our Toronto location will be within the next few months.
  4. One correction here as all new accounts are now put on our CloudLinux 7 servers which uses 5.16.3. Only our CloudLinux 6 servers which all will be migrated to CloudLinux 7 before the end of the year are running 5.10.1.
  5. The easiest way if you just installed the wordpress installation through Softaculous is to reinstall it. When you do the installation this time make sure there is no folder and just your domain and it'll make so it's yourdomain.com/ . If you have already spent a lot of time working on it then you would need to move the files instead down one directory. After you do this you would also need to update any Wordpress settings so it knows the change in location and URL.
  6. We had a bug report this morning that certain systems did not have the Python application system enabled. We have implemented a fix and it's been pushed to all servers.
  7. There is no direct connection into China it would go through transit/peering. You're best to check the network speeds of all our locations: https://www.hawkhost.com/our-hosting-network and pick the one that performs best for you.
  8. Tony

    Brotli

    We already support it and it's enabled by default.
  9. The bug was was thankfully fixed a few hours after being reported. We assume the bug was caused by security fixes they released earlier in the day. Hopefully cPanel have added unit tests for this specific case with the file manager so a similar bug won't come up again.
  10. I would recommend opening a ticket in this case as we definitely did not disable Node.js on any of our servers. There are a few causes that could break Node.js such as running out of disk space on an account but it's tough to know the cause in your case without us checking your account.
  11. Any site using that specific PHP version would have the same extensions. If you add an extension to PHP 7.3 all sites using it would get it. The default extensions for EA/ALT are not the same and as such we always recommend using the alt versions as you have control over the extensions. The EA versions you do not.
  12. You'd just go back to the select php version page pick the PHP version from the drop down you want to modify and then you can adjust the extensions.
  13. You can change each domain using the multi PHP manager. The default extensions are close to the same not necessarily identical as our default alt-php's due to the cPanel built PHP's not containing all the same modules.
  14. We recommended alt-php* as they support the ability to change the extensions while ea-php* do not. For changing the extensions go to select PHP version in cPanel then you'll see the ability to change the extensions for any PHP version we have available.
  15. For the name field you put your domain instead of @ and it'll create the correct MX records. You will also want to remove the existing MX record created by cPanel which points the MX record to our servers.
  16. We have no railguns at this time in Hong Kong and have no estimate on when it would be available. Unfortunately this location has obstacles that make it more difficult.
  17. Tony

    Imunify360

    Do you have a ticket number? We can definitely disable on a website it so I'm not sure why you were told otherwise.
  18. My understanding is our billing team worked with you and resolved this. In the future if you have add-ons you no longer wish to use please contact us so they get canceled properly before they're overdue otherwise you risk the associated linked service becoming suspended.
  19. My understanding is our billing team worked with you and resolved this. In the future if you have add-ons you no longer wish to use please contact us so they get canceled properly before they're overdue otherwise you risk the associated linked service becoming suspended.
  20. Glad the migration went well and you're happy with the the faster and more reliable environment at a lower cost! This is just our first step on this new offering though moving everyone to this modern platform. It also opens up many new possibilities some of which all users will benefit from and others where the more advanced users may find useful.
  21. My understanding is our team worked with you and figured this out. Glad it's resolved.
  22. Tony

    Imunify360

    That is very strange I wonder if mod_security is actually getting disabled as I checked the ticket number and we saw mod_security hits still which would be indicative of it not being disabled. As far as disabling Imunify360 we can definitely do it on a domain basis (we have an internal support guide on how to do it). That being said if it's a mod_security hit for a specific application usually it's better for us to fix the rule if possible or for the user to disable mod_security. If we disable Imunify360 entirely for a domain then you're going to see an increase in bot traffic hitting your website. Of course if you still want to go that route just update the ticket asking for Imunify360 to be disabled and our team should be able to do it.
  23. cPanel operates with several major versions at one time, however they don't actively support them all. As of this post cPanel 78 is the recommended version and is installed on anyone using the RELEASE branch which is the recommended branch for production systems. The cPanel 78 reaching STABLE builds is most likely going to be the before the end of March meaning cPanel 76 will no longer be supported. The current LTS release before cPanel 78 is actually cPanel 70: https://documentation.cpanel.net/display/CKB/cPanel+Long-Term+Support . This version will actually reach end of life at the end of this month as well meaning going forward cPanel 78 is going to be the oldest version one can run with active cPanel support. As far as SquirrelMail it's not actively being supported and hasn't had a stable release since 2011. It does not support the latest versions of PHP ( http://php.net/supported-versions.php ) . There is a remote code execution exploit in it that affects the latest version: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-7692 . cPanel has been patching the software themselves for quite some time to resolve compatibility and security issues. This was however not a long term solution and since no one has taken over the SquirrelMail project then it was finally time to stop maintaining it. There are still webmail programs within cPanel that are actually being actively maintained by the maintainers that are still offered.
  24. If you navigate to subdomains in cPanel it should show you the document root of the subdomain there. It's most likely /home/username/public_html/forum.mysite.com if you created the subdomain a long time ago. Only for new subdomains/add-on domains does cPanel put them below the public_html folder.
  25. Tony

    Imunify360

    Imunify360 is designed to stop malicious requests and unless the IP has been associated with malicious activity they should never see any prompt. The other cause could be you're triggering mod_security rules which can be disabled via Mod Security in cPanel. If you are really insistent on having absolutely no web application firewall protection you can open a ticket and our team can disable it just for your domain.