The most common thing is that the service is completely hung up, but the URL is missing /v1, Hermes' 8642 is not up, or the host is written as localhost in Docker. The official Open WebUI documentation lists these three points directly into the troubleshooting area, so let's check the fastest from here.
Minimum Troubleshooting Sequence
- Check whether the Open WebUI connection address is
http://host.docker.internal:8642/v1, not just a:8642. - Execute the
curl http://localhost:8642/healthnatively to confirm that the Hermes API Server is up. - After
curl http://localhost:8642/v1/models, you should be able to see thehermes-agentor profile name normally. - If Open WebUI runs in Docker, don't write the Hermes address as a
localhostin the container, but use ahost.docker.internal,--network=host, or bridge IP.
Why easy to get stuck here
Because Open WebUI's connection test can pass, it does not mean that the model list will be pulled. Connection tests are more like "does this address look like an API", and the model dropdown also relies on /v1/models to return the correct content.
In a word: the model drop-down box is empty, so don't reinstall the Open WebUI first. Prioritize checking whether the /v1, Hermes 8642 is listening, and how the container accesses the host's address.
Official open source address: https://github.com/NousResearch/hermes-agent; Official document entry: https://hermes-agent.nousresearch.com/.