Publishing errors can be frustrating roadblocks in your workflow, especially when you're close to finalizing your Vev project. Often, these errors are accompanied by messages in red and they can give you a key to understanding what went wrong. In this article, we have categorized them by type, possible cause, and suggested solutions.
FTP & SFTP Related Errors
Error message | Possible cause | Suggested solution |
Error: 550 Can't change directory to 1470405: Operation not permitted | The directory specified in the hosting settings is not accessible. | The user needs to address the issue on their end. |
Error: AccessDenied | Access Denied | Wrong login or FTP user does not have access. | The user needs to address the issue on their end. |
Error: connect: getConnection: All configured authentication methods failed | This occurs with SFTP when all methods of connecting to the server fail. It can be due to incorrect credentials or a blocked port on the client's server. | The user needs to address the issue on their end. |
Error: 550 Can't change directory to 1470405: Operation not permitted | The directory specified in the hosting settings is not accessible. | The user needs to address the issue on their end. |
S3 Related Errors
Error message | Possible cause | Suggested solution |
Error with wrong or missing credentials. | The credentials entered in your hosting settings may be incorrect or lack the necessary permissions to write to the specified bucket. | The user needs to address the issue on their end. |
Error: undefined | The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint. | The bucket could be located in a different region than the one specified. | The user needs to address the issue on their end. |
Webhook Related Error
Error message | Possible cause | Suggested solution |
Error message numbered with 400-500 accompanied with varying message. | The webhook server is responding with the error message. | The user needs to address the issue as it's their webhook server responding with the error message. |
Vev Related Errors
Error message | Possible cause | Suggested solution |
Error: An error occurred while publishing your project: network timeout. Please try again. If the problem persists, contact Vev Support. | It's unclear why this occurs, but it's likely related to the Vev backend, potentially due to an API responding slowly or an unusual external factor. | If the issue continues after trying to publish again, please contact our support team. |
Error: An error occurred while publishing your project: Evaluation failed: DOMException: Failed to set the 'cookie' property on 'Document': Access is denied for this document. Please try again. If the problem persists, contact Vev Support. | This error happens during project pre-rendering failure, usually triggered by an element in the project attempting an unusual operation. | If you suspect the issue is related to a custom element you've developed and are unsure how to resolve it, please reach out to our support team. |
Error: An error occurred while publishing your project: fetch failed. Please try again. If the problem persists, contact Vev Support. | The cause of this issue is uncertain, but it might be related to API rate limiting. Attempting to publish again usually resolves the problem. | Attempt to publish again; should the problem persist, please get in touch with our support team. |
Error: No files to upload, something may be wrong. | This typically indicates that there are no pages available for publishing in the project, often because all pages have been marked as not ready. | Make sure that all pages are marked as ready for publishing. If the issue remains, please contact our support team. |
Error: An error occurred while publishing your project: Cannot set properties of null. Please try again. If the problem persists, contact Vev Support. | The issue likely stems from a problem encountered during the project's pre-rendering process, possibly due to a custom-coded element, but the exact cause is uncertain. | Please contact our support team. |