https://www.deployhq.com/support/network-agent-errors/destination-address-not-allowed

When attempting to configure, or deploy to a server using the DeployHQ agent, you may run into the following … error: ``` Destination address not allowed ``` This happens when you're trying to connect to … a server that isn't permitted to connect via the Agent. … In order to connect to another machine in your network, you'll need to add its local IP address to `~ … After changes are made to agent.access, you'll need to restart the agent.

https://www.deployhq.com/support/common-server-errors/deployment-key-errors

You may run into the following error when trying to configure a server in your project: ``` Command … failed to execute: Warning: Permanently added 'repo-host.com,1.2.3.4' (ECDSA) to the list of known hosts … contact it to obtain a list of branches to deploy from. … The later would happen if you'd uploaded your own custom private key to the project. … To resolve this, you'll just need to head to the **Configuration** area in your project, copy the public

https://www.deployhq.com/support/common-server-errors/ssh-public-key-authentication-errors

message when attempting to add a server to your project : "We couldn't access this server using the … public key to your server. … If you do upload a custom private key to your project, it will also need to be uploaded to any servers … : ```bash tail -f /var/log/auth.log ``` You may need to update your `LogLevel` to a high enough … the configuration, you will likely need to restart the sshd process for it to take effect.

https://www.deployhq.com/support/common-repository-errors/direct-fetching-of-commit-failed

If you have made changes to a submodule in your project but not pushed it to your remote, or you have … one of the following errors displayed during your deployment: ``` Fetched in submodule path ‘path/to … error: Server does not allow request for unadvertised object 123456 Fetched in submodule path 'path/to … To resolve this issue, you'll either need to navigate to the submodule directory and run git push to … Once these changes have been made, you'll need to push to your main repository before you can retry your

https://www.deployhq.com/support/common-repository-errors/no-url-found-for-submodule

found when initiating a deployment is either: ```bash fatal: No url found for submodule path 'path/to … when the repository is using files cloned from another repository but has had no mapping reference to … The mapping needs to be added to a .gitmodules file located in the root directory of the repository you … You can find out how to either map the submodule to its external source or remove it below. ## Submodule … , which will then be given access to multiple Github repositories.

https://www.deployhq.com/support/common-server-errors/network-is-unreachable

When attempting to add or update a server in DeployHQ, you may run into the following error: ```bash … Network is unreachable ``` This may relate to the server `hostname` that you have entered. … You need to check that the hostname resolves to a publicly accessible IP range, and not a private IP. … If your the DNS for hostname has been configured to point to a private IP address, it will not be possible … to connect to it.

https://www.deployhq.com/support/notifications/e-mail

E-mail notifications can be set up deployments to inform you when it has completed. … the notification which is particularly useful if you're wanting to notify people that aren't users on … your account. ## Setting up email notifications To enable E-mail notifications, head to any project … in your account, then to the **Settings** tab on the left hand side. … any setting you wish to only apply to this particular server.

https://www.deployhq.com/support/faq-deployments

These activities can span from moving code from a repository to a server, to performing build operations … - **What does it mean to deploy code? … DeployHQ allows you to deploy to all 4 types by offering a flexible connection system with all types … Deployments happen to the inactive environment, which is then switched to become the live one. … making it available to everyone

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

We are providing a smooth migration process for DeployBot users to transition to DeployHQ. … Detailed instructions will be provided to ensure a seamless switch. ## Can I still log in to my DeployBot … New signups are directed 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/couldnt-access-repository-please-ensure-authentication

. ``` Firstly, if using SSH to connect, you'll need to make sure your SSH key is added to your repository … If you need to update your repository details, you can [follow this guide](https://www.deployhq.com/support … If you're connecting to a self-hosted repository (GitLab etc.) then this may use a different port. … ) to enable DeployHQ to connect. ### Build dependencies You may also see this error whilst running … To rectify this, you'll need to make sure your deploy key has been added to the dependant repository.