X4B.ORG - Reverse Proxy Hosting - Hide your Server IP (Russia, Sweden, USA, Romania)

Status
Not open for further replies.
Currently the best latency is generally the Romanian node, however the Swedish node is the next best preferred for the law in Romania has a number of caveats. We plan to introduce a node at Ecatel in with the launch of the new system (NL has the best latency to most of EU).

Generally the node which has the least ping from your server is the best choice (you can test using the IPs I provided)
 
I would love to see a 3rd Russian Node and/or a 2nd Swedish Node. NL is no longer a good choice. BREIN is f***ing everything up lately ...
 
Another RU node isnt necessary yet we have plenty of room for expension on each node. The only reason for the second node is a bit of redundancy for people who do DNS load balancing/redundancy.

Currently all nodes have IPs free and bandwidth to spare. (SE gbit/1tb, RU 100mbit/3tb each)

NL is great to a point, Ecatel being the main data-center in that region for quality hosting. We actually used to be with them till our vps provider closed down.
 
You should also look at Ukraine, UA. I was with MHost.ua (until they were arrested on unrelated money laundering charges lol) and got Abuse/DMCA complaints through the roof. Not that they cared ... as long as it is not porn, UA is VERY safe!
 
Biggest problems with Ukraine (although at various stages Ive been close to purchasing):
- High bandwidth costs/low speeds. We use alot of bandwidth, its our major resource.
- Payment processors, no paypal and most of the credit card processors require visa plus which is not an option currently.

So far since begining this service ive received a total of 4 complaints for RU/SE services so complaints are not an issue.
 
That's true ... however I switched all to the Russia_2 Node now and I must say, that it's all good now and it is faster (for me) then the Sweden Node. Anyway, I am glad my sites load fast again :)


... or not :(
As soon as morning hit, it all went bust again. During late-night, all was super fast :(
 
Last edited:
So far since begining this service ive received a total of 4 complaints for RU/SE services so complaints are not an issue.

Per se, you "should" not really receive complaints i.e. they don't really apply to you. You are proxying traffic, that's it. You don't offer domains or DNS or hosting. How a DMCA notice would ever be applicable to you, is beyond me, cause you cannot remove the content, since you don't host it and you also cannot switch off the traffic of 10 or 20 websites just cause some copyrighted material has been sighted on one of them ...
 
Strictly speaking we need to comply with DMCA to get service provider protection, we foward what little abuse I get to customers and require enforcement.


I have to be honest, the Gateway errors are a bit annoying.
Gateway errors are caused by an invalid response by your server. This happens mostly with HTTP/1.1 requests, try disabling keepalive (advanced features dialog)
 
Sweden Node 1 is down, its a data center issue. We are waiting for them to resolve the connectivity problems. Should be resolved within 12-24hours we hope.
 
that is generally not an error on our side, if you want me to look into it you will need to provide more infomation that this (I dont know who you are, I need your IP).

Oh and just FYI the swedish node was fixed last night.
 
Swedish Node is still up/down
Russia 1 or 2 are responding but very slow
Switched to Romania which is still working normally
If that fails too, then I don't know what to do ...
 
Swedish Node is working fine, the issue was solved.
There is a slight issue with keepalive with some servers, this will be fixed in a day or two. If you are experiencing issues try setting keepalive to 0 in the advanced options.
 
I disable keepalive and cache always anyway. Please read my PM, I would be willing to contribute financially to my proposal too ...
 
Currently we dont have a VIP system, we are working on a new billing system, which I hope to release in january (it has both plans and PAYG) as well as a new server base system and monitoring.

If you have both keepalive and cache disabled there shouldnt be any issues on our end (the code is well tested). Howeaver it may be fixed in the upcoming upgrade (the currently server version is a old patched version, we are going to be upgrading to latest development stable). Currently testing the new version now, providing everything goes well it will be pushed out to nodes in a day or two.
 
Swedish Node 1 is running the new server software, the others will get it once its been adequately tested on this node.

So far it appears a bit faster due to reduced memory usage (caused by HTTP/1.1 chucked requests). Keep alive should be stable so you can experiment with turning it on if you wish.
 
Status
Not open for further replies.
Back
Top