We can not stress enough how important it is to obtain the correct publishing credentials from you web hosts, as this is the main cause of publishing issues for 99% of users.
In RapidWeaver, choose File > Publishing Settings (Command-K) and check that all the fields are entered correctly: Server, Username, Password, and Path.
Entering an incorrect Path is a common cause of publishing problems in RapidWeaver. Some common site paths may include:
This is by no means an exhaustive list and paths can vary greatly between different hosts, so if you're still experiencing issues, please consult your webhost's online help to determine the Path required to upload to the correct folder.
You may even want to contact your webhosts directly and ensure that they have not made any recent changes to the server which may have affected your settings and that you are still within your upload quota.
Different Server Configurations
RapidWeaver has a number of options to configure publishing - particularly if you’re using FTPS uploading. Please try the each of the options available, as some hosting providers require specific settings. Due to the nature of how FTP works, RapidWeaver cannot reliably detect the correct settings that you should use.
Check for Limits on Concurrent Connections
If your host limits the number of connections which can be made to your server, you can set RapidWeaver 7 to use a smaller number of connections when publishing.
“Couldn’t connect to your FTP server” Error
If RapidWeaver consistently displays this message when publishing, try disabling Extended Passive Mode – which is enabled by default in the FTP Publishing Setup.
To do this, show the Publishing Setup window (Command-K), select the settings button next to the FTP Protocol field, then choose to disable the Use Extended Passive Mode option.
Publishing Issue Checklist
- Make sure your publishing details are correct, use the "Reveal" password option to check it's entered in correctly. This is one of the most common errors.
- If you're using FTP, the "Mode" should usually be set to "Extended Passive (Default)" (Try both when testing).
- If you're using SFTP make sure there is a path in the Path directory, such as "/".
- Try entering your FTP credentials into another FTP client (Forklift, Fetch, Transmit, CyberDuck, Interarchy, or YummyFTP), and see if you can make a connection. If this also fails it probably means your credentials are incorrect. You should contact your host for support and to check your ftp details.
- If the "Test" button reports that your details are correct, but you're still having issues publishing try updating the Path by using the "Browse" button. This can often fix any publishing issues you may be having.
If Publishing and Export seem slow…
RapidWeaver will no longer have to process every page to consolidate and minify things, export and publish should be significantly quicker.
If your connection keeps timing out…
It could be something slowing down the connection to the FTP server. It could be something on your connection, or it could be the server itself. It probably isn't an issue with RapidWeaver.
Open Terminal.app on your Mac and type ping yourserver.com (where yourserver.com is the value you entered in the "Host" field of the Publishing screen), then press enter.
If these take a long time to return, or they time out completely, you'll want to speak to your web host.
Another test would be to try ping 184.108.40.206 - that's Google's server, and it's always pretty quick. If that returns quickly, but the one to your server returns slowly, then it must be your server. If they both return slowly, then there's something going on with your connection.
Error Message when Exporting
If you’re seeing an error message when exporting your site, this may mean that there’s a problem with either an addon or a resource in your project. If an error message appears consistently when exporting a particular page, take a look at the page - are there any resources missing, or a particular stack that may be causing a problem?
Couldn’t upload to your FTP server
If RapidWeaver stops publishing part way through with one of the following errors: "Couldn't upload to your FTP server", "URL using bad/illegal format or missing URL" or "Operation was aborted by an application callback.". This is often because of missing resources.
To fix this issue, check that all your resources are correctly linked. Once you've done that, try re-publishing again.
Still having issues? Let us help.
If you've tried the above and are certain your FTP details are correct, please gather the following information and email email@example.com - We know the following information seems like a lot, but when we can't replicate something it makes it really really hard to fix. The more information we have, the more likely we'll get it fixed.
- What machine / OS / RW version are you using?
- Who are you hosting your website with?
- Which, if any, third-party add-ons are you using with your project?
- What publishing type are you using (FTP, SFTP, FTPS, local folder)?
- At what point does it go wrong?
- Does RW show an error message?
- Your FTP logs (see below)
- A video showing the problem in action
- Your RapidWeaver Project File
- Your FTP login details so we can test the issue here.
- Confirmation that you can log in with your details using a third-party FTP client.
RapidWeaver can be configured to produce a more in-depth report about publishing that the Realmac Software support team can use to identify potential problems.
- First of all open RapidWeaver’s preferences (Cmd,) and select the Publishing preferences pane.
- Make sure that the Enable Upload Logging option is checked.
- Quit RapidWeaver.
- Re-open your project in RapidWeaver.
- Attempt to republish your RapidWeaver project by choosing File > Re-Publish All Files.
- If the publishing feature returns an error, go to the Help menu, and choose Copy Support Logs.
- Finally, please paste the logs copied to the clipboard into your message.
To get the FTP logs from RapidWeaver, you have to turn it on in RapidWeaver preferences before performing a publish.
It might be an idea to turn off "Show Notifications" too, otherwise, the publishing window may automatically close. When the publishing fails, click the "Send Upload Logs" button.