https://www.deployhq.com/support/api/users-api

These API endpoints allow you to manage users within your DeployHQ account. … **Tip**: You can explore and test these endpoints interactively using our [OpenAPI documentation](https … ://api.deployhq.com/docs). ## Permissions These endpoints require the authenticated user to have the … **Can manage users** permission enabled, or to be an account administrator. ## Available Endpoints

https://www.deployhq.com/support/api/profile-api

These API endpoints allow you to view and update your own user profile. … **Tip**: You can explore and test these endpoints interactively using our [OpenAPI documentation](https

https://www.deployhq.com/support/api/security-api

These API endpoints allow you to manage API keys for the authenticated user. … **Tip**: You can explore and test these endpoints interactively using our [OpenAPI documentation](https

https://www.deployhq.com/support/faq/deployhq-and-deploybot-merger

DeployHQ has merged with DeployBot to create a unified, more powerful deployment platform. ## Why … This merger allows us to combine the strengths of both platforms, providing you with a broader range … We are providing a smooth migration process for DeployBot users to transition to DeployHQ. … Our friendly support team is happy to help. … Feel free to reach out to us at support@deployhq.com and we'll get back to you as soon as possible.

https://www.deployhq.com/support/common-deployment-errors/no-such-file-open

This error is usually down to permissions. … is either invalid, or the path doesn't yet exist and the user doesn't have the permissions required to … An example of this error would be: ``` error: no such file open "/path/to/my/folder" ``` /path … to create it. … For further information about how to resolve this error please read this [article](Article: #231).

https://www.deployhq.com/support/common-deployment-errors/ftp-data-errors

This can vary according to the FTP server that has been installed, so you will need to check with your … server administrator to see what these ports are, and that they are allowed on the server's firewall … following IP ranges: * 185.22.208.0/25 * 2a00:67a0:a:1::/64 Alternatively, it may be easier to … It may be required to use passive (PASV) mode for file transfer, which can help with firewall issues … If you wish to use PASV mode with your server, **make sure that the associated ports are open**.

https://www.deployhq.com/support/build-errors/node-does-not-support-current-environment

your initial build command, most commonly when running `npm install`, you might run an error similar to … You might indeed find that this works locally when you run the same commands - the first thing to check … You may need to downgrade your language version within your DeployHQ project, to match the version running … https://your-domain.deployhq.com/projects/your-project/build_configuration If you've made changes to … the language version, it would be wise to [clear your build cache](https://www.deployhq.com/support/

https://www.deployhq.com/support/common-repository-errors/repository-list-empty

When you first create a project, you choose your repository host and are then taken to your repository … You may find that sometimes when adding a repository to a new project, the list of available repositories … to use is blank, or different from what you're expecting after entering your repository login details … Because the process involves adding an SSH key to the repository to give DeployHQ read access, the action

https://www.deployhq.com/support/common-deployment-errors/branch-not-tracked

This means that you have pushed to the master branch, but no servers on the project are set to automatically … Your repository host sends a request to us on a push to any branch, so DeployHQ will ignore branches

https://www.deployhq.com/support/common-deployment-errors/svn-tuncated-http-body

are using SVN for your version control you may come across one of the following errors when trying to … truncated HTTP response body. ``` ``` An error occurred: Timeout ``` This is usually down to … One way to resolve this would be to try deploying fewer commits at a time, for example instead of 10