• Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Tony

  1. 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.
  2. 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.
  3. Tony


    Do you have a ticket number? We can definitely disable on a website it so I'm not sure why you were told otherwise.
  4. 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.
  5. 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.
  6. 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.
  7. My understanding is our team worked with you and figured this out. Glad it's resolved.
  8. Tony


    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.
  9. 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: . 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 ( ) . There is a remote code execution exploit in it that affects the latest version: . 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.
  10. 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/ 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.
  11. Tony


    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.
  12. We support the ability to have random seek of MP4/H264/F4V files which would allow you to stream the video file. You could then use the video tag to actually display it. If you're looking for a software package to manage the video's you could use Wordpress or any other third party PHP application. We also offer Softaculous which has many free open source applications which I'm sure one of them may work. This would be dependent on the speed of your internet connection.
  13. Tony

    PHP versions

    It's unfortunately wrong the MultiPHP system is made by cPanel and it's just not as smart. It always displays the current version as what we set the default version globally which right now is PHP 5.6. I suspect this is due to the fact all your add-on domains are in your public_html folder meaning they'd inherit their parent folders PHP version. You could either change the document root of all your add-on domains to be below your public_html folder or you'd need to set the PHP version of every add-on domain in the the MultiPHP manager as well.
  14. The stdout/stderr logs should be written in the project root of the Node.js application. This is also true of our Ruby and Python application systems. If it's not doing that it might be worth opening a ticket and asking it to be escalated as it might be a web server bug specific to Node.js
  15. As we explained in the ticket your account was unfortunately found sending spam and as you had requested our team provided you with a backup of your account.
  16. My understanding is our team identified your issue and resolved it. What I suspect is someone from your side switched your website to use the Securi service but then forgot that SpamExperts was setup on the account. As a result the destination where SpamExperts was told to deliver email was incorrect. Now that this is fixed it be wise to keep SpamExperts enabled as I bet it was filtering out a large amount of spam for you and you had no idea as it was just doing a great job. What I assumed was going on based on the information you gave in this thread is you were forwarding email to Yahoo and they were deferring it (pretty common problem people have). Not that your email was bouncing due to an incorrect destination setting on SpamExperts. My apologies but when investigating an issue without being able to lookup a users account info one can only go based on the information provided here.
  17. It would the problem is anytime you forward they consider you as the sender of these emails. It's a pretty standard practice anywhere as otherwise spammers would just make fake forwards to get around filtering software. That unfortunately then means anytime we let spam through to your or accounts there is potential for legitimate emails to not arrive along with the spam. It's a pretty good chance Gmail or Yahoo were already causing you to miss legitimate emails due to them dropping them or putting them in a junkmail folder and it's never checked. Since you have a Yahoo business account it's worth asking them about missing email but I suspect they won't be much help and will tell you to use your email address or ask why aren't you hosting the actual email accounts with them as well and not a third party. Unfortunately just have to get them to add you for us to investigate further but what I suggested above I suspect is the problem and our team won't have a fix to it. Our side is doing it's job it's the other end deciding they don't want the forwarded email.
  18. Looking at that failure notice it looks like you're forwarding email from one address to a address which is the problem. Yahoo has decided they don't want these emails and after x amount of tries and y amount of days we inform you we've been unable to forward it along. We see an increasing amount of users run into problems where forwards start failing due to them forwarding spam to their third party email provider. This provider then starts sending all the forwards to a junkmail folder or in Yahoo's case they just start blocking them entirely. We highly recommend users use the POP3/IMAP checker features of these third party services and create actual email accounts if you really want to manage your email through these providers. That being said most will send your replies as, making it not look particularly professional. A few guides from common providers on how to do this: Yahoo: Gmail: It sounds like you found a mistake in our article while the URL it shows is correct the underlying link isn't. This has been corrected sorry for the confusion there. Though what we'll need in order for you to provide support is for you to get your email added as an authorized contact and without that we simply cannot provide support this is a security concern without a user being authorized.
  19. The code you pasted should be right as it's the default one if it's not working that is very strange. How our Node.js, Python and Ruby application systems work is by utilizing Phusion Passenger except it's Litespeeds own implementation of it. We're going to get a few tutorials up on deploying some common node.js apps as the guides for most applications assume you have your own server. This is obviously not the case with us but the majority of them should still work once you only do the portions that actually apply to deploying the application itself.
  20. The benefits are great when looking at what the format itself. The problem comes in when you're for example wanting to restore a backup. The way mdbox saves everything it's via index and multiple messages within a single file. The maildir format each email message is it's own file which makes it extremely easy to restore individual email messages. Under mdbox you cannot do this and you'd restore the entire inbox and say you wanted a message from 5 days ago you'd be stuck taking your entire inbox back 5 days.
  21. You'll login to cPanel then go to "Email Routing" then you'll see radio buttons with a few options pick the "Remote Mail Exchanger" option. If you need further assistance you're best to open a ticket with our support team.
  22. Hello, One is a PHP packaged by cPanel where you have absolutely no control over extensions. The alt-php ones you have control over the extensions so you can use select php version look at say PHP 7.1 and set specific extensions for it and save it. Any site that uses alt-php 7.1 would get those extensions and this is a new feature as of a few days ago. That being said our team discovered a bug where if you have too many extensions loaded it will throw a 503 error. We've implemented a fix for this already and it's propagating to all servers. In the next 24 hours roughly all servers alt-php should work as well from the multi php manager page.
  23. We support the mail() function meaning wp_mail() would work so that is not the issue. What sounds like your issue is your email routing in your cPanel is setup incorrectly. If you're hosting your email externally you need to login to cPanel got to email routing then let it know that you're using a remote exchanger. After that it will send the mail out from the server opposed to trying to locally deliver which is the default setting.
  24. The way our systems work is they assume unless specified otherwise email is hosted locally. This is for optimization reasons to avoid sending mail out only for it to come right back to the server as it would lead to slower email delivery rates on the server. You can modify this on your account by logging into cPanel then going to "Email Routing" and setting your domain to "Remote Mail Exchanger". After this it'll send the email out and it should arrive to the Office 365 systems.
  25. There are stable memcached and redis packages for PHP 7.2 so both are optional extensions under the select php version option in our cPanel.