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
Can you give me the ticket number? so we can check. thanks
Yes, you can disable it. If you open a ticket, we can deactivate it.
In recent years, we have carried out a lot of monitoring and the average traffic per customer was around 5/6TB per month, so we have adopted a range of up to 10TB; the latter is increased (not by hundreds) for free.
Here is an example: #LTM-222972
Ticket #FQN-383264 (which is actually a continuation of the first ticket, since it was automatically closed when support replied). In the first ticket, I was asked why I needed to modify that file, but I was unable to reply due to it being closed. That is why I opened this ticket (but it also auto-closed).
Can I please get 100 Mbps unmetered? Or 80 Mbps unmetered at minimum. I do not need any higher speed, but I can't have the network get suspended.
You respond to tickets?
A very strange hosting service that doesn't allow card payments. A PayPal account is required for payment.
In fact, this is already on PayPal's side. for some countries, account registration is not required and you can pay by card
Always exciting to see a fresh face stepping into the DDoS protection space.
Paypal payments from India is not accepting, any other payment option available ?
I paid using crypto.
Ticket #KLO-461843 can u check this pls?
Thank you for the budget offer!
Is anyone else suffering serious TCP connectivity issues with XeniaHosting?
Yep, connection is not stable. I even need a few attempts to connect to the ssh. Beszel is constantly disconnecting.
Do you think you could run this twice and tell me the output?
Sure, I get nc.openbsd: command not found
Or just use traditional netcat: replace
nc.openbsd -w10 -vzwithnc -w10 -nvz. I just personally prefer the other one.First run:
(UNKNOWN) [216.218.219.41] 443 (https) open
(UNKNOWN) [204.13.164.118] 443 (https) open
(UNKNOWN) [193.23.244.244] 443 (https) : Connection timed out
(UNKNOWN) [66.111.2.131] 9001 (?) open
(UNKNOWN) [45.66.35.11] 443 (https) open
(UNKNOWN) [217.196.147.77] 443 (https) open
(UNKNOWN) [171.25.193.9] 80 (http) open
(UNKNOWN) [128.31.0.39] 9201 (?) open
(UNKNOWN) [131.188.40.189] 443 (https) open
(UNKNOWN) [199.58.81.140] 443 (https) open
Second run:
(UNKNOWN) [216.218.219.41] 443 (https) open
(UNKNOWN) [204.13.164.118] 443 (https) open
(UNKNOWN) [193.23.244.244] 443 (https) : Connection timed out
(UNKNOWN) [66.111.2.131] 9001 (?) open
(UNKNOWN) [45.66.35.11] 443 (https) open
(UNKNOWN) [217.196.147.77] 443 (https) open
(UNKNOWN) [171.25.193.9] 80 (http) open
(UNKNOWN) [128.31.0.39] 9201 (?) open
(UNKNOWN) [131.188.40.189] 443 (https) open
(UNKNOWN) [199.58.81.140] 443 (https) open
Interesting... This is what I get on the first run:
And the second:
That looks like yours isn't suffering the severe packet loss mine is (the third IP is actually down right now).
What subnet are you on? I'm on 37.202.205.0/24.
Same subnet. Seems like I am a bit more lucky but I must say that the server is pretty much unusable even with this 'luck'. I cannot even monitor is properly.
I have an open (and unanswered) ticket from several days ago. Hopefully they'll respond eventually.
Good luck. I am not going to renew this server.
FWIW here's the results I got (with "traditional" nc):
nc: connect to 216.218.219.41 port 443 (tcp) failed: Operation timed outnc: connect to 204.13.164.118 port 443 (tcp) failed: Operation timed outConnection to 193.23.244.244 443 port [tcp/*] succeeded!Connection to 66.111.2.131 9001 port [tcp/*] succeeded!Connection to 45.66.35.11 443 port [tcp/*] succeeded!Connection to 217.196.147.77 443 port [tcp/*] succeeded!Connection to 171.25.193.9 80 port [tcp/*] succeeded!nc: connect to 128.31.0.39 port 9201 (tcp) failed: Operation timed outConnection to 131.188.40.189 443 port [tcp/*] succeeded!Connection to 199.58.81.140 443 port [tcp/*] succeeded!Other remarks:
Well, I did stay a few months longer and my main points not really liking that @XeniaHosting VPS are
In case anyone here knows about a good european provide who offers a reasonably decent VPS in Italy for an attractive price (<= € 25/yr), PayPal as payment option, annual deals, a few days (3 to 7) test, Epyc preferred but Xeon Scalable is acceptable, let me know, please.
Maybe LakeNetworks? CPU is Xeon Gold 6138. Without a promo, they're €35.28/yr for 2c2g20g. On OGF they ran a 1c1g10g promo for €13.50/yr. They can do annual billing. Not sure if they accept Paypal but they do accept bank transfer and card for sure. YABS here: https://lowendtalk.com/discussion/comment/4817776/#Comment_4817776
(Beware that Xenia is one of their upstreams, but they don't seem to be having the connectivity issues XeniaHosting is)
Not really, I had a ton earlier (ssh doesn't connect from the first try), though it seems better in the last few days.
They were under heavy DDoS recently, but no longer. That was probably it.
What's your output of
sysctl net.ipv4.ip_local_port_range? Because apparently both LakeNetworks and XeniaHosting block any outgoing SYN with a source port lower than 15001, which is stupid.I just fixed the issues on both of those providers by shrinking the port range (I had previously expanded it).
net.ipv4.ip_local_port_range = 32768 60999Mine was
10000 64999. I fixed the issues by changing it to15001 64999at the expense of being able to hold open 5000 fewer connections, which shouldn't be an issue. I'm no longer experiencing any packet loss.Funny that I had to figure it out myself while both providers spent weeks of saying "we made some changes, how about now?" without success.
Hello, XeniaHosting!
Could you please check Ticket #CHN-386279?
I opened this ticket 8 hours ago regarding severe network routing issues on my VPS . The server suffers from 70%+ packet loss, global TCP resets.
Since the server was delivered unusable and there has been no update on the ticket, I have updated it with a cancellation and refund request.
Thank you!
Oops, meant 31501.
If you post some pcaps, I might be able to help troubleshooting.
Oh, never mind then. You only waited 8 hours after submitting the ticket before requesting a refund?