GitHub user dosubot[bot] added a comment to the discussion: Superset Dashboard
& Chart Screenshot Not Found
<!-- Answer -->
Since you have confirmed that geckodriver and Firefox are installed and
working, the ongoing "Not Found" error and screenshot/report failures are
likely due to Superset configuration issues rather than missing binaries.
Here’s what you should check and update in your superset_config.py:
1. Make sure these feature flags are enabled:
```python
FEATURE_FLAGS = {
"THUMBNAILS": True,
"ENABLE_DASHBOARD_SCREENSHOT_ENDPOINTS": True,
}
```
By default, these are set to False, which disables screenshot and thumbnail
generation. Both must be True for screenshots and reports to work.
[Reference](https://github.com/apache/superset/blob/c09f8f6f7665e503a376926700fa815add6892ca/superset/config.py)
2. Ensure your webdriver settings are correct:
```python
WEBDRIVER_TYPE = "firefox"
WEBDRIVER_OPTION_ARGS = ["--headless"]
```
If you use Chrome instead, adjust accordingly.
3. Configure a real cache backend for thumbnails. By default, Superset uses
NullCache, which means screenshots are never actually cached or retrievable:
```python
THUMBNAIL_CACHE_CONFIG = {
"CACHE_TYPE": "RedisCache",
"CACHE_DEFAULT_TIMEOUT": 60 * 60 * 24 * 7, # 1 week
"CACHE_KEY_PREFIX": "superset_thumbnail_",
"CACHE_REDIS_URL": "redis://localhost:6379/1",
}
```
Replace with your Redis/Memcached connection details.
[Reference](https://github.com/apache/superset/blob/c09f8f6f7665e503a376926700fa815add6892ca/superset/config.py)
4. Restart all Superset services and Celery workers after making these changes.
If you still see errors, check your Celery worker logs for any exceptions
related to screenshot generation. Common issues include timeouts (which you can
adjust with SCREENSHOT_LOCATE_WAIT and SCREENSHOT_LOAD_WAIT), permission
problems, or missing dependencies.
See [this discussion](https://github.com/apache/superset/discussions/31432) for
troubleshooting steps and recommended timeout values.
If you follow these steps and screenshots/reports still fail, please share any
error logs from your Celery worker for further diagnosis.
<!-- Dosu Comment Footer -->
*To reply, just mention my name [@dosu](https://go.dosu.dev/dosubot).*
---
<sup>How did I do?
[Good](https://app.dosu.dev/response-feedback/902b58e2-a3e5-4061-8f6b-7432d70618f4?feedback_type=great_response)
|
[Irrelevant](https://app.dosu.dev/response-feedback/902b58e2-a3e5-4061-8f6b-7432d70618f4?feedback_type=irrelevant_answer)
|
[Incorrect](https://app.dosu.dev/response-feedback/902b58e2-a3e5-4061-8f6b-7432d70618f4?feedback_type=incorrect_sources)
|
[Verbose](https://app.dosu.dev/response-feedback/902b58e2-a3e5-4061-8f6b-7432d70618f4?feedback_type=too_verbose)
|
[Hallucination](https://app.dosu.dev/response-feedback/902b58e2-a3e5-4061-8f6b-7432d70618f4?feedback_type=hallucination)
| [Report
🐛](https://app.dosu.dev/response-feedback/902b58e2-a3e5-4061-8f6b-7432d70618f4?feedback_type=bug_report)
|
[Other](https://app.dosu.dev/response-feedback/902b58e2-a3e5-4061-8f6b-7432d70618f4?feedback_type=other)</sup> [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/33660)
GitHub link:
https://github.com/apache/superset/discussions/33660#discussioncomment-13339917
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
