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
That is disturbing
I don't know about that bro... I opened an urgent ticket with @Chunkserve cos i messed up ssh so kinda locked myself out cos I found out vnc wasn't working. I wasnt replied until june 24 by then i had already used the dashboard key for coolify to login instead.. to which i responded to them within the next hour.. that happened to fall June25 since it was close to midnight.. Since then no reply from there. now they carried out a server update and it looks like i even have more issues as alll my service is down currently even though some things still work like sshing into the instance. I wonder when i would get areply I mean how do you not respond to a ticker for over 3 weeks or thereabouts.. that is just terrible
I also bought two VPSs from them, and both were terminated for alleged abuse ("Outbound port scanning / worm propagation / similar network abuse patterns"). My account was suspended as well, so I couldn't even log in or open a support ticket.
I don't think it's worth wasting your time or money with this provider.
I wouldn't say that qualified as an emergency ticket (your server was running) and upon initial reading, triaged as non-emergency. You also didn't close the ticket when you were able to resolve it yourself.
Lastly, some of your services not running is on you to figure out, not them.
The service I got the flag for wasn't c-servers (it was just an aside about a provider with a similarly bad abuse detection system). Thankfully I've never bought from c-servers, or likely my account would have been suspended rather than merely given a silly warning.
what? lol.. what then is the ticket opening for..yes i messed up ssh but i reached out to support for assistance. I wouldn't have needed to do that if vnc was working which i already complained about some weeks earlier prior to this new issue. explain to me how that is not urgent! The ticket was kept open because the real issue i complained about was still not fixed or do i start relaying how long some of my messages get response.
and no some of my services not running is not on me when in fact this issue started after an update they sent a mail they were going to do.
As I said, your server was running, you just couldn't access it. In other words, if that request comes to me at 3am, it ain't no fucking "emergency" that requires getting out of bed to deal with.
Yes, that's 100% still on you (and you broke ssh yourself). They don't know what services you should have running and how it's configured. You don't have managed services. You appear to need handholding so you should look into managed services.
Microsoft updates often require user intervention to correct something after an update. Do you send them a message saying it's their problem to fix your service because of their update?
Was KYC not completed at the time you were ordering? How come the order was processed without KYC?
I am literally wasting time with you. Either you don't understand what is going on or you have no idea what you are spewing. cos explain to me how a customer complain of over ssh not working for 3 weeks is what you understand as "if i see a complaint 3am". the whole reason i am reaching out is the abilty to add keys throught the virtualizor apparently doesn't work and vnc wasn't working. Explain to me how that is my fault ..if tools to solve problems are non functional.
and yes I literally had to share log times to emphasize the update they made most certainly had to do with my current issue as nothing has changed for my side. Server got rebooted and things didn;t work like they did before..at a time curl commands in-machine was not working even though ssh was. just hit and miss no consistent behavior. curl works doesnt work but was consistently not working for a 3rd party repository .whatever reply you have.. i probably won't respond.
At this point, I am just putting all this out there for everyone to see and that includes @Chunkserve