Cookies setup

Fix "Sign in to confirm you're not a bot" errors on hosting providers.

On this page

Why do I need this?

If you host Rawon on cloud providers like OVHcloud, AWS, GCP, Azure or other hosting services, you might see:

“Sign in to confirm you’re not a bot”

The platform blocks requests from data center IP addresses. By authenticating with a Google account, Rawon can generate valid cookies to bypass this restriction.

The built-in !login command opens a real browser for Google login via Puppeteer, exports cookies to disk, closes the browser afterwards and persists across restarts.

!login start    - Open a browser and start Google login
!login status   - View current login & cookie status
!login logout   - Clear the current login session (wipes all cookies and profile data)

Quick start

  1. Run !login start in Discord.
  2. The bot sends you a DevTools URL. Open it in your browser.
  3. A Google login page appears in the remote browser.
  4. Log in with a throwaway Google account (not your main account).
  5. Once logged in, the bot saves the cookies and closes the browser.

If bot detection occurs again

Cookies may become stale due to server-side rotation. Run !login logout, then !login start again.

Prerequisites

  • A secondary/throwaway Google account
  • For non-Docker users: Chrome or Chromium installed on the host

Docker users get persistence through the rawon:/app/cache volume, and the image includes Chromium.

Environment variables

Optional, in dev.env:

DEVTOOLS_PORT=""
CHROMIUM_PATH=""

For Docker, make sure the port mapping matches:

ports:
  - "${DEVTOOLS_PORT:-3000}:${DEVTOOLS_PORT:-3000}"

Troubleshooting

  • Still getting the error? Check !login status, then run !login logout and !login start.
  • Browser won’t start? Check !login status for details and make sure Chrome/Chromium is installed (or set CHROMIUM_PATH).
  • Account suspended? Create a new throwaway account, !login logout, then !login start.

Place a Netscape-format cookie file at cache/cookies.txt. The bot uses it if it exists, but the !login method is recommended.

Caution

Use a throwaway Google account. The DevTools URL gives access to the browser session, so don’t share it. Cookie files contain sensitive authentication data.

Type to search the documentation.