> For the complete documentation index, see [llms.txt](https://docs.realmacsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmacsoftware.com/classic/user-manual/publishing/how-to-fix-publishing-issues/upload-errors.md). # Upload Errors Upload errors and how to solve them When publishing fails you might see one of the following issues, here's what they mean and how to fix them. ### Unable to upload file, the server may be out of disk space. This error is exactly what it sounds like. Your web server has run out of space. You can either contact your hosting company to upgrade your plan and increase the server space. Or delete some files from your server using an FTP client such as Transmit from Panic. ### Couldn't upload to your FTP server (Retry in 5s) This can sometimes mean the login credentials are correct, but the **Path** you specified is not right. Re-enter the Path into the Publishing setup and press “Browse” to confirm the location.\ \ Once this has been done, RapidWeaver will show a **Change Publishing Path?** dialogue. Press the **Change and Re-Publish** button, this should resolve the issue. ### Couldn’t connect to your FTP server 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 FTPProtocol field, then choose another publishing Mode option until you find one that works for you. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.realmacsoftware.com/classic/user-manual/publishing/how-to-fix-publishing-issues/upload-errors.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.