Skip to content

Railway Deployment FAQ

Common Issues & Solutions

Database Connection Problems

Error: Connection to database failed on port 5432

Solution: Ensure PostgreSQL service is properly connected to your container in Railway settings.

Steps to fix:
  1. Go to your container service in Railway
  2. Navigate to Settings → Service Connections
  3. Click Connect next to your PostgreSQL service
  4. Wait 2-3 minutes for connection to establish
  5. Check deployment logs for confirmation :::

Configuration Issues

Error: ABS_CONFIG is required but not provided

Solution: Double-check all environment variables are properly set in Railway dashboard.

Steps to fix:
  1. Go to Variables tab in your service
  2. Verify all required variables are present
  3. Check for typos in variable names
  4. Validate JSON syntax in ABS_CONFIG
  5. Redeploy after fixing variables :::

Authentication Problems

Error: 401 Unauthorized - Invalid API key

Solution: Verify your API keys are correct and have proper permissions.

Steps to fix:
  1. Check API keys in respective dashboards
  2. Ensure no extra spaces or characters
  3. Verify key permissions and quotas
  4. Test keys individually if possible
  5. Contact API providers if keys appear valid :::

Normal Startup Behaviors

Log: Pool config not found in DB for 0x..., checking if we can initialize

Status: This is normal for new deployments. The system will auto-discover and initialize pools on first run.

What happens:
  1. System discovers pool configuration from blockchain
  2. Fetches token metadata automatically
  3. Creates database entities
  4. Begins processing blocks
  5. Usually completes within 60 seconds :::

Log: Processing batch with 0 blocks (waiting for sync...)

Status: Normal during initial sync. The processor is waiting for blockchain data to become available.

Expected timeline:
  • Initial sync: 1-5 minutes
  • Regular processing starts automatically
  • First meaningful logs appear after sync

Performance Issues

Symptoms: Container restarting frequently, out of memory errors

Solutions:
  1. Reduce pool count in ABS_CONFIG
  2. Upgrade Railway plan for more memory
  3. Optimize batch processing settings
  4. Contact support for memory optimization tips :::

Error: 429 Too Many Requests

Solutions:
  1. Upgrade CoinGecko plan if using free tier
  2. Check Alchemy usage limits
  3. Implement request delays if needed
  4. Contact Absinthe team about rate limits :::

Getting Help

Before Contacting Support

  1. Check Railway service status
  2. Review deployment logs for errors
  3. Verify all environment variables
  4. Test database connectivity
  5. Confirm API keys are valid

Support Channels

  • Railway Support: Use in-dashboard chat
  • Railway Discord: railway.app/discord
  • Absinthe Team: For adapter-specific issues
  • GitHub Issues: For open-source problems

Information to Include

When reporting issues, provide:

  • Railway deployment logs
  • Environment variable names (not values)
  • Error messages with timestamps
  • Service configuration screenshots
  • Steps to reproduce the issue