Troubleshooting

Common issues and how to resolve them. Start with the quick diagnostic below, then expand the relevant section for details.

Quick Diagnostic

1. Check deployment status — Open your environment page. If status is ERROR, click View Output to see what failed.
2. Check webhook delivery — In your Git provider, go to the webhook settings and check the delivery history for failed requests.
3. Check variables — After adding or changing variables, you must redeploy the environment for changes to take effect.

Deployment Issues

Webhook not triggering deployments

• Verify the webhook is Active in your Git provider settings
• Check that the correct events are selected (Pull Request events for Bitbucket/GitHub, Merge Request events for GitLab)
• Confirm the Webhook URL and Secret match exactly what Nebion shows (no extra spaces)
• Check the webhook delivery history in your Git provider for error responses
• Verify the Deploy Key is added to your repository

Deployment fails

• Click View Output on the failed deployment to see the error details
• Check that .nebion.yml exists in your repository root and is committed to the branch
• Verify the service names in .nebion.yml tasks match your docker-compose-nebion.yml services exactly
• Test your post-rollout commands locally (e.g., docker compose exec php drush cim -y)
• Check that your docker-compose-nebion.yml has valid syntax

Environment not accessible after deployment

• Confirm the deployment status is SUCCESS
• Wait a few minutes for DNS propagation
• Verify the URL matches the expected pattern (pr-{number}.{domain})
• Click View Output on the deployment to check for container startup errors
• Try a hard refresh in your browser (Ctrl+Shift+R)

Environment not created from pull request

• Verify your webhook is configured correctly (Bitbucket / GitHub / GitLab)
• Check webhook delivery history in your Git provider for failed deliveries
• Ensure the PR is targeting the correct repository that's linked to your Nebion project
• Contact your administrator to check system logs

Configuration & Access

Variables not taking effect

• After adding or changing variables, you must redeploy the environment
• Click the Deploy button on the environment's Overview tab
• If still not working, try deploying with Reset environment checked
• Verify the variable appears in the Custom Variables section on the Variables tab

Cannot view logs

• Refresh the page
• Make sure at least one deployment has completed successfully
• Try changing the Period filter to a wider range
• If selecting a specific service shows no results, try All Services

CLI: Login fails

• Run nebioncli logout then nebioncli login to start fresh
• Make sure your browser can reach the Nebion login page
• Check that you're using the correct instance URL (--host flag)

CLI: SSH connection fails

• Run nebioncli login to ensure you're authenticated
• Delete SSH keys and retry: rm ~/.config/nebioncli/id_*
• Verify the environment is deployed and running (status SUCCESS)
• Check that the container you're trying to connect to exists

Getting Help

If you cannot resolve the issue:

1. Note the project name and environment affected
2. Copy any error messages from View Output or the CLI
3. Take a screenshot of the issue
4. Contact your system administrator with these details