Skip to content

FAQ#

I found a bug! 🐞#

If you've found a bug, please raise a GitHub issue for it, or contact your Lagoon administrator.

I found a security issue! 🐞#

If you've found a security issue, please send your findings to security@amazee.io. Please DO NOT file a GitHub issue for it.

I'm interested in amazee.io's hosting services with Lagoon#

That's great news! You can contact them via email at sales@amazee.io.

I'm getting an invalid SSL certificate error#

The first thing to try is what is listed in our documentation about SSL.

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.

I'm getting an "Array" error when running a Drush command#

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!

I'm seeing an Internal Server Error when trying to access my Kibana logs#

No need to panic! This usually happens when a tenant has not been selected. To fix this, follow these steps:

  1. Go to "Tenants" on the left-hand menu of Kibana.
  2. Click on your tenant name.
  3. You'll see a pop-up window that says: "Tenant Change" and the name of your tenant.
  4. 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 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: https://pygmystack.github.io/pygmy/troubleshooting/

How can I check the status of a build?#

How do I add a cron job?#

How do I add a new route?#

How do I remove a route?#

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.

When I run pygmy status, no keys are loaded#

You'll need to load your SSH key into pygmy. Here's how: https://pygmystack.github.io/pygmy/ssh_agent

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: https://pygmystack.github.io/pygmy/troubleshooting

My deployments fail with a message saying: "drush needs a more functional environment"#

This usually means that there is no database uploaded to the project. Follow our step-by-step guide to add a database to your project.

When I start Pygmy I see an "address already in use" error?#

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:

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.

How can I change branches/PR environments/production on my project?#

You can make that change using the Lagoon API! You can find the documentation for this change in our GraphQL documentation.

How do I add a redirect?#

How can I add new users (and SSH keys) to my project/group?#

This can be done via the Lagoon API. You can find the steps documentation for this change in our GraphQL documentation.

Can an environment be completely deleted to roll out large code changes to my project?#

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, Don’t forget to re-sync!

It is possible to delete an environment via GraphQL. You can find the instructions in our GraphQL documentation.

How do I get my new environment variable to show up?#

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.

How do I SFTP files to/from my Lagoon environment?#

For cloud hosting customers, you can SFTP to your Lagoon environment by using the following information:

  • Server Hostname: ssh.example.com
  • Port: 22
  • Username: <Project-Environment-Name>

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: https://github.com/uselagoon/lagoon-sync

Authentication also happens automatically via SSH Public & Private Key Authentication.

I don't want to use Let's Encrypt. I have an SSL certificate I would like to install#

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 set the tls-acme option in .lagoon.yml to false.

Is it possible to mount an external volume (EFS/Fuse/SMB/etc) into Lagoon?#

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 Dockerfile), and ensuring the volume mount is connected via a pre- or post-rollout task.

Is there a way to stop a Lagoon build?#

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.

We installed the Elasticsearch\Solr service on our website. How can we get access to the UI (port 9200/8983) from a browser?#

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 http://localhost:<port> in your browser.

I have a question that isn't answered here#

You should contact your Lagoon administrator for any hosting-related enquiries, but you can also reach out to the Lagoon team via Discord or email at uselagoon@amazee.io.