[Review & Urgent Help] Chunkserve: Production VPS Dead, WHMCS 2FA Broken (502 Gateway)

triondres

Hello LET community and @Chunkserve rep,

I am writing this thread both as a review of my current ongoing experience and an urgent cry for help. To be completely fair and objective, I want to state upfront that I have been a loyal customer; this is my second year (second renewal) with this exact same VPS, and I have never experienced a single issue since day one—until today.

Currently, my production VPS hosted with Chunkserve is completely dead, and I am trapped in a frustrating "Catch-22" situation: I need to open a support ticket, but their billing portal is completely broken during the 2FA login process.

Here is the exact chronology of the nightmare:

Part 1: The VPS Failure (Target VPS IP: 141.11.62.177)

• Earlier today, my VPS suddenly hung. The KVM dashboard showed the status as "Online", but I was completely unable to SSH into the Linux OS.
• I initiated a forced restart from the panel. It took an unusually long time but finally completed.
• However, after the restart, all services inside the OS (aaPanel, OpenLiteSpeed, etc.) were hung and completely unresponsive. My websites remained down.
• I decided to perform a graceful shutdown via the KVM dashboard to attempt a fresh boot.
• Now, the VPS refuses to start at all. Every time I click "Start", Virtualizor throws a red toast message: Error 1) The operation could not be completed. The task logs are filled with "Started VPS - Fail" statuses.
• I even tried enabling Rescue Mode, but that failed to start as well, throwing the exact same Error 1) The operation could not be completed message. This confirms the issue is heavily on the host node/hypervisor side, not just a corrupted OS.
• VNC Console is also completely dead. When I try to open VNC to diagnose the boot sequence, it is just stuck in an infinite "Connecting..." loop, likely because the VM process isn't running on the host node at all.
  
  
  (Note regarding the attached Virtualizor log screenshot: The IP 114.10.98.229 shown in the task log is simply my local ISP connection IP performing the action, while the actual dead VPS IP is 141.11.62.177).

Part 2: The Billing Portal / WHMCS Bug (The Catch-22)
Since the VPS won't boot, my immediate reaction was to log into billing.chunkserve.com to open an urgent support ticket. This is where it gets worse:

• I enter my email and password successfully.
• I am prompted with the Two-Factor Authentication screen (/login/challenge).
• I input my 6-digit 2FA code and hit Login.
• The page hangs, redirecting to /login/challenge/verify, and eventually throws a Cloudflare 502 Bad Gateway Error (Host Error).
• I thought my authenticator app was out of sync, so I tried using my 2FA Backup Code (/login/challenge/backup). It results in the exact same 502 Bad Gateway Error.
  
  

Note: I can log into the Virtualizor panel perfectly fine, but I am completely locked out of the WHMCS billing portal due to this 502 backend bug on their end, making it literally impossible for me to contact their support team.

Call to Action:
@Chunkserve - I know you are active here. Please look into VPS IP 141.11.62.177 as the node seems to be having severe issues, and please fix your WHMCS 2FA verification endpoint so your clients can actually reach you when things go down!

I have attached all the screenshots proving the 502 error and the Virtualizor failure. I will update this review thread once the issue is resolved. Has anyone else experienced this 2FA 502 bug with them today?

Thanks in advance.