Conversation
…istered On premium, the lifespan hook sets channel.webhook_registered=True before BlueBubblesChannel.start() runs, so the existing 'if self.webhook_registered: return' short-circuit skipped the _check_server_reachable() call entirely. server_reachable stayed False, is_bluebubbles_configured() returned False, and the dashboard Channels page showed BlueBubbles as "Not available" even though webhook delivery and outbound sends were working fine. Reorder start(): run the reachability check first (it's orthogonal to who registered the webhook), then short-circuit on webhook_registered before tunnel discovery. The tunnel-discovery skip is preserved. Regression test verifies that with webhook_registered=True and a reachable server, start() still sets server_reachable=True while skipping tunnel discovery and webhook registration. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Deployed clawbolt-premium on Railway; the dashboard Channels page showed BlueBubbles as "Not available" (grayed out), but inbound webhooks and outbound sends worked fine.
Root cause: `BlueBubblesChannel.start()` had `if self.webhook_registered: return` before `_check_server_reachable()`. On premium, the lifespan hook in `clawbolt_premium/app.py` sets `channel.webhook_registered = True` during PaaS webhook registration, so the OSS `start()` short-circuits and never runs the reachability probe. `server_reachable` stays `False`, `is_bluebubbles_configured()` returns `False`, dashboard paints it unavailable.
Fix
Reorder `start()`: run the reachability check first (it's orthogonal to who registered the webhook), then keep the `webhook_registered` short-circuit to skip tunnel discovery + OSS webhook registration.
Type
Tests
Checklist
AI Usage
🤖 Generated with Claude Code