Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by bear

  1. Choose one response: 1) It was a feature asked for by many users. 2) Open a feature request for us to ignore. 3) The new user/client system means it's hard to get right, so no.
  2. Got it. WHMCS changes have pissed everyone off, so therefore help/answers is what you can scrounge from older posts. Always enjoyed being punished for someone else's faults. 😉
  3. Very minimalist, that. Don't suppose more detail would be possible?
  4. Copy to text files and give them those?
  5. I've had a few ticket responses fail (I use piping import), and have yet to see that in this hook. Always shows empty. I have ticket responses going to a 2nd mailbox just so I know they've failed, and the most recent few show only "Ticket Import Failed" in the main log. No reasons given, just that brief message. I opened a thread asking if there was any more info to be found anywhere, but it got no responses. Disappointing.
  6. Why does it say to put the file into modules/hooks? That doesn't seem right (doesn't exist, for one).
  7. User opens a ticket, we're conversing in it. One of the more recent replies didn't get imported. The error message? "Ticket Import Failed". Helpful. Same email for the client, same email for the desk, ticket ID in the subject, no clue why it failed. Piping, version 8.1.3 of WHMCS. Any idea if this generated something more useful to help troubleshoot? My crystal ball is broken.
  8. Likely the result for many, not just you. May want to give them back the gearhead title too. 😉
  9. It was never offered, and in fact refused for every provider in the past, unless it was included with a hosting product. Until this recent revelation, I'd never once heard of a legitimate seller that didn't. Back door deals? I imagine it's not the only one.
  10. Honestly, WHMCS support should be the ones to help you, now that the rates for the software are what they are. They relied on members in this board to handle the things they either broke/removed/missed, and they've lost that support. They were told it was going to happen, and carried on as if it didn't matter. It did, and it does.
  11. Once the helpers that kept things running have all left (not just Brian!), that will probably be the fate.
  12. This is not a WHMCS security issue, as far as I can see. If the method you're using for signups isn't preventing this, that means it's probably a failure of ReCaptcha combined with allowing signups without a purchase. If you're using invisible recaptcha, change that to challenge/response and see if it helps. If that also fails to stop them, I'd suggest shutting off signups without a purchase, even if just for a while, if that's possible. I'd try the captcha first, and see if it does anything.
  13. OK, so the visitors are connecting to the normal signup pages, and you allow signups without purchase. Someone is connecting repeatedly over a VPN and setting up accounts and not being stopped by Recaptcha, so you feel WHMCS is hacked? Have I missed anything?
  14. You need to match up the time of the account creation and the page they hit in the server logs. That's where I'd start. Is this WHMCS installation isolated from other software and users (like on a VPS all by itself, no Wordpress, etc)? If not, I'd be checking that vector as well.
  15. Did each of those connections from that VPN (ipvanish) cause a new account?
  16. We allow signup only with a purchase. That stops all the bot signups. I'm curious how they're "injecting" accounts. Do they go through the signup form, or are these simply appearing?
  17. Interesting. Though not due to a pandemic, Kayako did that very thing, when they reduced existing support "contracts" by half. ' Kept hiring sales people and building sales centers, all the while telling us they were fixing support and putting money into developers. Blatant lies, it was eventually discovered.
  18. The flaw in this is the "monthly billing" thing. If they really wanted uninterrupted payments for owned license holders, the simple fix would be denying updates unless back payments were caught up if allowed to lapse in the first place. That would then deny them the really large price increase of the monthly-based-on-accounts model, however, and that was the real impetus there. No doubt in anyone's mind, despite the claims to the contrary. Very, abundantly clear. Even with concurrency, the fees were not high enough compared to the monthly lease, so they found a way to make owned licenses a thing of the past and marched on towards greater income for the VC that owns them. It will continue, they will increase again and again, eventually imploding in some way. VC's do that. Buy a company, monetize to death, sell the bones and move on.
  19. This is coming in any case, and was already in the planning, I'd suggest. It's not based on how many leave, it's simply a climb to increase until it stops growing enough, to see how far they can push that before it slows sales and retention.
  20. If you're using the multiPHP selector to have your site run as PHP7, but the system defaults to PHP5.6, that may be it. Make sure the cron is being called correctly, as in: /opt/cpanel/ea-php73/root/usr/bin/php -q /path/to/whmcs/cron/here Of course, that sounds more like you have the old cron file from that error. 😉
  21. Have to say, up to the deletion of the logs, it all seemed normal and expected for automated pruning *if* the conditions were actually met. Removal of the logs makes no sense, as you'd want those to show why and when. I know the point of pruning is to clear out old info, but that's just too far.
  22. I think that's the issue. Loads of white space in the logo, native size is height="419" and width="744". It's being resized to fit the space. EDIT: someone replied while I was writing this. 😉
  23. Not sure how it's lazy coding to have something that explains what it does do that very thing. Perhaps it should have checked "invoice, transaction and no active services", and I'd say it would be better if it called attention to the admin it recommends deletion and the reason, rather than carrying that out as soon as the condition is met. This is the very reason we've rarely used any "automatically do this" stuff in any software, much less something as important as billing. Too easy for something unexpected/unwanted to occur. Much rather have the inconvenience of manually reviewing things than the alternative.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated