-
-
Notifications
You must be signed in to change notification settings - Fork 0
troubleshooting
github-actions[bot] edited this page Jan 4, 2026
·
2 revisions
Common issues and solutions for Eclosion deployments.
# Check logs for errors
docker compose logs eclosion
# Common issues:
# - Port already in use: Change the port mapping
# - Permission denied: Check volume permissions
# - Out of memory: Increase container memory limit# Verify container is running
docker compose ps
# Check if port is listening
netstat -tlnp | grep 5001
# Test from inside container
docker compose exec eclosion python3 -c "import urllib.request; print(urllib.request.urlopen('http://localhost:5001/health').read().decode())"
# Check firewall
sudo ufw status# Verify volume is mounted
docker compose exec eclosion ls -la /app/state
# Check volume exists
docker volume ls | grep eclosion
# Inspect volume
docker volume inspect eclosion_data# Check credentials are stored
docker compose exec eclosion ls -la /app/state/credentials.json.enc
# View application logs for API errors
docker compose logs eclosion | grep -i "monarch\|api\|error"# Stop and remove container
docker compose down
# Remove data (DESTRUCTIVE - will delete all settings and credentials)
docker volume rm eclosion_data
# Start fresh
docker compose up -d- GitHub Issues: Report bugs
- Security Issues: See Security for responsible disclosure
Documentation | Try Demo | Report Issue | Discussions
Eclosion is not affiliated with, endorsed by, or sponsored by Monarch Money.