Troubleshooting
Logged out after restart
BIM VPN keeps your session in the system keychain and renews it every time the app starts. You should stay signed in across restarts.
Update the app first. Older versions could show the login screen after a restart even though the session was still valid:
- On networks that block
api.bimvpn.xyz, versions before 0.8.7 tried only that one address, gave up, and showed the login screen. Current versions try every BIM address in turn and never sign you out because the network is unreachable. - Some older test builds were not signed consistently, and macOS treated each update as a different app that could not read the saved session.
If you are still signed out on the latest version, the server rejected your session. That happens when:
| Cause | What happened |
|---|---|
| You signed out everywhere | Sign out of all devices in Account ends every session at once |
| The session was used twice | A saved session was reused, for example after restoring the app data onto another computer. As a safety measure every session of the account is signed out. |
| The device identity changed | The session is tied to the device. A reinstalled system or replaced hardware can count as a new device. |
Sign in again. If it keeps happening, contact support with your app version and operating system.
Only offline? You are not signed out
If the app cannot reach any BIM server at launch, it keeps your saved session and retries. Connect to a network and reopen the app.
Activation email not received
Check your spam folder, then use Resend verification email in the app (Account). If nothing arrives within 10 minutes, contact support through t.me/bimvpn.
- Wait a few minutes and check your spam or junk folder.
- Check the address. The email goes to the exact address typed at registration. A typo cannot be fixed by resending.
- The link lasts 24 hours. An expired or already used link shows Link expired or invalid.
- Ask for a new link. In the app, open Account and click Resend verification email. After clicking the new link, click Refresh. If no email arrives, contact support through t.me/bimvpn with your account email. Developers can call
POST /auth/resend-verification.
You can use the app and buy a plan while your email is not yet activated.
Payment pending
The checkout page and the app update by themselves when a payment is matched. If the invoice stays pending, go through this list.
1. Check the amount
The payment must equal the invoice amount exactly, to the last decimal: six decimals for USDT, eight for BTC, up to twelve for XMR. The last digits identify your invoice.
- Paid from an exchange? It may have subtracted its fee or rounded the amount, so the payment does not match.
- Sent in two parts? Each part is checked on its own, so neither matches.
2. Check the network and token
- USDT ERC-20 must go over Ethereum, USDT TRC-20 over Tron. A transfer on another network (for example BNB Chain) is not seen.
- Only official Tether USDT counts. See the contract addresses on Pay with USDT stablecoins.
3. Check that it was actually sent
Look up your transaction in your wallet or a block explorer.
- USDT: it must appear on Etherscan (ERC-20) or Tronscan (TRC-20). BIM relies on those explorers, so a delay on their side delays the match by a few minutes.
- Bitcoin and Monero: payments are detected as soon as they reach the network, before confirmation. A Bitcoin transaction with a very low fee can still take long to be broadcast.
4. Check the time
An invoice is valid for 30 minutes from creation. Switching payment method in checkout cancels the previous invoice. Pay only the invoice currently on screen.
5. Refresh the app
Your plan is credited on the server even if you closed the checkout page. Reopen BIM VPN, or sign out and in again, to see it.
Still pending?
Contact support through t.me/bimvpn with:
- the email or username of your account,
- the coin, the amount sent and the time,
- the transaction hash (for Monero, the transaction id).
Never send your password, your wallet recovery phrase or your private keys. Support never asks for them.
Exit proxy errors
See Error messages.
