WHMCS -> SolusVM (weird bug)

[TruvisT]

Tonight our 1024MB package randomly stopped creating accounts on SolusVM and required manual setup. The other packages work just fine. 

This is the working packages:



Broken one/create new:



Anyone seen or know what would cause WHMCS to stop seeing the SolusVM server randomly?

 

[KuJoe]

I have seen this a few times in the past. I can't for the life of me remember what caused it but you're not alone with this issue. I'll try to dig through my notes to find you more info for it.

 

[TruvisT]

I have seen this a few times in the past. I can't for the life of me remember what caused it but you're not alone with this issue. I'll try to dig through my notes to find you more info for it.

Thanks, Joe! Anything you find would be of help. I've recreated API keys and checked firewalls, ect... but nothing.

 

[trewq]

This has happened to me before. Can't remember what happened that caused it. From memory I deleted the broken one, copied the working package and edited the copied one to be the package that was broken.


This was over a year ago but I'm 70% sure that's how I fixed it.

 

[Geek]

Flat-out refusing to budge?  Hmm...

Broken one/create new:



Anyone seen or know what would cause WHMCS to stop seeing the SolusVM server randomly?

The only difference is the lack of a u/n prefix which I doubt is the catalyst.  Is it happening with the same package on multiple nodes, or is this a single node having problems?  Anything in the logs to give us a hint?  Any recent updates run?  As far as the node side is concerned I'd be glad to act as a second pair of eyes if needed...

@KuJoe - do you remember if the issue was leaning more towards WHMCS, or the node?  I don't want to waste this fellow's time going in the wrong direction.

 

[TruvisT]

This is how random it can act:



No updates have been done. As far as logs go, the API shows success:

seems like it is a SolusVM issue.



I could understand something breaking, but nothing has been touched.

I've never been much a fan of SolusVM and their panels. Maybe it is a sign to switch.

 

[WSWD]

This happened to us as well quite some time ago.  Submitted a ticket to Solus and while they were looking into it, it fixed itself.  I asked them what they did and they said they hadn't touched a thing.  So who knows?  Probably similar to how Solus randomly loses connectivity to some of the VPS nodes, even though connectivity is never really lost.  That one still perplexes me.

 

[Joshua-Epic]

I would try enabling the error log for the module. I know when I experienced a similar error, it ended up being a IP resolution problem so not exactly related but the logs did help point me in the right direction. 

 

[netgremlin]

This did happen to us a while back but for some reason while trying to investigate the problem it solved itself and has been fine ever since....we couldn't even duplicate the fault to reason it out... all we did was reset all the servers and reload whmcs from scratch. good luck

 

[TurnkeyInternet]

#1 issue we see is a firewall blocking communication between whmcs and a solusVM provisioning master node - for whatever reasons the packet count/type/volume occassionaly leads to a firewall block.  Rare, but thats the only time we have seen issues provisioning with it.

 

[winnervps]

@TruvisT

Have you tried put this:

<debug>on</debug>