Firecrawl web extract keeps failing in Hermes Agent 0.17
Since 0.17, with a Firecrawl setup has been failing every time. and Firecrawl run on the same desktop and the same instance, but they are in separate . After Firecrawl is set as the provider for , requests made from the agent chat always fail.
The same scrape request works when it is run as a from inside the Hermes container through the VS Code terminal. The Hermes service runs with the `gateway run` command, exposes port 8642 for the core API gateway and port 9119 for the web dashboard, and enables settings for the dashboard, trusted proxy, config path, and a longer cron timeout.
Key points
- Firecrawl-based fails every time from chat after version 0.17.
- and Firecrawl run on the same instance but in separate .
- A run inside the Hermes container can scrape successfully.
- The likely area to check is ’s wiring, provider settings, container URL, or version 0.17 behavior.
- A direct inside-container test is a useful first step for narrowing the problem.