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
Works fine for me.
I'm aware that it works fine for some people, but I'm curious as to why it's not working for me, as well as some VPN connections....
@QuadHost
@QuadHost
Have you considered opening a ticket with them? Just an idea...
Yes, I have opened a ticket with them.
Great thing! That's the spirit!
Magic.
Uhhhh....okay
Their main site IP looks to be under clouvider ddos mitigation, so routes might not have updated in some locations?
@linuxthefish
Oh it is? Maybe that's what happened. Hm.
Run a traceroute and see where it stops?
The IP address that I get after tracerouting is one that belongs to Clouvider, I guess it is DDoS protection
oh, no! their VPS panel still UP, who care about their website ? (their website just fine)
More likely NTT's Arbour platform has identified the connection as suspicious and blacklisted @karatekidmonkey IP.
QH is under SYN flood, and as such excessively refreshing the website (especially when you have a number of plugins in your web browser that created even more connections) when it's loading and being authenticated by the scrubbers sends the IP to the blacklist, as the traffic you generate is too similar to the attack they are receiving.
If you got blacklisted by NTT for that reason, you'd normally not reach Clouvider's network in the traceroute, and the last reachable hop would be somewhere in the NTT's network.
If this is the case feel free to contact QuadHost or our NOC directly (https://www.clouvider.co.uk/contact-us), we will be happy to ask NTT to whitelist your IP.
IPv6 is not working on that website:
so when a client tries to use IPv6, it will hang for a long time.
Also I can't load it via Squid proxy, because Squid currently doesn't fall back to IPv4 as it should.
Probably deployed v6 years ago and then stopped caring or verifying that it actually works.
Apologies to everyone for the delay in response here, we figured you would all appreciate our efforts in resolving the issue rather than visiting a 3rd party forum.
@karatekidmonkey more than likely as @clouvider suggested you were picked up as a false positive by the protection during the attacks.
Only our main site was hit by the attacker, all client VM's and systems remained online.
Correct it wasn't, and is now resolved...
Thats your opinion that you are free to have however it is not the case.
It would be ideal if you could do both, but yeah I guess solving the issue is better
That's probably true, I have quite a few browser addons that create additional connections to the servers. During that time I just setup openvpn on one of your i-83 nodes and used it to access the client area
Issue solved at this point.