Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Gmail Pub/Sub push reaches topic, but openclaw webhooks gmail endpoint does not process real pushes in Docker + Tailscale Funnel setup [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#77093•Fetched 2026-05-05 05:52:20
View on GitHub
Comments
2
Participants
2
Timeline
6
Reactions
2
Author
gigimanlangit73gigimanlangit73
Participants
clawsweeper[bot]clawsweeper[bot]gigimanlangit73gigimanlangit73
Timeline (top)
commented ×2labeled ×2mentioned ×1subscribed ×1

openclaw webhooks gmail does not process real Gmail Pub/Sub push deliveries in a Docker + Tailscale Funnel setup, even though Gmail history advances, Pub/Sub messages are published, and Pub/Sub push delivery works to another HTTPS endpoint.

Error Message

Real Gmail-triggered Pub/Sub events reach the Pub/Sub topic and can be consumed by a pull subscription, but the OpenClaw Gmail webhook path does not show successful processing. A tokenized simulated Pub/Sub-shaped POST to the local watcher endpoint returns 500 Internal Server Error, while direct POSTs to the internal OpenClaw /hooks/gmail endpoint return 200 OK.

Root Cause

openclaw webhooks gmail does not process real Gmail Pub/Sub push deliveries in a Docker + Tailscale Funnel setup, even though Gmail history advances, Pub/Sub messages are published, and Pub/Sub push delivery works to another HTTPS endpoint.

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

openclaw webhooks gmail does not process real Gmail Pub/Sub push deliveries in a Docker + Tailscale Funnel setup, even though Gmail history advances, Pub/Sub messages are published, and Pub/Sub push delivery works to another HTTPS endpoint.

Steps to reproduce

  1. Run OpenClaw 2026.4.15 in Docker with ports 18789:18789 and 8788:8788, and expose /home/gigi/.openclaw to /home/node/.openclaw.
  2. Build a Gmail Pub/Sub setup with:

openclaw webhooks gmail setup
--account [email protected]
--project plexiform-being-494004-a6
--tailscale off
--bind 0.0.0.0
--port 8788
--push-endpoint "https://gigi.tail1f5295.ts.net/gmail-pubsub?token=<pushToken>"

  1. Confirm the watcher process is running: ps aux | grep '[g]og gmail watch serve'

  2. Send a new email to the watched Gmail account.

  3. Observe: • Gmail history advances • Pub/Sub pull subscription receives the event • docker logs -f openclaw shows no successful Gmail hook processing

Expected behavior

A real Gmail-triggered Pub/Sub push should be accepted by the openclaw webhooks gmail endpoint and processed into the OpenClaw Gmail hook path, producing observable successful handling.

Actual behavior

Real Gmail-triggered Pub/Sub events reach the Pub/Sub topic and can be consumed by a pull subscription, but the OpenClaw Gmail webhook path does not show successful processing. A tokenized simulated Pub/Sub-shaped POST to the local watcher endpoint returns 500 Internal Server Error, while direct POSTs to the internal OpenClaw /hooks/gmail endpoint return 200 OK.

OpenClaw version

2026.4.15

Operating system

Host: Ubuntu Linux Container base image: ghcr.io/openclaw/openclaw:2026.4.15

Install method

Docker

Model

openai-codex/gpt-5.4

Provider / routing chain

OpenClaw embedded agent routing to openai-codex/gpt-5.4

Additional provider/model setup details

This issue was reproduced in an OpenClaw Docker deployment whose default model route is openclaw -> cloudflare-ai-gateway -> minimax. The Gmail Pub/Sub failure described here was observed in the webhook/watcher path and was also reproducible through direct local HTTP tests against the watcher and internal hook endpoints.

<img width="621" height="441" alt="Image" src="https://github.com/user-attachments/assets/35ae8a41-f2b1-4424-8b5d-09b50137df67" /> <img width="620" height="361" alt="Image" src="https://github.com/user-attachments/assets/01c61fc5-fb9d-4677-8391-15b0fbf8321f" /> <img width="622" height="1204" alt="Image" src="https://github.com/user-attachments/assets/29bbc0a7-9045-4b6d-94e5-80ce8fc6fbe4" /> <img width="622" height="1174" alt="Image" src="https://github.com/user-attachments/assets/a069cb46-6b89-47bf-912f-6e3402751b90" />

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The OpenClaw webhook endpoint may not be correctly configured to handle Gmail Pub/Sub push deliveries in a Docker + Tailscale Funnel setup, resulting in failed processing of real Gmail-triggered Pub/Sub events.

Guidance

  • Verify that the openclaw webhooks gmail setup command is correctly configuring the webhook endpoint to receive push deliveries from Gmail Pub/Sub.
  • Check the Docker container logs for any errors or warnings related to the webhook endpoint or Pub/Sub push delivery.
  • Test the webhook endpoint directly using a tool like curl to send a simulated Pub/Sub push delivery and verify that it is processed correctly.
  • Review the OpenClaw documentation to ensure that the webhook endpoint is correctly configured to work with Tailscale Funnel.

Example

No code snippet is provided as the issue is related to configuration and setup.

Notes

The issue may be related to the specific configuration of the OpenClaw webhook endpoint or the Tailscale Funnel setup. Further investigation and debugging may be required to determine the root cause of the issue.

Recommendation

Apply workaround: Verify the webhook endpoint configuration and test it directly to ensure it is working correctly. If the issue persists, consider seeking additional support from the OpenClaw community or documentation.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

A real Gmail-triggered Pub/Sub push should be accepted by the openclaw webhooks gmail endpoint and processed into the OpenClaw Gmail hook path, producing observable successful handling.

#configuration error#environment variable#network issue#logging issue#authentication issue

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Gmail Pub/Sub push reaches topic, but openclaw webhooks gmail endpoint does not process real pushes in Docker + Tailscale Funnel setup [2 comments, 2 participants]