Troubleshooting
Most issues below are permission or configuration related, and fixable in a couple of minutes.
Wallet not verifying
- Double-check you're on the chain your community's Access Policy actually requires.
- If connecting a wallet fails, try verifying without connecting instead (or vice versa) - both prove the same thing.
- You can always retry with a different wallet if the first one doesn't qualify.
Warning
Verify is still in active production testing against a few wallets. Some signing issues have been seen with certain wallet apps and WalletConnect specifically - if a wallet fails to connect, verifying without connecting is currently the more reliable path.
Role not assigned
On Discord, this is almost always one of two things:
- OtterFi's bot role needs to sit above the role it's trying to grant, in your server's role list.
- The bot is missing the Manage Roles permission - see Administration.
Bot cannot access a channel
Confirm the bot can actually see the channel (View Channels) and, for Notify, that it can post and embed there (Send Messages, Embed Links, Attach Files). A private channel needs the bot explicitly added to it.
Notifications not arriving
- Check the destination hasn't been paused (
/resumeif it has). - Confirm the notification category is turned on in Settings.
- If the bot is missing Attach Files, message delivery can fail outright rather than just missing an image.
Dashboard not updating
The pinned dashboard refreshes roughly once an hour by design - it's not meant to update on every single event. If the pinned message itself was deleted or unpinned, run /pin again to recreate it.
Permission issues
Most permission problems trace back to the exact list in Administration - worth checking there first before anything else.
Common mistakes
- Expecting Live Membership by default - it's opt-in per community and off until turned on.
- Adding the bot to two channels that both try to run separate setups for the same server - OtterFi will flag this rather than silently pick one.
- Assuming a paused community keeps checking access in the background - it doesn't, until resumed.