gog OAuth setup on DigitalOcean - GOG_KEYRING_PASSWORD not working
What I'm trying to do:
Set up gog (Google Calendar CLI) for my clawdbot on DigitalOcean so the bot can access my Google Calendar. I've completed OAuth authorization successfully multiple times, but the clawdbot systemd service can't access the encrypted token file.
What's happening instead:
Getting error: "no TTY available for keyring file backend password prompt; set GOG_KEYRING_PASSWORD"
What I've done:
- Created OAuth 2.0 credentials in Google Cloud Console
- Installed credentials.json to ~/.config/gogcli/credentials.json
- Successfully completed OAuth flow (authorized with cbryce@dotfusion.com)
- Added GOG_KEYRING_PASSWORD=<password> to /opt/clawdbot.env
- Added export GOG_KEYRING_PASSWORD=<password> to /home/clawdbot/.bashrc
- Restarted clawdbot service multiple times
Environment:
- Platform: DigitalOcean Ubuntu droplet
- Bot: Clawdbot 2026.1.24-1
- Tool: gog v0.7.0
- Service: systemd service running as clawdbot user
- Token file exists: ~/.config/gogcli/keyring/token:default:cbryce@dotfusion.com.json
The problem:
The GOG_KEYRING_PASSWORD environment variable doesn't seem to be recognized by the clawdbot service, even though it's set in /opt/clawdbot.env. The OAuth tokens are encrypted and gog can't decrypt them without the password.
Has anyone successfully set up gog on a headless server with a systemd service? Is there a way to configure gog to use unencrypted tokens or a different keyring backend for server deployments?
Set up gog (Google Calendar CLI) for my clawdbot on DigitalOcean so the bot can access my Google Calendar. I've completed OAuth authorization successfully multiple times, but the clawdbot systemd service can't access the encrypted token file.
What's happening instead:
Getting error: "no TTY available for keyring file backend password prompt; set GOG_KEYRING_PASSWORD"
What I've done:
- Created OAuth 2.0 credentials in Google Cloud Console
- Installed credentials.json to ~/.config/gogcli/credentials.json
- Successfully completed OAuth flow (authorized with cbryce@dotfusion.com)
- Added GOG_KEYRING_PASSWORD=<password> to /opt/clawdbot.env
- Added export GOG_KEYRING_PASSWORD=<password> to /home/clawdbot/.bashrc
- Restarted clawdbot service multiple times
Environment:
- Platform: DigitalOcean Ubuntu droplet
- Bot: Clawdbot 2026.1.24-1
- Tool: gog v0.7.0
- Service: systemd service running as clawdbot user
- Token file exists: ~/.config/gogcli/keyring/token:default:cbryce@dotfusion.com.json
The problem:
The GOG_KEYRING_PASSWORD environment variable doesn't seem to be recognized by the clawdbot service, even though it's set in /opt/clawdbot.env. The OAuth tokens are encrypted and gog can't decrypt them without the password.
Has anyone successfully set up gog on a headless server with a systemd service? Is there a way to configure gog to use unencrypted tokens or a different keyring backend for server deployments?
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
83,815Members
Resources
Similar Threads
Was this page helpful?
