Since the summer of 2023, I have been unable to upload my websites! Yes, you’ve read that right!
After 2 years of being unable to publish with Rapidweaver, my business is now ruined, so it’s just an academic question right now. Why has this been happening?
My provider says I open too many connections, and get banned by my own server, which I have been paying for, dutifully, each and every month. My reply has always been that I do not understand connections, have no interface to monitor them, cannot control them, and can only watch in agony as publishing gets halted at around 250-260 files being uploaded, with my IP banned for several hours, or even permanently.
It’s interesting that a loophole I found the last 2 years was to connect using a mobile data network (using my iPhone as hotspot) instead of an ADSL landline, but recently, even my mobile IP got banned as well.
Am I the only one whose business got killed by their own server banning them? What on earth is going on? How can this problem be prevented? Anyone?
Most web hosts have a limit to the amount of FTP connections that can be opened concurrently. I think the average limit is 5, but some web hosts allow less, some more.
Anyway once a file is uploaded that connection should close and new connection would open to upload the next file, but sometimes the connections don’t get properly closed and you end up with a lot of zombie connections, which I guess is what is happening here. I can’t really confirm without looking at your server logs.
You could ask your web host if they could increase your connection limit, but a lot of shared web hosts are hesitant to do that.
You can try to go into RapidWeaver’s publishing settings and set the Connections drop-down menu to something like 1 or 2.
Cyberduck! I have been using it to upload htaccess files and to remove obsolete folders.
Even when I use Cyberduck, I often get banned because apparently, Cyberduck, as soon as it launches, starts hammering port 7, he says. Again, I have no clue this is happening or how to prevent it.
Port 7 is not an FTP port. You can check in your CyberDuck settings to make sure the port is set to 21 if using FTP, or 22 if using SFTP. Or if your web host uses a custom FTP port, then whatever that port is (it shouldn’t be port 7 though).
Yeah, I am completely in the dark regarding this. All my Cyberduck projects utilize port 21. However, my provider insisted that I (Cyberduck) keeps hammering port 7 and bans me immediately. I am at a loss.
My first thought: how does your host “know” that it’s Cyberduck that’s doing the hammering? And how does your host “know” that RapidWeaver is opening all those connections?
It sounds to me that they “know” just enough to deflect any effort looking into the problem.
First of all, do they mention which protocol is sent over port 7 during the hammering? TCP or UDP?
TCP port 7 is the echo service, which simply reflects back whatever you send to it. It’s there for measuring connection speeds and to see if a node or endpoint is live. It’s also a target of many cheap and simplistic malware, who hope to bring down a server by making it echo millions of times per second.
UDP port 7 is used for WOL (wake-on-lan), which wakes up a remote machine so you can interact with it. Could it be that something on your local machine decides to ping port 7 on the server because it thinks it needs to wake it up?
