#Dash cannot process updates and cannot open the analytics page

1 messages · Page 1 of 1 (latest)

lunar ruin
#

This will upload the following to a public paste service:
• System info (OS, Python version, Hermes version, provider, which API keys
are configured — NOT the actual keys)
• Recent log lines (agent.log, errors.log, gateway.log — may contain
conversation fragments and file paths)
• Full agent.log and gateway.log (up to 512 KB each — likely contains
conversation content, tool outputs, and file paths)

Pastes auto-delete after 6 hours.

Collecting debug report...
Uploading...

Debug report uploaded:
Report https://paste.rs/ozBdT
agent.log https://paste.rs/KhmfF
gateway.log https://paste.rs/YzcMI

⏱ Pastes will auto-delete in 6 hours.
To delete now: hermes debug delete <url>

Share these links with the Hermes team for support.

image.png
#

The image shows a rendering issue on the Analytics page; nothing is displayed.

#

Updating the status page operation in Hermes resulted in an error: Action failed: 405: {"detail":"Method Not Allowed"}

#

QQ Bot WebSocket 4009 Timeout

#

01:44:39 WARNING gateway.platforms.qqbot.adapter: [QQBot:1903868416] WebSocket closed: code=4009 reason=Session timed out

median bronze
#

The dashboard problem and the QQBot line look like separate issues.

For the blank Analytics page and the 405 from the dashboard action, restart the dashboard process itself. Your logs show the dashboard process has been running since Apr 16, while Hermes/gateway was updated and restarted later. Gateway restart does not necessarily restart the dashboard, so the browser/frontend and Python dashboard backend can get out of sync.

Run this from the machine hosting the dashboard:

hermes update
pkill -f "hermes dashboard"
hermes dashboard --no-open --host 127.0.0.1 --port 9119

Then hard-refresh the browser page with Ctrl+F5 or Cmd+Shift+R.

There is also a real config issue in the logs:

FileNotFoundError: /opt/hermes

Hermes is trying to use /opt/hermes as the terminal working directory, but that directory does not exist. Either create that directory if it is intentional, or point Hermes at a real existing directory.

For example:

hermes config set terminal.cwd /root
hermes gateway restart

For the QQBot 4009 line: that means the QQ session timed out. Hermes handles that by clearing the session and reconnecting/re-identifying. The logs show it reconnecting afterward, so that line is probably not the cause of the blank Analytics page. If QQBot is disconnecting every minute continuously after the restart, that should be treated as a separate QQBot connection issue.

After restarting the dashboard and fixing terminal.cwd, try Analytics again. If it is still blank, please paste the output of this from the same machine:

curl -s http://127.0.0.1:9119/api/analytics/usage?days=30

Also send a screenshot of the browser console error from the Analytics page.

lunar ruin
#

Everything works fine after restarting the dashboard. The terminal configuration has been corrected to "." It appears that version 0.10.0 conflicts with Caddy's basic_auth. When entering "auth" for the first time to access the Herme panel, it prompts for "auth" again, causing a loop where I have to keep entering the credentials, and I can't log in.

median bronze
#

hmm. yep, looking into a fix.

median bronze