New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
@Chunkserve, Node has been offline for 3 days now, Ticket #LQC-650903
Any plans of restocking?
waiting restock
restock please
waiting restock
Paid two days ago and server is still on pending and no answer on tickets. I understand that is a budget vps, but it's too much. Crappiest service 👎
Check Ticket #RRF-349402. No need to activate the server just refund me
LOLZ 😂 Sorry mate
previous post got people say "Node has been offline for 3 days now"
how to provision a server for you?
Hey,
I see the ticket. We didn't receive webhook response about the payment, and that is probably the cause why it didn't provision automatically. Please understand that there were public holidays in Poland (01,03 May), and that's why there were sligh delays. Already issued a refund by the way
Node is and was online; I always prioritise to contact customer at first. The case was not connected with the node - more likely with single service, and as far as I know, nothing on our side caused it. I sent the message to the customer on ticket, that explained what I did.
ChunkServe’s refund policy must be written in invisible ink.
Support response time: somewhere between soon and never.
(BTW still no reply to my ticket. Still no refund.)
Hey,
(The refund for $2.49 has been completed 5/6/25, 9:11:25 PM). Also, You can always inform us via ticket. I informed You via the comment - sorry for not doing that on a ticket too. We didn't receive any new ticket/reply since I replied to You here.
as I said yesterday, it's done on our side. Please check it now
Can you check some of your vms are offline? Ticket ID: OSY-957841
$2.49 😂
@Chunkserve Bro Waiting Fro Restock 😎😎😎
man my vps is suddenly offline again, its the 2nd time since nov 2024. But now it cant be started. node03-AMS
Same as mine, 2nd time since nov 2024 probably same node as yours but now it says only localhost instead in which node is it.
My node text is still the same.
Man this ticketing support is useless, already 18 hours but still no respond.
Still Offline ? Been 6 days so far
May You please DM me? Everything is online from what I see
No response from you since January. I sent 3 messages that still remain unanswered - see here: https://share.zight.com/2NuePN1W
My server continuously turn off and have been doing this since the beginning. I have to manually go into your panel and turn it on again. I have 4 servers with you. You fixed the issue with one of them - kind of - it still turns off but it autorestarts.
However the others just turn off randomly - IPs ending with 69 and 49.
Could you please check and get this fixed. I can see form the threads here that it is a typical problem with responses and servers turning off.
Hey,
may You please check the ticket again? In fact, a lot of tickets regarding "offline" state are only indicationg the wrong status on the virtualizor panel; and the server itself works flawlessly. Since couple of months we didn't notice any major downtime that would degradate all the services. Waiting for Your response
Have a great day!
It's not a problem with the server indicating the servers going down and not going down - then I wouldn't write here. I have customers complaining and I have docker containers with services that I can't connect to. They constantly go down. Everytime I log into the chunkserve controlpanel is because one of my servers again have gone down. And I also get notifications of downtime from Malcare.
Honestly, I don't understand why do you write privately that I am trying to start "drama" simply for writing here - where else can I write when you don't respond to my tickets despite 3 followups? The reason why the server is pingable and up now is because I have restarted. It is down every few days.
"Hey,
I'll try to fully whitelist communication between virtualizor master server and node04."
xx.xxx.xxx.69 is pingable, checking the uptime history now. If virtualizor shows wrong status - it may be also related to communication error between nodes - sometimes caused by the protection. Sorry for the delay - it was a really old ticket - and of course it's my fault. However, there's no need to start any drama or anything like that - sorry if I got Your intentions wrong. I'm there to help
And as I said before you also fixed it with another node, which has not gone down since. So you solved it once - which is positive which I also mentioned. No drama here simply stating the fact.
Also another positive thing I want to share is that the servers are actually really fast and I'm very happy about them apart from them shutting down randomly.
Hey,
thank You for the clarification! I'm indicating the issue with status as a response for "I can see form the threads here that it is a typical problem with responses and servers turning off." - wanted to confirm if it's the case or not.
Regarding drama - it looked a bit like that for me, but I told You that if I got it wrong, then I'm sorry. I blamed myself for the response time - as far as i know the ticket got left on "customer-reply" since a long time. As mentioned on the status page + WHMCS, we restarted the server after applying couple of changes on the hypervisor side; let me know if issue still persists
(VMS should be up in around ~5mins). I alsoa dded 1month on me to the server.
Please give me a feedback after it will run for some time! Thank You so much
Have a great day!
I see that the service is up, CPU ~100%, probably everything on the VM is turning on, waiting for the feedback. It would be amazing to see that the service can finally satisfy the requirements and that this issue is fixed. It's the most important thing at the moment. Thank You so much again for clarification!
its up again after 2-3 days i think, after my ticket is processed. but the vps still offline on the dashboard last time i check.
@Chunkserve any chance you guys could actually check / answer your support tickets. My server has now been down since the 9th and I have had a ticket open with no reply at all from you. Pretty freaking sad.
You have to have a whole node down since Virtrtualizor just continues to return "Error 1) The operation could not be completed"...
My 2 cents.
Cheers!
This is a good post and exemplifies the issues I've had. Every few days to week, the VPS will randomly shut down for no reason i've been able to find. It has to be restarted via control panel, and typically a few times for some reason (ie, I'll restart - it registers online in control panel but I can't connect...will wait 15 minutes and try again and still won't connect then I'll restart again from control panel), before it'll come back online. It ran great with zero downtime from Nov to late March and it's been that every week to few days since. I've moved everything off for the time being and will try again in a few months.
(The only thing I got from support was "it shows up on our end" so that's why I'm waiting to see if they get the node's underlying issues sorted before trying again. When it's working it's an awesome VPS)
Hey,
Thank You for the feedback. May You share the ticket ID? Regarding issue You’re reporting, my main thought is we migrated the server one day and virtualizor did not reflect the change. > @mbjones said:
Hey, thank You for the feedback
It was about the VNC?
VNC issue is mine and it's still unresolved.
Mine is before 9th and still offline. I even DM him like he wanted but not single response either in ticket or DM...