Powered by

# Troubleshooting Guide

This guide provides solutions to common issues encountered during the configuration and deployment of your application using StationOps. It includes potential causes and step-by-step solutions to resolve them efficiently.

# General Issues

# Wizard is Not Loading

Possible Causes:

  • Browser cache issues
  • Slow or unstable internet connection
  • Server downtime
  • Ad-blockers or browser extensions interfering

Solutions:

  1. Clear your browser cache and hard refresh the page.
  2. Try using a different browser or open an incognito window.
  3. Disable any ad-blockers or browser extensions that may interfere with scripts.
  4. Check StationOps Status for any ongoing server outages.
  5. Restart your router to rule out connectivity issues.

# Organization Setup Issues

# Unable to Create an Organization

Possible Causes:

  • Organization name already exists
  • Account lacks the necessary permissions

Solutions:

  1. Choose a unique organization name that isn’t already in use.
  2. Verify that your account has the necessary permissions to create an organization.

# Project Setup Issues

# Project Creation Fails

Possible Causes:

  • Invalid project name
  • Connectivity issues

Solutions:

  1. Ensure the project name follows the naming conventions (use only letters, numbers, and dashes).
  2. Check your internet connection and try again.

# AWS Configuration Issues

# AWS Authorization Fails

Possible Causes:

  • Incorrect AWS credentials
  • Insufficient IAM permissions
  • MFA (Multi-Factor Authentication) required but not entered

Solutions:

  1. Double-check your AWS credentials and ensure they are correctly entered.
  2. Verify that your IAM role has the required permissions for StationOps.
  3. If MFA is enabled, ensure you enter the correct authentication code.

# Git Repository Connection Issues

# Unable to Connect Git Repository

Possible Causes:

  • GitHub permissions issue
  • Repository not found or private
  • Authentication token expired
  • Incorrect repository URL

Solutions:

  1. Ensure your GitHub account has the correct permissions to access the repository.
  2. Confirm that you have granted the necessary Auth permissions to StationOps.
  3. Reauthenticate and generate a new personal access token if needed.
  4. Verify that the repository URL is correct and accessible.

# Environment Configuration Issues

# Infrastructure Deployment Fails

Possible Causes:

  • Incorrect or missing environment variables
  • Incorrect repository
  • Incorrect Git branch

Solutions:

  1. Review and validate all environment variables to ensure correctness.
  2. Make sure that the right repository is selected for the service being deployed.
  3. Ensure that the branch selected in StationOps corresponds to the correct repository branch in Git

# Configuration Issues

# Unable to Create a Configuration

Possible Causes:

  • Incorrect service selected
  • Conflicts with existing configurations
  • Misconfigured pass to services

Solutions:

  1. Double-check configuration settings and make sure the correct service is selected at the top of the configuration page.
  2. Ensure no conflicting configurations exist in your setup.
  3. Ensure that your services and components are passed to correctly. For example your componants should pass to your api, your api should pass to your app.

# Environment Variables Not Applying

Possible Causes:

  • Variables not properly saved
  • Incorrect variable scope
  • Cloud provider caching old values

Solutions:

  1. Navigate to the Infrastructure Dashboard and manually verify all environment variables.
  2. Ensure variables are assigned to the correct scope (e.g., Dev, Test, Prod).
  3. If using sensitive variables, confirm they are stored securely and correctly referenced.

# Queue Configuration Issues

# Messages Not Processing

Possible Causes:

  • Incorrect visibility timeout settings
  • Misconfigured retention period
  • No consumers available to process messages

Solutions:

  1. Adjust the visibility timeout and retention period settings in the queue configuration.
  2. Ensure at least one active consumer is available to process messages.
  3. Check logs for errors and resolve any identified issues.

# Storage Configuration Issues

# Unable to Access Storage

Possible Causes:

  • Incorrect access permissions
  • Public access settings not enabled
  • Storage bucket name conflicts

Solutions:

  1. Verify the correct access permissions are set for the storage service.
  2. If public access is required, enable it via the Storage Settings page.
  3. Ensure that no other bucket exists in your AWS account using the same name

# Datastore Configuration Issues

# Database Connection Fails

Possible Causes:

  • Incorrect database credentials
  • Missing environment variables
  • Unsupported database version

Solutions:

  1. Verify database credentials and update them if incorrect.
  2. Ensure all required environment variables are properly set.
  3. Check that the selected database version is supported

# Release Issues

# Release Fails to Deploy

Possible Causes:

  • Incomplete release configuration
  • Missing required files
  • CI/CD pipeline failure

Solutions:

  1. Verify that all required fields are filled during release creation.
  2. Ensure all necessary files are included in the package.
  3. Check CI/CD logs for deployment errors and resolve any issues.

# Additional Help

If you are still experiencing issues, reach out to our support team at team@stationops.com or alternatively visit the StationOps Wizard +

© Copyright 2025. All rights reserved.