docs: add setup guide for zrok proxy service - #29
Merged
Conversation
zlshames
approved these changes
Jan 27, 2026
nicoalba
marked this pull request as ready for review
January 27, 2026 19:31
Contributor
Author
|
@zlshames last changes made, ready to merge. Thank you |
zlshames
approved these changes
Feb 7, 2026
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
2 participants
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.
This PR adds a documentation guide for using zrok as a proxy service.
zrok is already integrated into the BlueBubbles Server settings, but lacked a corresponding guide in the "BYO Proxy" section. This guide helps users who want an open-source, high-bandwidth (5GB/day) alternative to Cloudflare and Ngrok.
Summary of changes:
advanced/byo-proxy-service-guides/zrok-proxy.mdSUMMARY.mdREADME.md, and also alphabetized the options to matchSUMMARY.mdinstallation-guides/manual-setup.md*.share.zrok.iotunnel initializes immediately upon saving the token and confirmed the active frontend mapping via the zrok portal.