Access troubleshooting
Work Through a Rajabets Access Problem
When access fails, preserve the exact message and check one layer at a time: hostname, browser state, recovery delivery, OTP, device session and account status. This page has no login form or destination.
Follow the tree without sharing credentials
Complete each step before moving to the next. A password field is deliberately absent from this page.
Trusted address
Start only from a hostname you already verified independently. Do not use a link sent in an unsolicited message.
Browser state
Check browser updates, automatic date and time, blocked cookies and site-specific stored data.
Password reset
Use a recovery control reached through the trusted interface; do not follow a separate reset link from an unknown sender.
OTP delivery
Check the expected channel and device time. Never reveal the code to a person or enter it into a second page.
Device and session
Close old sessions on shared devices and avoid saving credentials in a public browser.
Account restriction
Read the exact notice and preserve its date and wording. Repeated attempts can make the timeline harder to explain.
Verified support route
Use a route already shown in a trusted in-account interface and send only a redacted issue summary.
Browser problems that resemble account problems
A stale session, blocked site data, incorrect device clock or extension can interrupt access before account credentials are even evaluated.
- Open one fresh private tab to rule out a stale session.
- Confirm the hostname before entering anything.
- Update the browser and enable automatic date and time.
- Clear only the affected site data before removing all browsing data.
- Test another normal page on the same network.
- Record the exact error instead of guessing that the account is blocked.
Recovery and OTP boundaries
A genuine recovery flow should not require an existing password, a UPI PIN, remote-device access or payment to unlock an account.
Do not forward an OTP or recovery code to anyone who claims to complete the process on your behalf. If the recovery channel is no longer controlled by you, preserve the notice and use a verified account-support route. Avoid submitting the same request repeatedly while the first one remains open.
Prepare a clear access record
Write the trusted hostname, browser, device, approximate time, exact error and the last step that completed. Remove names, phone numbers and account identifiers before copying the summary.
The App and Mobile Access Guide covers device-specific troubleshooting. Use Account Safety to examine address structure and the Support Guide to assemble a redacted timeline. For concise answers, open the FAQ library.
Login-help questions
Can I log in on this website?
Should I share an OTP with support?
What should I record after an access error?
Read an error as evidence, not as a diagnosis
“Incorrect details”, “expired session”, “too many attempts” and “service unavailable” describe different stages. Copy the exact text before trying another step.
An incorrect-details notice can involve the entered identifier, the password or an account state. An expired-session notice often belongs to browser state. A rate-limit message means waiting may be more appropriate than repeating the action. A generic service error can be device-, network- or server-related. Replacing all of them with “login failed” removes the detail that a verified support route would need.
Record whether the message appeared before or after an OTP step. If the page changed hostname or opened a new tab, note that as a separate safety concern. Do not paste the entire browser address if it contains a session token; retain the hostname and a redacted path.