Advertisement
hjysy

HostXNow review - bad experience

Sep 13th, 2019
144
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 44.68 KB | None | 0 0
  1. HostXNow review - bad experience
  2. I signed up to HostXNow after finding out about them here last year. I was on a small reseller package just to host a couple of sites with their own cpanel accounts. Most of the sites were small starter, test WordPress sites.
  3. ++++++++++++++
  4. If You want to buy cheap web hosting then visit http://Listfreetop.pw and select the cheapest hosting. it can be suitable for all your needs.
  5.  
  6. Top 200 best traffic exchange sites http://Listfreetop.pw/surf
  7.  
  8. list of top gpt sites
  9. list of top ptc sites
  10. list of top ptp sites
  11. list of top crypto currency Wallets sites
  12. Listfreetop.pw
  13. Listfreetop.pw
  14. Listfreetop.pw
  15. +++++++++++++++
  16.  
  17. One site received a bit of traffic, a hundred or so sessions per month. It had WordPress and woocommerce installed and was an Amazon affiliate site.
  18.  
  19. In general my experience was good, I only had a few sites here but the CPU and Ram "offered" was higher than most other hosts at that price point.
  20.  
  21. Unfortunately last week, the site was suspended. I wasn't notified and contacted support to find out what the issue was.
  22.  
  23. Their initial response was that the site was using high resources for a while and I needed to move to a VPS or move the site to another provider. I thought it might have been a rouge plugin or script but I couldn't access any part of the site to check. I was told that an e-mail should have been sent to me, I couldn't find it initially but found it in the spam folder. Unfortunately the e-mail was not useful as it was just confirming that the site was suspended and I needed a VPS - no prior warning so I can look into it.
  24.  
  25. After requesting access, I was told that I could be sent a backup file to check locally or move to another provided.
  26.  
  27. After looking at the analytics I could see that there were only a few hundred sessions over months so there was no spike in traffic. Without access, I couldn't figure out what else to do.
  28.  
  29. Eventually, after another request, the site was unsuspended, I was told that there was too much CPU/MySQL usage. I looked at the CPU usage in cpanel to check the usage, I was told by Chris that me doing that was causing more problems. I was again told to backup and move.
  30.  
  31. I checked the stats from cpanel and I did not get any faults for cpu or ram, I couldn't see where the issue was. I was told that this was because of CloudLinux and those stats were not correct.
  32.  
  33. So from the information I had, the only data available to me was worthless and my site was a problem but I didn't know about it.
  34.  
  35. Chris wanted me to move so I had no choice but to move my few sites.
  36.  
  37. My biggest issue was the way I was told that my site was a problem and I had to move it, the stats I had didn't seem so but if that is what I have to go by then what am I supposed to do? Maybe the sales pitch should be 2 x CPU when we are not backing up and only once a month
  38.  
  39. I know Chris is quite active here, this is where I found HostXNow. Feel free to reply or correct me if I made any mistakes as I only presented what I had.
  40.  
  41. If any other hosts are reading this, is this the standard process, suspend sites without warning and then offer a backup and tell customers to move on?
  42.  
  43. I did initially praise hostxnow so this is a fairer reflection after being with them for almost a year. Everything is all good when there are no issues, first real issue and I ended up having to leave.
  44.  
  45. HostXNow review - bad experience
  46. It was great until we would not let you host a site that was using too much CPU? Ok.
  47.  
  48. I signed up to HostXNow after finding out about them here last year. I was on a small reseller package just to host a couple of sites with their own cpanel accounts. Most of the sites were small starter, test WordPress sites.
  49. True.
  50.  
  51. One site received a bit of traffic, a hundred or so sessions per month. It had WordPress and woocommerce installed and was an Amazon affiliate site.
  52. It is not just about traffic. Even a few requests to a poorly coded script can use tons of CPU. That along with a fair bit of traffic at the same time can be too much, and it is a Shared hosting environment after all.
  53.  
  54. In general my experience was good, I only had a few sites here but the CPU and Ram "offered" was higher than most other hosts at that price point.
  55. Glad to hear that.
  56.  
  57. Unfortunately last week, the site was suspended. I wasn't notified and contacted support to find out what the issue was.
  58. You was notified, you said the email went to your junk/spam folder. It said "High Resource Usage. Contact support" or something along those lines. So you were notified. Please stick to facts. If the email was sent to your junk/spam folder then that is usually caused by a filter at email provider due to the sensitive information contained in the email. Happens with majourity of providers.
  59.  
  60. Their initial response was that the site was using high resources for a while and I needed to move to a VPS or move the site to another provider. I thought it might have been a rouge plugin or script but I couldn't access any part of the site to check. I was told that an e-mail should have been sent to me, I couldn't find it initially but found it in the spam folder. Unfortunately the e-mail was not useful as it was just confirming that the site was suspended and I needed a VPS - no prior warning so I can look into it.
  61. This is normal. You do not have access to Shared environment. You then contact support to discuss the issue which you did. You can be upset as much as you want to be cannot have your one site using lots of CPU for the price being paid. Simple as that.
  62.  
  63. After requesting access, I was told that I could be sent a backup file to check locally or move to another provider.
  64. True. Some wouldn't even do that and would just terminate your account and not even provide you with a backup file to abuse of resources. Of course, we did not do that and tried to make things easier for you. If you can't or don't want to upgrade to VPS even though going by the usage I recommended it, then that is up to you.
  65.  
  66. After looking at the analytics I could see that there were only a few hundred sessions over months so there was no spike in traffic. Without access, I couldn't figure out what else to do.
  67. Again, it isn't just about traffic, rather some coding causing lots of high MySQL usage causing a high load.
  68.  
  69. Eventually, after another request, the site was unsuspended, I was told that there was too much CPU/MySQL usage. I looked at the CPU usage in cpanel to check the usage; I was told by Chris that me doing that was causing more problems. I was again told to backup and move.
  70. Yes, we did not have to unsuspend, but we are not like other providers and tried our best to make things easier for you and for you to understand that the usage was too high and not acceptable in any Shared hosting enviroment at your price range, and that if you want to host such site with high usage a VPS would be needed, or at least a plan with high resource limits like our Performance Plan.
  71.  
  72. I checked the stats from cpanel and I did not get any faults for cpu or ram, I couldn't see where the issue was. I was told that this was because of CloudLinux and those stats were not correct.
  73. Again, CloudLinux doesn't always report high usage correctly. It was high MySQL usage which CL can miss. The same thing has been reported in threads with other providers too.
  74.  
  75. So from the information I had, the only data available to me was worthless and my site was a problem but I didn't know about it.
  76. That's the downside to using Shared hosting.
  77.  
  78. Chris wanted me to move so I had no choice but to move my few sites.
  79. Of course, for the reasons I mentioned above.
  80.  
  81. My biggest issue was the way I were that my site was a problem and I had to move it, the stats I had didn't seem so but if that is what I have to go by then what am I supposed to do? Maybe the sales pitch should be 2 x CPU when we are not backing up and only once a month
  82. I explained above.
  83.  
  84. I know Chris is quite active here, this is where I found HostXNow. Feel free to reply or correct me if I made any mistakes as I only presented what I had.
  85. I have corrected you. Enjoy your new provider.
  86.  
  87. If any other hosts are reading this, is this the standard process, suspend sites without warning and then offer a backup and tell customers to move on?
  88. The standard for Shared can be terminate the account and not provide a backup :/ We only suspend and did offer you a full/recent backup.
  89.  
  90. I did initially praise hostxnow so this is a fairer reflection after being with them for almost a year. Everything is all good when there are no issues, first real issue and I ended up having to leave.
  91. So you was happy to host many sites for nearly a year and when one of your sites starts getting traffic/resource usage of a highish spec VPS you create a thread here with "HostXNow review - bad experience"
  92.  
  93. Each to their own. I hope I helped you understand the situation a bit better.
  94. Fast Host - Cloud Hosting w/ LiteSpeed & Imunify360 Security
  95. Backup Storage - Backup Storage w/ SFTP, SSH & cPanel Access
  96.  
  97. The standard is if the usage is high, but not causing issues to other users, contact client / open ticket for him, if there is no response, suspend him to get a response from him.
  98.  
  99. If the usage is high that is using way more resources that it should, or is affecting other users, for sure will be suspended, and you will be contacted to provide him more information, help him fixing, or anything.
  100.  
  101. A host terminating inmediately, i haven't seen that before, and a host doing that will have a terrible reputation and feedback. simple as that.
  102.  
  103.  
  104. I would recommend you just change host, you exceeded what your previous host was able to provide you. And if your new host goes smooth, then you have your answer about those providers that promises a lot of CPU, power, etc... when you, as an user, can't really check if that's true.
  105.  
  106. I would recommend you just change host, you exceeded what your previous host was able to provide you. And if your new host goes smooth, then you have your answer about those providers that promises a lot of CPU, power, etc... when you, as an user, can't really check if that's true.
  107. Not necessarily, the issue could have been caused by an update from the OP, and the problem was fixed after we unsuspended the account. The site is moved to a new provider in good working order (most likely the case here).
  108.  
  109. So can't really go by that.
  110. Fast Host - Cloud Hosting w/ LiteSpeed & Imunify360 Security
  111. Backup Storage - Backup Storage w/ SFTP, SSH & cPanel Access
  112.  
  113. If any other hosts are reading this, is this the standard process, suspend sites without warning and then offer a backup and tell customers to move on?
  114. Yes. Usually it's an automated account suspension. - Server resources are shared fairly amongst other resellers/shared accounts on that server - so rather than let you hoggle the resources and slow the server down for everyone, it suspends you until you contact support.
  115.  
  116. As for backup & move on, well, that depends on the host, each host is different with different resource limits, it should be written in the tos.
  117.  
  118. Yes. Usually it's an automated account suspension. - Server resources are shared fairly amongst other resellers/shared accounts on that server - so rather than let you hoggle the resources and slow the server down for everyone, it suspends you until you contact support.
  119.  
  120. As for backup & move on, well, that depends on the host, each host is different with different resource limits, it should be written in the tos.
  121. To be clear, I wasn't just like "resource usage is too high, so please take a backup and move on". I suggested the issue either be fixed or upgrade to different plan/service that is more suitable for the resources that were being used. OP did not want to upgrade, and that is entirely up to OP. Instead, OP said he disabled something that he thought was causing the high load, and after he did the load was ok. I know the plugin being used uses 3rd party URLs. It can be as simple as some of those 3rd party domains being requested were not working and thus causes the site to hang/causes issues with high load. Seen it loads of times.
  122.  
  123. That's the thing when using WordPress with plugins/themes that request things from other third-party sites like CDNs/APIs (he mentioned it was connected to Amazon Affiliate Store and it was New Year's Eve!). If there is a remote issue, it can cause a problem for the site itself too.
  124.  
  125. This did happen right on New Year's Eve too. Sure someone didn't have one too many drinks given the occasion and broke something? *cough cough ;-)
  126.  
  127. We could have left the site use resources unnecessarily and potentially let it affect other customers hosted on the same server, but we didn't and resolved the issue, even on New Year's Eve! That's good management, IMO. Thread should say good experience, not a bad experience.
  128.  
  129. If we had a site from different customers hogging all the server resources unnecessarily and it affected OPs site, then I'm pretty sure he'd be on to us telling us to sort it out. Goes both ways.
  130. Fast Host - Cloud Hosting w/ LiteSpeed & Imunify360 Security
  131. Backup Storage - Backup Storage w/ SFTP, SSH & cPanel Access
  132.  
  133. As a third party, if I were reading this as a potential client, it looks to me like the server is loaded to the point that if my site traffic is higher than normal or something isn't working properly - that I'll just end up suspended and without paying more money there is no solution.
  134.  
  135. There are better ways to handle this to where the end-user's email still functions and they can access their cPanel, FTP, etc and can even still access their sites to work on them/investigate the issue while public traffic can't access it.
  136.  
  137. Without automating it - you could even just set up some password protection on the document roots or disable access for everybody but the client's IP address. You can do this via .htaccess easily but if your concern is that the client could remove it - you can do it via httpd.conf includes. Personally I wrote a script to automate a lot of this years ago.
  138.  
  139. That said - I have to ask - why are you giving your clients resource limits that, if they use those resources, they're using 'too much'? Can you quantify what their limits are and what limits they were hitting and why it was causing problems for the server as a whole?
  140.  
  141. I could see a shared user using 100% of their allocation all the time being something that needs investigated - but I can't see that it would be a big enough issue that suspension would be the first step.
  142.  
  143. I think I covered everything already.
  144.  
  145. Customer's site was causing a high load, and CloudLinux was not limiting it properly. Soon as I suspended the site, the server load returned to normal.
  146.  
  147. Unfortunately, it was New Year's Eve, and so support is, of course, going to be limited.
  148.  
  149. I will say the server IS NOT overloaded. The spec is 8 CPU with 3.1 GHz, and server load was around 5 when customer's site was causing high load, but because the backup was running at the same time, the load was going between 5-7. Again, soon as suspended the site, the load went back to 1-3 and no sluggishness.
  150.  
  151. The Cloud instance is top spec. Just something configured on the site that was causing the issue, nothing to do with the server itself.
  152.  
  153. We have a copy of the site in backup (the account has not been terminated yet) so could try to load it on a dev server and test it there if the customer likes, but he did not ask for this and created this thread. And besides, it could've been a tempoary issue with one of the customer's plugin connecting to Amazon API or something like that. Not much going to be checked on New Year's Eve.
  154.  
  155. So customer's site causes massive load on New Year's Eve and then in the New Year creates this thread mentioning the host with such damaging thread title right from the off all because his site was using resources that of highish spec VPS/Dedicated server at the time, but only paying for resources of the Shared plan? Not quite sure how that works, but there you go. And now the thread is posted on the weekend and he hasn't bothered saying anything since. Nice one.
  156.  
  157. Well, they say you cater to everyone.
  158.  
  159. This is the first time a customer mentioned this issue.
  160. Fast Host - Cloud Hosting w/ LiteSpeed & Imunify360 Security
  161. Backup Storage - Backup Storage w/ SFTP, SSH & cPanel Access
  162.  
  163. As a third party, if I were reading this as a potential client, it looks to me like the server is loaded to the point that if my site traffic is higher than normal or something isn't working properly - that I'll just end up suspended and without paying more money there is no solution.
  164. I'm not seeing that.
  165. || Need a good host?
  166. || See my Suggested Hosts List || Editorial: EIG/Site5/Arvixe/Hostgator Alternatives
  167.  
  168. I'm not seeing that.
  169. I guess it's good we're different people . For clarity I was speaking based upon the original post and what they said. I am curious what the average Idle CPU and free RAM is on their servers but I don't anticipate getting an answer.
  170.  
  171. IMHO account suspension should be the absolute last recourse should everything else fail. Any provider that really cares about their customers and their experiences should not be using suspensions to solve problems unless there is no other option whatsoever.
  172.  
  173. A few days ago there was an issue on a server that I administer on the side/freelance for a third party. I saw a user that was using ~35 CPU cores due to an issue with CloudLinux [an incorrectly specified limit]. It took a little bit of time to identify why this was but in the meantime no account suspension was ever put in place. The client was not forced to pay more money or to upgrade or to work via their backups or anything else.
  174.  
  175. Public access to the document roots was temporarily disabled while the issue was investigated. Even once the CloudLinux limit was corrected the account clearly needed more resources than it was given or they needed a chance to actually investigate and work on resolving the issue. Sure - they could have upgraded - or downloaded a backup and tried to investigate - or moved to another provider - but none of that was necessary.
  176.  
  177. There are almost always multiple ways to solve a problem - some better than others.
  178.  
  179. I hope that HostXNow takes away from this where and how they can improve so that should something like this happen again in the future they can resolve it / work on it / work with their clients in a more positive way.
  180.  
  181. If any other hosts are reading this, is this the standard process, suspend sites without warning and then offer a backup and tell customers to move on?
  182. No but it depends on how much load you are using and if you are doing 24/7 load.
  183.  
  184. If the site spiked with high load, which do happen with WP when you updated it, then it is fine. But constant or 24/7 overloaded is another thing.
  185. Specially 4 You ||| Elevate Your Sites
  186. .
  187. JoneSolutions.Com ( Jones.Solutions or Jones.Hosting ) is on the net 24/7 providing stable and reliable web hosting solutions and services since 2001
  188.  
  189. why do you keep coming in different HostXNow thread to try to make out we did something wrong and said that we could always do something better? Anyone who isn't even technical in any way can see what we did was justified. I'm not sure why you're saying otherwise.
  190.  
  191. Right now
  192.  
  193. Code:
  194. top - 23:46:53 up 24 days, 3:26, 0 users, load average: 2.73, 2.47, 2.45
  195. Tasks: 383 total, 2 running, 381 sleeping, 0 stopped, 0 zombie
  196. %Cpu(s): 12.9 us, 5.3 sy, 0.0 ni, 81.8 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
  197. KiB Mem : 29988136 total, 1028928 free, 5990432 used, 22968776 buff/cache
  198. KiB Swap: 0 total, 0 free, 0 used. 18462872 avail Mem
  199. Quote Originally Posted by MikeDVB View Post
  200. IMHO account suspension should be the absolute last recourse should everything else fail. Any provider that really cares about their customers and their experiences should not be using suspensions to solve problems unless there is no other option whatsoever.
  201. There was no option. The cPanel etc was sluggish and when I check MySQL queries it was showing updates to some plugin 24/7, and there was a lot of requests to the site. Therefore, I suspended the site, and it was the right thing to do.
  202.  
  203. I have seen an incorrectly configured site take down a powerful VPS node and doing what you suggested would not have helped as it causes 100% CPU usage due to the coding in the script. Many other different cases where there is no option but to suspend/terminate the account. I saw the load get higher and so I did what I needed to do before it potentially got even worse to the point where it could cause data loss or something more serious like that. It was something from API causing the issue
  204.  
  205. And what you say is irrelevant in this case as I've explained many times already. It was related to high MySQL usage which for some reason CloudLinux was not limiting things properly at the time. Maybe something was not working correctly at the time due to an update of CloudLinux/LVE. Point is I saw said site was causing the issue and acted on that which resolved the issue and all other customers sites were loading fine because of it. The customer had been fine with us for a year and then on New Year's Eve BAM!!! The load was consistently high, and I emailed to say it was high, and it needed to be fixed, but due to no response and after some time the load just went higher and higher and so the account was suspended (the affected account, not the entire Reseller account), then the load went down, he asked me to unsuspend it which I did, and the load went up. Customer disabled WooZone or something like that and the load went back down. It was most likely a plugin that caused it for whatever reason.
  206.  
  207. We could have just tested it on a dev VPS, but again, he did not ask for this and sounded ok about it as he seemed to know how to resolve the issue with the plugin.
  208.  
  209. Quote Originally Posted by net View Post
  210. No but it depends on how much load you are using and if you are doing 24/7 load.
  211.  
  212. If the site spiked with high load, which do happen with WP when you updated it, then it is fine. But constant or 24/7 overloaded is another thing.
  213. It was not just an update. It was causing high MySQL usage for constant MySQL queries to API/WooZone or something like that if remember rightly. Trust me, it was too much. This was on powerful 8 CPU server running fast 3.1 GHz processor with SSD/NVMe, CloudLinux, LiteSpeed, etc. There is no reason why that site alone should have caused such high usage. Hence why this went the way it did for it not to affect service for other paying customers hosted on the same server.
  214.  
  215. CloudLinux/LVE does not prevent total account hogging 100%. We all know this depending on the type of queries being run, etc.
  216.  
  217. I have nothing more to add to this. I did the right thing, IMO.
  218.  
  219. The customer had a shared account hogging resources which is not allowed as per TOS thus site was suspended. If the customer had a Cloud VPS, it wouldn't have mattered to us as other customers wouldn't have been affected by it, but this was a Shared server.
  220.  
  221. I'm done with this thread now. Uncalled for, IMO. Why did OP not just create a thread instead with a non-damaging thread title and not mention the name of the provider and asked questions if he was not sure? Makes more sense to me to go about it that way. Like it was done intentionally to cause damage for whatever reason.
  222.  
  223. Also, when customers do this a provider can cancel their service, well I'm not going to that level.
  224.  
  225. @OP it'd be great if you could request the thread title to be updated now you're more clued up about what happened. I'm sure you wouldn't like it if one of your customer's made such damaging thread title about your own business due to your customer not knowing the ins and outs of everything. Good luck with your new provider. Obviously, you won't have the same issue with them now thanks to this thread.
  226. Fast Host - Cloud Hosting w/ LiteSpeed & Imunify360 Security
  227. Backup Storage - Backup Storage w/ SFTP, SSH & cPanel Access
  228.  
  229. Hey, you can take what I say personally - or you can learn from it.
  230.  
  231. If you want to continue believing that suspension is the only way to handle issues like this you are welcome to do so. This doesn't affect me, just your customers.
  232.  
  233. Personally if I were you I wouldn't be asking why I reply to your threads but why users feel the need to come here and post a thread. I can, by nature of a public discussion forum, reply to this thread or any other thread here on WHT I desire.
  234.  
  235. If you see a thread about my company I welcome you to join in on the discussion.
  236.  
  237. Hey, you can take what I say personally - or you can learn from it.
  238. I never learnt anything from what you said, at least not this time. The site was using too many resources on New Year's Eve! and so I suspended it, then I unsuspended the account so the customer could check the issue and fix the problem which he did. Problem solved.
  239.  
  240. Quote Originally Posted by MikeDVB View Post
  241. Personally if I were you I wouldn't be asking why I reply to your threads, but why users feel the need to come here and post a thread that I can, by nature of a public discussion forum, reply to.
  242. Don't make out like my customers report issues here all the time, because they don't. Anyone can check review history. But we resolve any problems as fast as possible. No provider is perfect, not possible when running a Shared hosting service — too many points of failure, etc. But again, we do our best, and that's why our review ratio is more excellent than terrible. If some got an issue with that then that's their problem; they should concentrate on their business, not putting down others because they're doing ok/well.
  243.  
  244. You know the issue you had recently which no doubt stressed you out big time. I could've gone in the threads created by your unhappy customers stating the obvious how such issue could've been prevented, but I'm not going to patronise and try to talk you down like you seem to do in mine. People see past that.
  245.  
  246. Do as you will Mike. You might believe in bad publicity is good publicity, but I don't.
  247.  
  248. I see you just added
  249.  
  250. If you see a thread about my company I welcome you to join in on the discussion.
  251. The only time I did that for negative thread of yours was not done in the way you do to mine. Anyone can check what I said if they wish. I was helping; you're not helping here. You seem to come up with solution opposite to what I said which does not make sense given what I've said over and over again.
  252.  
  253. So, I did something you did not agree with? It does not mean you are right. Let other's judge for themselves if what I did was right or could've been handled differently. I've not seen anyone else disagree with what I did yet.
  254. Fast Host - Cloud Hosting w/ LiteSpeed & Imunify360 Security
  255. Backup Storage - Backup Storage w/ SFTP, SSH & cPanel Access
  256.  
  257. suspending the account, demanding to upgrade to a VPS or terminating the service giving a backup, is a terrible way to go, in my opinion.
  258.  
  259. Use CL, and limit the account number of processes.
  260.  
  261. Put less load on the very small server with 8 Core.
  262.  
  263. Easy.
  264.  
  265. suspending the account, demanding to upgrade to a VPS or terminating the service giving a backup, is a terrible way to go, in my opinion.
  266.  
  267. Use CL, and limit the account number of processes.
  268.  
  269. Put less load on the very small server with 8 Core.
  270.  
  271. Easy.
  272. Wasn't like that. You make it sound like this all happened within a few minutes to an hour. I worked with the customer for many hours on this, far more than what majority of providers would have done.
  273.  
  274. Hello,
  275.  
  276. The site has been using very high resource usage for some time. We did not mention it because it may have just been a temporary spike in traffic due to Christmas, but again, the usage is very high every day. We cannot host that site under your current plan. You may ask the owner of the site to host the site on a VPS with us, or you may host the website at a different provider.
  277.  
  278. Kind regards,
  279. Christopher Smith
  280. Some hours later the account was suspended, and the customer replied saying he did not receive an email regarding account was suspended. The email was sent, just in the spam/junk mail folder.
  281.  
  282. Posted on Monday 31st December 2018 at 16:29
  283. You should have received an email when the site was suspended?
  284.  
  285. I can provide you with a backup of the account, and you may check it locally or at a different provider. Please confirm.
  286.  
  287. Kind regards,
  288. Christopher Smith
  289. The customer said he was working on the site and when came back the site was suspended? This proves it was something the customer did that cause the problem to cause an even higher load than it did all the past days it was causing high load.
  290.  
  291. I have unsuspended the account for now.
  292.  
  293. No matter the limits you have, Shared is Shared and so they can't be used 100% 24/7.
  294.  
  295. Provide me with an update asap.
  296.  
  297. Kind regards,
  298. Christopher Smith
  299. Your site is using too much CPU/MySQL usage. Again, please fix it asap. Thanks.
  300.  
  301. Kind regards,
  302. Christopher Smith
  303.  
  304. Please correct script/plugin/theme and let me know once done and then I'll check if you have fixed the issue. If load continues I'll have to provide with a backup and check site somewhere else because we are currently running backup on the whole server and your site alone is causing a delay on this.
  305.  
  306. Kind regards,
  307. Christopher Smith
  308. The customer also said he was using PHP 5.6 and now switched it to PHP 7.2
  309.  
  310. Look, not my fault if the customer is using something that causes high usage. All I can do is help the customer try to fix the issue which I did.
  311.  
  312. </end>
  313. Last edited by HostXNow_Chris; 01-05-2019 at 09:55 PM. Reason: some typos
  314. Fast Host - Cloud Hosting w/ LiteSpeed & Imunify360 Security
  315. Backup Storage - Backup Storage w/ SFTP, SSH & cPanel Access
  316.  
  317.  
  318. If any other hosts are reading this, is this the standard process, suspend sites without warning and then offer a backup and tell customers to move on?
  319. It ultimately depends on the situation. Ultimately if your web host feels that your activity is causing harm to the other people on the server they are most certainly going to suspend first, ask questions later. As it relates to resource usages though, typically I like to think that a web host would simply rate limit your account first, then give you a window/opportunity to correct the situation before striking the ban hammer. However again, without having access to the server you were on, I could not say what should, or should not have been done.
  320.  
  321. Is this the first time you have experienced this type of issue?
  322. Checkout This Awesome cPanel Web Hosting Deal
  323.  
  324. "Knowing is not enough, we must apply. Willing is not enough, we must do." – Bruce Lee
  325.  
  326. It ultimately depends on the situation. Ultimately if your web host feels that your activity is causing harm to the other people on the server they are most certainly going to suspend first, ask questions later.
  327. Exactly.
  328.  
  329. Quote Originally Posted by Forward Web View Post
  330. As it relates to resource usages though, typically I like to think that a web host would simply rate limit your account first, then give you a window/opportunity to correct the situation before striking the ban hammer. However again, without having access to the server you were on, I could not say what should, or should not have been done.
  331. Spot on. I did try limiting the resources of the account, but whatever he had running not even CloudLinux LVE was able to throttle it at the time thus the account was temporarily suspended until he asked for the account to be unsuspended so he could check the issue. He fixed the problem whatever it was. Strange how there was no issue all year and then load crept up towards New Year's Eve and later on New Year's Eve the load went very high after "he changed" something as if to ruin New Year's Eve for many (unlikely the case here). But temporarily suspending the account until he could fix the issue was justified, IMO.
  332.  
  333. Quote Originally Posted by Forward Web View Post
  334. Is this the first time you have experienced this type of issue?
  335. Yes, at least with us. Going by thread history, he was with Guru before. Maybe he had an issue with them too; hence he tired us and was with us for a year.
  336.  
  337. Just checking the username of OP shows he is new to things. So it's be expected he did not entirely know some things, but hopefully, he does now thanks to this thread, Though it's best to ask in ticket instead on a public forum. We do not have to say anything at WHT, but I don't like false accusations, etc. If you don't know something just ask, no need to create such thread, IMO. Of course, popcorn for WHT though and people do seem to like a bit of drama at other innocent people's expense for various reasons.
  338.  
  339. Enjoy the rest of your Sunday everyone.
  340. Fast Host - Cloud Hosting w/ LiteSpeed & Imunify360 Security
  341. Backup Storage - Backup Storage w/ SFTP, SSH & cPanel Access
  342.  
  343. popcorn for WHT though and people do seem to like a bit of drama at other innocent people's expense for various reasons.
  344. I wouldn't necessarily look at it that way, something I learned is that every complaint (no matter how crazy I think it might sound) should be analyzed and if I am doing so honestly, there is always some merit to the complaint that needs to be addressed. Sometimes it can be as simple as the way we are communicating with our clientele. Other times it can be better screening, or education, maybe all of the above. Either way, I always make an effort to take situations like this to learn and improve.
  345. Checkout This Awesome cPanel Web Hosting Deal
  346.  
  347. "Knowing is not enough, we must apply. Willing is not enough, we must do." – Bruce Lee
  348.  
  349. This is an interesting 'complaint' thread. To me, it's quite logical that the provider suspended the account as it was utilizing too many server resources. Standard procedure. Perfectly acceptable. And it sounds like whatever it was that was causing it wasn't being able to be controlled by any of the governors within CloudLinux.
  350.  
  351. The only part that bothers me here is the statement of "powerful 8 core CPU" - I am assuming that's 8C / 16T and not 4C / 8T because we have to specifically request the latter for our vCenter servers. But the reason it bothers me is that Shared Servers should have a lot more cores than that. In 2019, I would say the minimum is 12C / 24T. It sounds like the server is underpowered.
  352.  
  353. Now, please correct me if I am completely wrong. I do not want to spread any misinformation so if I am wrong about the aforementioned, let me know.
  354.  
  355.  
  356. But the reason it bothers me is that Shared Servers should have a lot more cores than that. In 2019, I would say the minimum is 12C / 24T. It sounds like the server is underpowered.
  357. Well keep in mind that a server is only under-powered if the specs do not match the target load. Which ultimately comes down to how many active users the web host is planning to place on each server (which is always going to vary from web host to web host).
  358. Checkout This Awesome cPanel Web Hosting Deal
  359.  
  360. "Knowing is not enough, we must apply. Willing is not enough, we must do." – Bruce Lee
  361.  
  362. This is an interesting 'complaint' thread. To me, it's quite logical that the provider suspended the account as it was utilizing too many server resources. Standard procedure. Perfectly acceptable. And it sounds like whatever it was that was causing it wasn't being able to be controlled by any of the governors within CloudLinux.
  363. Exactly, Carefully tuned script to cause such issues or what? None of that on New Year's Eve. Gave plenty of notice and no response, like where post thread and no update since. For this reason, account suspended tempoarily until customer checked the issue and then fixed the problem. Of course, after he fixed the issue he then did not need to leave, instead, he chooses to leave and create this thread. Many would think the way it happened to be intentional. Low test sites all year and then cause disruption right on New Year's Eve with a high traffic/strange high usage site out of the blue. Many would suspend and likely lying if they say otherwise.
  364.  
  365. Quote Originally Posted by NortheBridge View Post
  366. The only part that bothers me here is the statement of "powerful 8 core CPU" - I am assuming that's 8C / 16T and not 4C / 8T because we have to specifically request the latter for our vCenter servers. But the reason it bothers me is that Shared Servers should have a lot more cores than that. In 2019, I would say the minimum is 12C / 24T. It sounds like the server is underpowered.
  367.  
  368. Now, please correct me if I am answer wrong. I do not want to spread any misinformation so if I am wrong about processor, let me know.
  369. It seems @Forward Web beat me to answering that question of yours. But This is 8 CPU with 3.1 GHz which is eqivlent to any provider running around 16 CPU with standard 2.3 GHz. So, yes, the 8 CPU with faster processer speed at 3.1 GHz is much faster compared to what other providers use like 2.3 GHz.
  370.  
  371. Well keep in mind that a server is only under-powered if the specs do not match the target load. Which ultimately comes down to how many active users the web host is planning to place on each server (which is always going to vary from web host to web host).
  372. So the server is 8 CPU at 3.1 GHz but can easily be upgraded to 16 or 32 CPUs given it's a Cloud server. Or create additional 8 CPU servers.
  373. Last edited by HostXNow_Chris; 01-06-2019 at 12:02 PM. Reason: corrected CPU info
  374. Fast Host - Cloud Hosting w/ LiteSpeed & Imunify360 Security
  375. Backup Storage - Backup Storage w/ SFTP, SSH & cPanel Access
  376.  
  377. suspending the account, demanding to upgrade to a VPS or terminating the service giving a backup, is a terrible way to go, in my opinion.
  378.  
  379. Use CL, and limit the account number of processes.
  380.  
  381. Put less load on the very small server with 8 Core.
  382.  
  383. Easy.
  384. I could not agree more! They should not put it on unlimited specs if they can not handle it. It should say how much resources you can use.
  385.  
  386. I could not agree more! They should not put it on unlimited specs if they can not handle it. It should say how much resources you can use.
  387. Excuse me? We do put the limits and list them on site and knowledgebase. We mention more restrictions than other providers do. We were one of the first to start listing the limits many others kept hidden.
  388.  
  389. The competitors bashing at WHT is quite pathetic. One of the reasons I haven't posted here for a long time. Just thought I'd clear things up in this thread.
  390.  
  391. No first-hand experience any many try to put down a provider doing well. Many see past the competitor bashing, etc. Keep doing what you're doing if you want to lose sales. And I'm not saying this to any one person, just speaking in general.
  392. Fast Host - Cloud Hosting w/ LiteSpeed & Imunify360 Security
  393. Backup Storage - Backup Storage w/ SFTP, SSH & cPanel Access
  394.  
  395. I never learnt anything from what you said, at least not this time. The site was using too many resources on New Year's Eve! and so I suspended it, then I unsuspended the account so the customer could check the issue and fix the problem which he did. Problem solved.
  396. There is certainly a lot you could learn from this - not just what I said - but the whole situation in general.
  397.  
  398. Personally I try to take a step back from any situation and evaluate not only why it happened but what could be done differently or better in the future to either avoid it or to handle it better. I know that I'm not perfect and my choices and actions may not have been the best once the dust settles which is why I always try to take that step back and re-evaluate it after it's over.
  399.  
  400. Don't make out like my customers report issues here all the time, because they don't.
  401. I was replying to this:
  402. Quote Originally Posted by HostXNow_Chris View Post
  403. @MikeDVB why do you keep coming in different HostXNow thread to try to make out we did something wrong and said that we could always do something better?
  404. You're the one that opened the door about multiple HostXNow threads, not me.
  405.  
  406. Anyone can check review history. But we resolve any problems as fast as possible. No provider is perfect, not possible when running a Shared hosting service — too many points of failure, etc.
  407. Absolutely. Nothing is perfect and we all make mistakes - it happens.
  408.  
  409. I think you're taking what I'm saying as me putting you down or criticizing you when that's not my intention. I suppose you could say I'm trying to be the devil's advocate and to get you thinking about what you aren't already thinking about. How you could handle such a situation differently in the future - and not so much trying to tear you down for what has already happened.
  410.  
  411. I am absolutely certain that I have made mistakes or choices that you wouldn't have made - or where you would have made better choices - and I'm more than happy to hear what you have to say if you ever feel that to be the case. We're human - we make mistakes - but what is more important than whether a mistake happens is whether we learn from it.
  412.  
  413. We're different people and what I may see as not having been handled well you may think is perfectly fine - and it may go the other way as well. Such is life.
  414.  
  415. But again, we do our best, and that's why our review ratio is more excellent than terrible. If some got an issue with that then that's their problem; they should concentrate on their business, not putting down others because they're doing ok/well.
  416. Ah, so you are taking my statements as tearing you down. I'll say again that is not my intention but if that's how you choose to interpret it there's not a whole lot I can do about it.
  417.  
  418. Quote Originally Posted by HostXNow_Chris View Post
  419. You know the issue you had recently which no doubt stressed you out big time. I could've gone in the threads created by your unhappy customers stating the obvious how such issue could've been prevented, but I'm not going to patronise and try to talk you down like you seem to do in mine. People see past that.
  420. You could have and I would simply have agreed with you that you were correct. There were a lot of things we could have done to avoid it or should have been doing that we weren't. It wouldn't have upset me in the slightest because in the off chance it's something we hadn't thought about - I'd have appreciated the feedback. In the event it's something we did already realize - I'd simply have stated as such.
  421.  
  422. At the end of the day - I'm not going to take any criticism positive or negative personally and will try to use it objectively to improve .
  423.  
  424. Do as you will Mike. You might believe in bad publicity is good publicity, but I don't.
  425. Not even sure where this comes from :: shrug ::.
  426.  
  427. Quote Originally Posted by HostXNow_Chris View Post
  428. The only time I did that for negative thread of yours was not done in the way you do to mine. Anyone can check what I said if they wish. I was helping; you're not helping here. You seem to come up with solution opposite to what I said which does not make sense given what I've said over and over again.
  429. Maybe next time I think you could do something differently that I think would work out better for you and your customers I'll send you a PM instead.
  430.  
  431. I honestly didn't expect you to get so personally upset over a little constructive criticism.
  432.  
  433. So, I did something you did not agree with? It does not mean you are right. Let other's judge for themselves if what I did was right or could've been handled differently. I've not seen anyone else disagree with what I did yet.
  434. It doesn't matter what other people think - it matters what you and your customers think. If your customer is happy with how you handled it - great. If you think you did an excellent job of handling it, that's awesome.
  435.  
  436. At the end of the day - learn from what I have to say - or don't - it's not going to upset me either way.
  437.  
  438. or you can learn from it
  439. All I see is "hosts" (people) talking too much, creating TL;DR threads, and are just arguing for sport. That turns off reasonable customers. Some folks need to think before posting.
  440.  
  441. All I see is "hosts" (people) talking too much, creating TL;DR threads, and are just arguing for sport. That turns off reasonable customers. Some folks need to think before posting.
  442. Well said. If the TOS of Hostxnow says that they reserve the right to suspend/terminate an account found using excessive server resources, then there is no point questioning the way in which they handled the situation of OP. Also if they are not handling things properly, sooner or later we will see lot of negative threads about them here in WHT.
  443. No matter how great your service provider is, the following golden rule still applies to you:
  444. Always keep a current backup of your data. You never know when your server will come crashing down on you.
  445.  
  446. All I see is "hosts" (people) talking too much, creating TL;DR threads, and are just arguing for sport. That turns off reasonable customers. Some folks need to think before posting.
  447. It appears that way, so closing.
  448.  
  449. If the OP has any more to add, please use the report button and we will reopen it temporarily.
  450. "Every successful individual knows that his achievement depends on a community of persons working together"
  451.  
  452. domain name registration
  453. 7 ways to make money
  454. a hosting country
  455. host agency
  456. swingbtc.com
  457. hosting oscars red carpet 2019
  458. t host parker
  459. t.j. is hosting a dinner party
  460. hosting 4 bd
  461. bonusbitcoin.co
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement