Hi there, I’ve successfully installed Hermes and have encountered many errors trying to get a Slack up and running. Here’s an article that I used as a starting point. I also relied on Perplexity AI to help walk through the steps. Here’s the text that was generated to report the problem:
Title: Hermes gateway on ZimaOS: Slack setup fails with /opt/data/gateway.lock permission error
Environment:
– ZimaOS (Hermes app from ZimaOS App Store)
– New Slack workspace at pxlla.slack.com
– New Slack app Hermes with chat:write, app_mentions:read, channels:read, channels:history, im:history and Socket Mode enabled
What I did:
-
Created a fresh Slack app (
Hermes) in the new pxlla workspace and obtained bothxoxb-…bot token andxapp-…app-level Socket Mode token. -
Opened the Hermes terminal in ZimaOS and ran
hermes gateway setup, chose Slack, and pasted the tokens when prompted. -
The wizard asked “Restart the gateway to pick up changes? [Y/n]” and I answered
y.
What happened:
– The CLI crashed with:
```text
PermissionError: [Errno 13] Permission denied: ‘/opt/data/gateway.lock’
```
– From the Hermes Web UI (http://<zima-ip>:9119), I clicked “Restart Gateway”.
– In Slack, I can now see and invite the @Hermes app into the #all-pxlla channel (Slackbot says “Hermes was added”).
– However, sending @Hermes say "pong" in #all-pxlla produces no response at all.
What I expected:
– Hermes gateway to restart cleanly and respond to @Hermes mentions in the channel.
Notes:
– This is a clean ZimaOS Hermes install and a brand‑new Slack workspace + app created just for this test.
– It looks like the Hermes container user does not have write permission to /opt/data/gateway.lock, so the gateway cannot manage its runtime lock and never fully starts.