Skip to content
This repository was archived by the owner on Sep 14, 2025. It is now read-only.

CHECK_BETA_STATUS.md

Latest commit

 

History

History
70 lines (49 loc) · 1.69 KB

CHECK_BETA_STATUS.md

File metadata and controls

70 lines (49 loc) · 1.69 KB

Beta Deployment Status

✅ GitHub Actions: Fixed and Working!

  1. Azure credentials: Updated successfully
  2. Docker build: Completed successfully
  3. Push to Docker Hub: Success
  4. Deploy to VM: Success
  5. Health check: Passed (localhost:3010 responding)

⚠️ Current Issue: 502 Bad Gateway

The deployment succeeded but https://beta.crove.com returns 502.

Possible causes:

  1. Nginx on VM not configured properly
  2. Docker container not exposed on correct port
  3. Firewall blocking port 3010

To diagnose and fix:

# SSH to VM
ssh joy@52.172.194.116

# Check Docker containers
docker ps

# Check if Rails is running
docker logs crove-rails --tail 50

# Test local connection
curl http://localhost:3010

# Check Nginx config
sudo cat /etc/nginx/sites-available/crove

# Check Nginx error log
sudo tail -100 /var/log/nginx/error.log

# Restart Nginx if needed
sudo systemctl restart nginx

Quick fix attempts:

  1. Restart containers on VM:
ssh joy@52.172.194.116 "cd /home/joy/crove && docker-compose -f docker-compose.production.yml restart"

  1. Check if container is named correctly: The health check looks for crove-rails but deployment might create different container name.

  2. Verify port mapping: Make sure docker-compose.production.yml maps port 3010 correctly.

Summary

  • ✅ CI/CD pipeline is now working
  • ✅ Code deploys automatically on push to develop/main
  • ⚠️ Site accessibility needs fixing (502 error)
  • 📝 Need to SSH to VM to diagnose Nginx/Docker issue

Next Steps

  1. SSH to VM and check container status
  2. Fix Nginx reverse proxy configuration
  3. Ensure port 3010 is accessible
  4. Test end-to-end deployment again