-
Notifications
You must be signed in to change notification settings - Fork 0
HTTPS and Reverse Proxy
Public BlokeBot dashboards need a trusted HTTPS origin so Twitch can return users safely after authorization.
Run BlokeBot on a private listener such as 127.0.0.1:8080, then publish it through Caddy, nginx, or another HTTPS reverse proxy. Keep the private listener out of the public firewall.
The proxy must preserve the public host and forward the original HTTPS scheme. BlokeBot uses that public origin when building dashboard and channel callback URLs.
Register both callbacks on the same Twitch Website Integration application:
https://bot.example.com/auth/twitch/callback
https://bot.example.com/oauth/callback
Replace the example origin with the real public dashboard origin. Do not register the proxy's private HTTP address. Twitch compares callback URLs exactly, so the scheme, host, port, path, and any path base must agree with Twitch identity configuration.
BlokeBot.Site is a stateless service and can use its own host or a path below an existing host. When it is published below a path such as /blokebot, set BlokeBotSite:PathBase (or BlokeBotSite__PathBase) to the same value so its routes, assets, and accessibility links remain under that prefix.
The help site does not need access to the bot's application state or Twitch credentials.