wholebad.blogg.se

Error could not connect to server filezilla
Error could not connect to server filezilla




error could not connect to server filezilla error could not connect to server filezilla

So please, drop the dramatic "It's getting out of hands, oh noes!" (paraphrasing here), read up on internet routing and research the costs of hosting a high speed connection and understand that we, a community entirely based on member contributions and dedication, can't do much about it. Mind you, the archive is hosted off a home connection at our own cost, I can as much control the speed and latency to members with slow connection speeds as I can control my speeds to say the US or any other country. ISP routing is not something we can control in any way unless we pay a good deal of money needed to buy a dedicated connection and multisite setup to cover all major routings.

error could not connect to server filezilla

Maybe the routing was slightly better before which yielded better speeds, but again, completely out of my or Andys control. In both cases, most likely slow ISP routing. It could be between the file server and the main BA server, or between the BA server and users. Although my connection speed has been lowered by 90% I rarely saturate my full upload, which means the problem is elsewhere. It's getting out of hand? This affect only a handful of people, just looking at the traffic at the time of writing this we have multiple members pushing well over 500-600KB/s totaling several MB/s, at times I've seen several MB/s from single members. When this can be fixed, this is seriously getting out of hand






Error could not connect to server filezilla