David @gilk,
You ask the same question back in September on this post and the question was answered
But let’s put this question to rest.
NO RealMac doesn’t impose any upload limits
Why on earth would they care about how often you change your live site. It’s not their bandwidth being used. There are thousands of users using Rapidweaver every single day on tens of thousands of sites hosted on almost every hosting company, and no one is being throttled by Rapidweaver.
Did you have an intermittent connection when you were browsing the Internet? Did you try any simple speed tests? Issues with email? Any app (including Rapidweaver) that is going to communicate (FTP, SFTP, HTTP, HTTPS, etc, etc ) uses the same gateway to connect with the Internet. If you’re not having issues with all connections then it’s probably not the issue.
There’s nothing magical happening here. Something changed that made things start working. If you didn’t change something then more than likely the host did.
The FTP protocol is ancient in the world of technology. It predates the Internet by over a decade. It was designed for private networks transmitting small amounts of data. It has zero security built-in, even login credentials including password are sent in the clear transmitted unencrypted. It’s easily and often hacked and Since FTP is unencrypted, man-in-the-middle attacks can and have been used to inject malware into software downloaded using FTP.
SFTP uses a secure shell (SSH), the same shell system administrators use to manage their servers. It creates a secure ”tunnel” and uses a completely different new file transfer protocol. It’s better designed to handle the larger amounts of data that today’s websites use. It does a lot less handshaking between the server and the client so it tends to be much more reliable.
Now, that being said, it’s not going to solve every publishing issue. If a Rapidweaver project doesn’t publish to your hosting company I’d probably first attempt to publish to a local folder. If you can’t publish locally you’ll never be able to publish to a remote server.
If you can publish locally without errors then you can always try a standalone FTP app like Transmit or FileZilla. All modern FTP apps support SFTP, so don’t be fooled by their name. If you can get a Transmit or Filezilla to work then you have a workaround until you figure out what RapidWeaver is having issues with.
Unfortunately, the publishing log part of RW doesn’t seem to be working with the latest release of RW (DevMate issue), so debugging publishing issues are going to be handicapped until that gets fixed.
If you can’t publish locally then there’s something wrong with something on one of the pages.