Protect Your Proxy Credentials

Do not

  • Post full proxy strings in public chats or ticket screenshots.
  • Hard-code API URLs, usernames, and passwords in public repos.
  • Share one credential set across many people for a long time.
  • Paste real passwords into third-party pages while debugging.

Do

  • Load credentials from environment variables in local scripts.
  • Use a secret manager or CI/CD secrets for team projects.
  • Split configs per project so you can revoke and debug cleanly.
  • Reset credentials after a project ends, contractor handoff, or team change.

Example

MASKPROXY_HOST=gw.maskproxy.io
MASKPROXY_PORT=1288
MASKPROXY_USER=username
MASKPROXY_PASS=password

Before opening a ticket, redact username, password, API URL, full proxy string, and account balance.

Related: Manage credentials · Reset credentials · Proxy accounts and credentials.

Powered by MaskProxy