c2e7465645
- Document the solution for Docker environment variable truncation issue - Add verification script to test the fix - Include proper .env configuration with quoted values - Add Docker network (172.20.0.0/16) to allowed IPs The fix ensures bcrypt hashes and other values with special characters are properly passed to Docker containers without truncation. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
1.4 KiB
1.4 KiB
Environment Variable Truncation Fix
Issue
Environment variables with special characters (like $ in bcrypt hashes) were being truncated when passed to Docker containers, causing authentication failures.
Solution
-
Created proper .env file with quoted values:
ADMIN_PASSWORD_HASH='$2b$12$LQv7c3SijBJLhSHPDOLkDe7YfPzFaXhJNXLKqFsFC37GA9xc1wSNi' JWT_SECRET='your-very-long-secret-key-that-should-be-at-least-32-characters-long' -
Added Docker network to ALLOWED_IPS:
- Added
172.20.0.0/16to support Docker's default bridge network - This allows testing from the Docker host
- Added
-
Default credentials:
- Password:
admin123 - The hash in .env corresponds to this password
- Password:
Verification
Run the verification script:
./scripts/verify-env-fix.sh
This script will:
- Rebuild containers
- Check environment variables are properly loaded
- Test authentication API
- Show if login is working
Testing Login
- Access the WebUI at http://localhost:7511
- Use password:
admin123 - You should be able to log in successfully
Troubleshooting
If issues persist:
- Check that .env file exists and has proper quotes around values with special characters
- Ensure Docker containers were rebuilt:
docker compose -f docker-compose.dev.yml up -d --build - Check logs:
docker logs minio-webui-backend-dev - Run debug script:
./scripts/debug-auth.sh