Files
proxmox/docs/archive/completion/BLOCKSCOUT_FIXED_SUCCESS.md
defiQUG cb47cce074 Complete markdown files cleanup and organization
- Organized 252 files across project
- Root directory: 187 → 2 files (98.9% reduction)
- Moved configuration guides to docs/04-configuration/
- Moved troubleshooting guides to docs/09-troubleshooting/
- Moved quick start guides to docs/01-getting-started/
- Moved reports to reports/ directory
- Archived temporary files
- Generated comprehensive reports and documentation
- Created maintenance scripts and guides

All files organized according to established standards.
2026-01-06 01:46:25 -08:00

3.3 KiB

Blockscout Fixed Successfully!

Date: December 23, 2025
Status: FIXED AND RUNNING


Problem Solved

The Blockscout container was restarting due to:

  1. Missing command: The image entrypoint was /bin/sh with no default command
  2. DISABLE_WEBAPP=true: Default environment variable was disabling the webapp

Solution Applied

1. Added Explicit Start Command

command: /app/bin/blockscout start

2. Set DISABLE_WEBAPP=false

environment:
  - DISABLE_WEBAPP=false

3. Complete docker-compose.yml Configuration

version: '3.8'

services:
  postgres:
    image: postgres:15-alpine
    container_name: blockscout-postgres
    environment:
      POSTGRES_USER: blockscout
      POSTGRES_PASSWORD: blockscout
      POSTGRES_DB: blockscout
    volumes:
      - postgres-data:/var/lib/postgresql/data
    restart: unless-stopped
    networks:
      - blockscout-network
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U blockscout"]
      interval: 10s
      timeout: 5s
      retries: 5

  blockscout:
    image: blockscout/blockscout:latest
    container_name: blockscout
    command: /app/bin/blockscout start
    depends_on:
      postgres:
        condition: service_healthy
    environment:
      - DISABLE_WEBAPP=false
      - DATABASE_URL=postgresql://blockscout:blockscout@postgres:5432/blockscout
      - ETHEREUM_JSONRPC_HTTP_URL=http://192.168.11.250:8545
      - ETHEREUM_JSONRPC_WS_URL=ws://192.168.11.250:8546
      - ETHEREUM_JSONRPC_TRACE_URL=http://192.168.11.250:8545
      - ETHEREUM_JSONRPC_VARIANT=besu
      - CHAIN_ID=138
      - COIN=ETH
      - BLOCKSCOUT_HOST=192.168.11.140
      - BLOCKSCOUT_PROTOCOL=http
      - SECRET_KEY_BASE=<generated-secret-key>
      - POOL_SIZE=10
      - ECTO_USE_SSL=false
    ports:
      - "4000:4000"
    volumes:
      - blockscout-data:/app/apps/explorer/priv/static
    restart: unless-stopped
    networks:
      - blockscout-network

volumes:
  postgres-data:
  blockscout-data:

networks:
  blockscout-network:
    driver: bridge

Current Status

Container Running: Blockscout container is up and running
Port 4000: Listening on port 4000
PostgreSQL: Connected and healthy
Configuration: All settings correct (Chain ID 138, RPC URLs, etc.)


Access Points


Next Steps

  1. Wait for Initialization: Blockscout may take 1-2 minutes to fully initialize and start indexing
  2. Verify API: Test the health endpoint: curl http://192.168.11.140:4000/api/health
  3. Check Logs: Monitor startup: docker logs -f blockscout
  4. Test Web UI: Open http://192.168.11.140:4000 in browser

Useful Commands

# View logs
docker logs -f blockscout

# Check status
docker ps | grep blockscout

# Restart
cd /opt/blockscout
docker-compose restart blockscout

# Stop
docker-compose down

# Start
docker-compose up -d

Files Modified

  • /opt/blockscout/docker-compose.yml - Updated with command and DISABLE_WEBAPP=false

Blockscout is now running and ready to use!