Banglarbhumi login not working — what to try

First: yes, you do need the account

Worth settling before you troubleshoot anything, because plenty of advice online says the opposite: a banglarbhumi.gov.in account is required to get a record out of the portal. Fixing your sign-in is not a detour around your real task — it *is* the task.

The confusion is understandable, because the portal does not stop you at the door. Signed out, the menus still open, and the District, Block and Mouza dropdowns still populate one after another exactly as they should. The cascade genuinely works. Only when you ask for the record itself does the portal hand back its login page in place of a result — no error message, no explanation. People read the working dropdowns as proof they are far enough in, and then walk straight into the wall.

So if a search sent you to a sign-in screen, nothing went wrong with the search. You reached the point the portal was always going to stop you. What breaks at that point is almost always one of four things:

• The OTP never arrives — usually the registered mobile number rather than your handset
• Password reset does nothing — a stale registered contact, or a newer request superseding the code you are holding
• “Invalid credentials” with a password you know is right — auto-capitalisation, or a CAPTCHA failure reported as a login failure
• The page errors before the form even loads — portal availability, which is not an account problem at all

What signing in actually opens up

Signing in does two separate things, and keeping them apart makes the rest of the portal easier to read.

First, it makes record lookups return something rather than redirecting you. Second, it wakes up the transactional menus under Citizen Services, which stay inert — showing “Please Login and then click Citizen Services” — until you are in.

Those transactional menus are:

• Online Application — Mutation, Conversion, Warish, Land Revenue (Khajna), and Mobile Number update Against Khatian
• Service Delivery — ROR Request, Plot Info. Request, Plot Map Request, Mouza Map Request, Signed ROR/PI/PLM Copy(s), No Due Certificate
• Online Service Status — Mutation Status, Conversion Status, Warish Status, Payment Status of Land Revenue (Khajna)
• eChallan Application — eChallan Generation. Note that GRN Search, Mouza Map Availability Details, RS-LR Information, Land Classification and the Online Fees Calculator sit directly under Citizen Services rather than inside this submenu

The OTP never arrives

This is the most reported failure, and it usually isn't your phone. OTPs are delivered by SMS, and delivery delays are among the most commonly reported problems with the portal. Users frequently report longer waits during busy periods.

Work through these in order, giving each a genuine chance before moving on:

• Wait several minutes before requesting a second OTP. On many portals a fresh request invalidates the previous code, so repeated tapping can leave you with nothing usable — request once and give it time.
• Check that your number is registered against the right record. If your phone number changed since registration, no OTP will reach you — the portal has a Mobile Number update Against Khatian service for this, though it sits behind login — updating the registered number covers both routes.
• Turn off any SMS-filtering or spam-blocking app, and check the spam or blocked folder. Automated service messages are commonly filtered.
• If the portal is visibly slow, try again at a quieter time — delivery problems and general portal load often coincide.
• Confirm your inbox isn't full — some Android handsets silently drop incoming SMS when storage is exhausted.

Password reset does nothing

The reset flow sends a link or OTP to the registered email or mobile. It fails silently in two situations, neither of which the portal explains clearly.

The first is that the registered contact is stale, which produces the same dead end as above. The second is that several resets were requested in a row. Where a newer request supersedes an older one, only the most recent link or code will work — so use the latest message you received, not the first.

“Invalid credentials” when you know the password is right

Two portal quirks account for most of these.

Check for an unintended capital letter. Mobile keyboards auto-capitalise the first character of an empty field, and if the stored username is lower-case that alone will cause a rejection. Type it manually and try again.

Separately, if the CAPTCHA is wrong, some portal screens report the failure as an invalid login rather than a failed CAPTCHA. If the message appears instantly rather than after a pause, suspect the CAPTCHA rather than the password.

When the problem isn't login at all

If pages hang, time out, or return a server error before you even reach the login form, the issue is portal availability rather than your account — a separate problem with separate fixes.