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
one time
omg. I'm just tired of the fact that you don't want to fix the situation, although you have the opportunity to do so.
It doesn't reproduce on other servers. It appeared after the upgrade. Because of it, I can't use the server.
We'll continue to help and support you. The only thing i ask is respect on your ticket. Despite everything and some of your inappropriate responses, we're trying to help you, even by opening tickets directly with our upstream partners who direct our traffic.
We'll let you know as soon as we have more information, Don't think that we enjoy having an unsatisfied customer or that we are making fun of you.
Let me repeat: everything was working perfectly. Before the upgrade. I don't recall you telling me in the ticket that you'd sent a request to Fastly for example. I do remember you suggesting I wait. Even though the problem has been going on for at least a week now. And you didn't suggest anything other than disabling Neoprotect, which started causing the problems after the upgrade.
I hope everything will work perfectly again, just like before the upgrade. But it's hardly a good idea to tell the user you can't do anything when you absolutely can. And denying the obvious probably doesn't make sense either.
Once you finally fix the situation, I'll be sure to edit my review. I hope you'll do it sooner rather than later.
The recent network upgrade did not modify NeoProtect in any way. Its configuration and routing behavior are exactly the same as before. The temporary IP we assigned you with a lighter protection profile was used only for diagnostic purposes, and it confirmed that NeoProtect is not the cause of the issue.
As mentioned, we have already opened tickets with our upstream providers to verify whether an alternative path or routing optimization is possible.
So, explain to me why I'm having so many problems after the upgrade, and almost all the problems go away after changing the IP? I have two servers, one with Neoprotect, the other without it. The first one has random timeouts, SFTP freezes, and Warp-SVC burns the CPU. But the second one only has a problem with the .108 GitHub IP. Can you explain this by something other than Neoprotect, which didn't affect the server's performance before the upgrade?
When you reach this level of back and forth it's time to just cut your losses man. There's almost never any point or use in bickering with the host. I'm almost there as well.
Everything was great, and I hope everything will stay great. I just don't understand why things are happening. I admit there may be some coincidences, but the server issues are obvious, and the team's approach to solving them is strange for me.
Tbh I agree with random network issues that's occurring with their DDos protection module. I've a ticket with them regarding some wireguard connectivity issues, which keeps reoccurring for the 3rd time now. I hope they find a fix for this once and for all
After speaking with our upstream @BackboneDirect and NeoProtect, they confirmed that the issue isn't our fault, nor is it related to them or some wrong routing, as we've already specified several times in the ticket.
We're now contacting GitHub to determine how to resolve the situation. As a temporary fix, simply run the command sent to you shortly in the ticket.
hello, the ticket ID is the same? so i can check what happend
With us there will always be an open door to dialogue, as long as there is respect.
This is going on for me as well, though only with one specific vps.
I purchased a Frankfurt vps when they ran a recent special, on a whim and because I had good experiences so far with a previous purchase.
This Frankfurt vps developed a ton of packet loss about 10 days ago and the solution was to move it to Amsterdam.
Well, not what I had in mind but since in either location it would be a backup it's fine, whatever.
However since that move from Frankfurt to Amsterdam several times a day they drop UDP for varying amounts of time.
I don't bother ticketing unless it's been a few hours because I have better things to do and I'm beginning to find the non-answers offensive.
You can quite clearly see NeoProtect in the path during these events, and it's absence when packets are flowing usefully.
Well hopefully the dialog and respect get us somewhere soon. Solutions would be good.
I think I understand the problem you're referring to, and we're already working on a solution.
Basically, when we receive carpet bomb attacks (attacks exceeding 300/400 Gbps+), traffic is redirected to NeoProtect to avoid causing damage, causing a 1-second micro disconnection. May i ask what your ticket ID is? or if you can a new one.
i think i can find a temp fix for this.
JKX-586505 - I might as well ask you to completely disable NeoProtect for my server if that'd solve these issues
The issue seems to have gone now btw. Do I really have to open a ticket everytime whenever I add a new server to my cluster and delux servers having connectivity issues with them?
Well, it's hardly "1-second micro disconnections" or I can't imagine I'd even notice. My UDP traffic seems to be effectively discarded, occasionally for hours though most often it's only for several minutes at a time.
I'm in the same UDP drops and low throughput, wireguard slow, ssh disconnects every few seconds or minutes, tickets opening and closing for some time boat. Hopefully this can be fixed. I don't want this to become a "you got what you paid", but if a functional VPS requires more funds then I'd gladly trade some euros for stability of an otherwise great performing VPS.
We thank you for your feedback, and as mentioned, we're working with our team to find a quick solution to this issue. If you have any tickets, I'd be more than happy to ask for your ID so I can review them quickly and provide a temp solution.
I will shortly check the tickets of those who have already sent their ticket ID
Well you're aware now that this is an ongoing problem for >1 customers. Hopefully enough people have chimed in on this issue that a general solution will be found before it comes up again.
A thing I've learned is I will absolutely avoid any (vps) hosts that lean on NeoProtect in the future as it's clearly not aligned with my quite basic network usage.
Of course, we are absolutely working on it and will do our best to resolve the situation, unfortunately, as you can imagine, it is not entirely up to us, so we will have to wait for feedback from Neoprotect which will certainly come soon.
I'm sorry for the inconvenience anyway.
IPv6 and rDNS is now online in Frankfurt
And where is the new Deal in Germany?)))
Servers delivered.
just done some restock
Wonder why there are so many issues.
what issue? at the moment we are ok with the uptime and other things.
thanks. It works ver good for me.