[D] Self-hosting Superset leads to `ERR_EMPTY_RESPONSE` [superset]

["brunolnetto (via GitHub)" <gi...@apache.org>]

GitHub user brunolnetto created a discussion: Self-hosting Superset leads to `ERR_EMPTY_RESPONSE`

I hosted Superset with below configuration and compose file. When I tried to access any route I could imagine, like route `/`, got `ERR_EMPTY_RESPONSE`. 

```
# superset_config.py

# Example configuration for Superset
SQLALCHEMY_DATABASE_URI = 'postgresql://superset:superset@superset-db:5432/superset'
SECRET_KEY = 'your_secret_key'
SUPERSET_WEBSERVER_PORT = 8088
```

```
services:
  # PostgreSQL for Superset metadata storage
  superset-db:
    image: postgres:15
    container_name: superset-db
    restart: always
    environment:
      POSTGRES_USER: superset
      POSTGRES_PASSWORD: superset
      POSTGRES_DB: superset
    volumes:
      - superset-db-data:/var/lib/postgresql/data
    networks:
      - superset-network

  # Redis for caching
  superset-redis:
    image: redis:latest
    container_name: superset-redis
    restart: always
    networks:
      - superset-network

  # Apache Superset
  superset:
    image: apache/superset:latest
    container_name: superset
    restart: always
    ports:
      - "8088:8088"  # Superset web UI
    environment:
      SUPERSET_CONFIG_PATH: /etc/superset/superset_config.py
      DATABASE_URL: postgresql://superset:superset@superset-db:5432/superset
      REDIS_URL: redis://superset-redis:6379/0
    volumes:
      - ./superset_config.py:/etc/superset/superset_config.py
    depends_on:
      - superset-db
      - superset-redis
    networks:
      - superset-network
    command: >
        /bin/bash -c "pip install psycopg2-binary && superset db upgrade && superset init && superset run -p 8088 --with-threads --reload --debugger"

volumes:
  superset-db-data:
  superset-config:

networks:
  superset-network:
    driver: bridge
 
```

GitHub link: https://github.com/apache/superset/discussions/32805

----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org

Re: [D] Self-hosting Superset leads to `ERR_EMPTY_RESPONSE` [superset]

["dosubot[bot] (via GitHub)" <gi...@apache.org>]

GitHub user dosubot[bot] added a comment to the discussion: Self-hosting Superset leads to `ERR_EMPTY_RESPONSE`

<!-- Answer -->
I couldn't find a specific solution to the `ERR_EMPTY_RESPONSE` error within the repository, but here are some general recommendations that might help resolve connectivity issues when hosting Superset with Docker:

1. **Network Configuration**: Ensure that all services are correctly configured to communicate within the same Docker network. You are using `superset-network`, which is good. Double-check that all services are indeed connected to this network.

2. **Service URLs**: Verify that the service URLs are correctly set. For internal communication between Docker services, use the service names as hostnames (e.g., `superset-db` for PostgreSQL and `superset-redis` for Redis).

3. **Port Binding**: Ensure that the port binding is correctly set up. You have `8088:8088` for Superset, which should be correct. Make sure no other service is using this port on your host machine.

4. **Environment Variables**: Double-check the environment variables in your `docker-compose.yml` file. Ensure that `SUPERSET_CONFIG_PATH`, `DATABASE_URL`, and `REDIS_URL` are correctly pointing to the respective services.

5. **Command Execution**: The command you are using to start Superset seems comprehensive. However, consider simplifying it to isolate the issue. Start with just `superset run -p 8088` and see if the error persists.

6. **Logs and Debugging**: Check the logs of the Superset container for any errors or warnings that might indicate the cause of the issue. You can do this by running `docker logs superset`.

7. **Docker Image Version**: Ensure you are using a stable version of the Superset Docker image. Sometimes, the latest image might have unresolved issues. Consider using a specific version tag instead of `latest`.

If these steps do not resolve the issue, you might want to explore similar threads or discussions for additional insights. For example, there is an open discussion about connecting to a Postgres DB running in a container, which might provide some relevant context <sup>[[1]](https://github.com/apache/superset/discussions/30880)</sup>.


<!-- Dosu Comment Footer -->
*To continue talking to [Dosu](https://dosu.dev), mention @dosu.*

---
<sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/4d92d23b-e38d-4ca5-a641-586db397746e?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/4d92d23b-e38d-4ca5-a641-586db397746e?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/4d92d23b-e38d-4ca5-a641-586db397746e?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/4d92d23b-e38d-4ca5-a641-586db397746e?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/4d92d23b-e38d-4ca5-a641-586db397746e?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/4d92d23b-e38d-4ca5-a641-586db397746e?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/4d92d23b-e38d-4ca5-a641-586db397746e?feedback_type=other)</sup>


GitHub link: https://github.com/apache/superset/discussions/32805#discussioncomment-12588741

----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org