Project: Lagoon (App Definition and Development / Application Definition & Image Build)
File: faq.md

You should have a private Slack channel that was set up for you to communicate - if not, or you've forgotten how to contact us, reach out at . If you've found a bug or security issue, please send your findings to . Please DO NOT file a GitHub issue for them. That's great news! You can contact them via email at . We have backups available for files and databases, typically taken every 24 hours at most. These backups are stored offsite. We keep up to 7 daily backups and 4 weekly backups. If you ever need to recover or restore a backup, feel free to submit a ticket or send us a message via chat and we will be more than happy to help! <iframe width="560" height="315" src="https://www.youtube.com/embed/bluTyxKqLbw" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe> The first thing to try is what is listed in . If you follow those steps, and you are still seeing an error, please submit a ticket or send us a message on chat and we can help resolve this for you. This was a bug that was prevalent in Drush versions 8.1.16 and 8.1.17. There error would look something like this: ```bash The command could not be executed successfully (returned: Array [error] ( [default] => Array ( [default] => Array ( [driver] => mysql [prefix] => Array ( [default] => ) , code: 0) Error: no database record could be found for source @main [error] ``` Upgrading Drush should fix that for you. We strongly suggest that you use version 8.3 or newer. Once Drush is upgraded the command should work! <iframe width="560" height="315" src="https://www.youtube.com/embed/BuQo5J0Qc2c" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe> No need to panic! This usually happens when a tenant has not been selected. To fix this, follow these steps: Go to "Tenants" on the left-hand menu of Kibana. Click on your tenant name. You'll see a pop-up window that says: "Tenant Change" and the name of your tenant. Go back to the "Discover" tab and attempt your query again. You should now be able to see your logs. I'm unable to SSH into any environment. I'm getting the following message: `Permission denied (publickey)`. When I run `drush sa` no aliases are returned. This typically indicates an issue with Pygmy. You can find our troubleshooting docs for Pygmy here: <iframe width="560" height="315" src="https://www.youtube.com/embed/PyrlZqTjf68" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe> <iframe width="560" height="315" src="https://www.youtube.com/embed/Yd_JfDyfbR0" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe> <iframe width="560" height="315" src="https://www.youtube.com/embed/vQxh87F3fW4" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe> Lagoon will detect the removal of routes from your `.lagoon.yml` during a deployment. Check the deployment logs to confirm that the routes were removed automatically or for instructions on how to remove them. You'll need to load your SSH key into pygmy. Here's how: This typically indicates an issue with

You can find our troubleshooting docs for Pygmy here: This usually means that there is no database uploaded to the project. . `Error starting userland proxy: listen tcp 0.0.0.0:80: bind: address already in use Error: failed to start containers: amazeeio-haproxy` This is a known error! Most of the time it means that there is already something running on port 80. You can find the culprit by running the following query: ```bash title="" netstat -ltnp | grep -w ':80' ``` That should list everything running on port 80. Kill the process running on port 80. Once port 80 is freed up, Pygmy should start up with no further errors. You can make that change using the Lagoon API! You can find the documentation for this change . <iframe width="560" height="315" src="https://www.youtube.com/embed/rWb-PkRDhY4" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe> This can be done via the Lagoon API. You can find the steps documentation for this change . Environments are fully built from scratch at each deploy, dropping the old database and files and pushing your code would result in a fresh clean build, Dont forget to re-sync! It is possible to delete an environment via GraphQL. You can find the instructions . Once you've added a runtime environment variable to your production environment via GraphQL, then all you need to do a deploy in order to get your change to show up on your environment. For cloud hosting customers, you can SFTP to your Lagoon environment by using the following information: Server Hostname: `ssh.lagoon.amazeeio.cloud` Port: 32222 Username: &lt;Project-Environment-Name&gt; Your username is going to be the name of the environment you are connecting to, most commonly in the pattern `PROJECTNAME-ENVIRONMENT`. You may also be interested in checking out our new Lagoon Sync tool, which you can read about here: Authentication also happens automatically via SSH Public & Private Key Authentication. We can definitely help with that. Once you have your own SSL certificate, feel free to submit a ticket or send us a message via chat and we will be more than happy to help! You will need to send us the following files: Certificate key (.key) Certificate file (.crt) Intermediate certificates (.crt) Also, you will need to . Mounting an external volume would need to be handled completely inside of your containers, Lagoon does not provide a provision for this type of connection as part of the platform. A developer can handle this by installing the necessary packages into the container (via the ), and ensuring the volume mount is connected via a . If you have a build that has been running for a long time, and want to stop it, you will need to reach out to support. Currently, builds can only be stopped by users with admin access to the cluster. <!-- markdown-link-check-disable-next-line --> We suggest only exposing web services (NGINX/Varnish/Node.js) in your deployed environments. Locally, you can get the ports mapped for these services by checking `docker-compose ps`, and then load `:<port>` in your browser. You can reach out to the team via or email at .