Troubleshooting

Bot Does Not Respond in Webex

  • Make sure the bot is added to the space: open the space > People > add the bot's @webex.bot email address.

  • Try mentioning it again: @PrivMan Approvals

  • Check logs: docker logs privman-webex-bot

No Approval Cards Appearing

  • Confirm the space is registered by mentioning the bot and checking that it replies.

  • The bot polls every 30 seconds — wait up to a minute after a request is submitted.

  • Verify there are pending requests in Privilege Manager.

Bot Stopped Unexpectedly

Run docker logs privman-webex-bot and look for ERROR lines. Common causes:

  • Webex token expired — Regenerate it at developer.webex.com/my-apps and re-run the container with the updated -e WEBEX_BOT_TOKEN value.

  • Privilege Manager URL or credentials changed — Re-run the container with the corrected -e values.

Authentication Failed in Logs (Privilege Manager)

  • Verify PRIVMAN_USERNAME and PRIVMAN_PASSWORD are correct.

  • Confirm PRIVMAN_BASE_URL ends exactly with /Tms and has no trailing slash.

  • Verify the API client exists in Privilege Manager and has the Privilege Manager Administrators role.

ValueError: PRIVMAN_BASE_URL Is Required

The container cannot find the environment variables. Verify all required -e flags are present in the docker run command.

Container Exits Immediately

Run docker logs privman-webex-bot to see the error. The most likely cause is a missing or incorrect WEBEX_BOT_TOKEN. Regenerate the token in the Webex developer portal and re-run the container with the updated value.

Websocket Disconnects in the Logs

The bot automatically reconnects every 5 seconds. This is normal behaviour and not a problem unless reconnects fail repeatedly.

Quick Reference

Item Value
Docker image delineaxpm/privman-webex:latest
Default poll interval 30 seconds
Auto-approve duration 4 hours
Data volume privman-bot-data (named Docker volume)
Transport Webex device websocket (no public URL required)
Runtime user Non-root