Troubleshooting
Common issues and solutions when using SIGILAR.
Login and authentication
401 Unauthorized after OAuth callback
Symptom: Error during or right after Discord login.
Possible causes:
- OAuth callback is trying to fetch CSRF token before cookies are set
- Session or cookie configuration issue
Solution: Ensure the OAuth callback uses skipCSRF: true for the callback request. If the issue persists, clear cookies and try again.
Redirect loop on subscription-required
Symptom: You have an active subscription but are stuck on /subscription-required.
Possible causes:
- Subscription state not refreshed after activation
- Cache or stale state
Solution: Log out and log back in. If you just activated, wait a few seconds and refresh. Ensure the subscription store has fetched the latest status.
Access Rules
Role is not assignable
Symptom: Console shows the bot cannot assign a chosen role.
Causes:
- Above bot position — the role is higher than the bot’s highest role in Discord’s role hierarchy
- Managed role — Discord restricts bot management of this role
- Role not found — role was deleted or changed
Solutions:
- Move the bot’s role higher in Server Settings → Roles
- Choose a different role that the bot can manage
- Re-invite the bot with correct permissions if needed
Role not updating for a member
Symptom: Member should have a role but it is not assigned.
Possible causes:
- Member has not linked their wallet on the Community Portal
- Verification sweep has not run yet (e.g. hourly)
- Wallet does not satisfy the rule (wrong collection, insufficient balance)
Solution: Ask the member to link their wallet, wait for the next sweep, and verify the rule criteria match their holdings.
Wallets (Community Portal)
Wallet connection fails
Symptom: Error when linking a wallet.
Possible causes:
- Wallet extension not installed or locked
- User rejected the signature request
- Network or provider issue
Solution: Ensure the wallet extension is installed and unlocked. Try again and complete the signature when prompted.
"Already linked" but I don't see it
Symptom: Message says wallet is already linked but it does not appear.
Solution: Refresh the wallet list. The wallet may be linked to your account from a previous session.
API and network
CORS errors
Symptom: Browser shows CORS errors when calling the API.
Possible causes:
- Frontend origin not in API CORS whitelist
- Incorrect API base URL
Solution: Ensure CORS_ALLOWED_ORIGINS (or equivalent) includes your frontend URL (e.g. https://sigilar.io, https://console.sigilar.io). Check environment configuration.
429 Too Many Requests
Symptom: API returns 429.
Cause: Rate limit exceeded (e.g. Discord API limits).
Solution: Wait and retry. SIGILAR implements rate-aware dispatch; avoid triggering many requests in a short time.