IMUGA portal help
IMUGA Portal Not Working: Errors and Fixes
A troubleshooting guide for the IMUGA portal: slow pages, validation messages, browser cache problems, expired sessions, stuck submissions and missing emails.
Sooner or later the IMUGA portal does something unhelpful: the page hangs, a field turns red for no visible reason, or the Traveller Declaration refuses to submit at eleven at night with a flight the next morning. Most of these failures are ordinary web problems with ordinary fixes, and knowing which are yours and which belong to Maldives Immigration saves a lot of panic.
Short answer: roughly nine failures out of ten are local — a stale cache, a browser that has not been updated in two years, a session that quietly expired, or a date typed in the wrong format. Clear the cache, open a private window, re-check the flagged field and try again. Only a genuinely unreachable portal is a system problem, and that usually clears within the hour.
The page will not load, or loads at a crawl
First find out whether the problem is the portal or your connection: open any other website you rarely visit. If that also drags, the network is at fault. If other sites are fine but the portal is not:
- Reload once, properly — a hard reload that ignores the cache, not a tap on the address bar.
- Switch network. Hotel Wi-Fi and airport captive portals interfere with secure connections more often than people expect. Mobile data is usually the fastest diagnosis.
- Disable a VPN. Some routes to the Maldives resolve badly through VPN exit nodes, and a few corporate VPNs block government domains outright.
- Try a different device. A five-year-old tablet is a common invisible culprit.
If the portal is genuinely down, waiting is the only option: come back in thirty to sixty minutes rather than hammering refresh.
In short: isolate the variable — network, device, browser, portal — before changing anything.
Validation messages: what they actually mean
A red field is not a system error. It is the form telling you that what you typed does not match the shape it expects. Three families cover almost everything.
Passport format. The portal wants the number exactly as printed on the data page, with no spaces,
dashes or country prefix you added yourself. Confusing 0 with O and 1 with I accounts for a
startling share of rejections. Read it off the passport, not off a booking that may have reformatted
it.
Dates out of range. Either the date genuinely falls outside the permitted window, or you typed it in the wrong order — day/month rather than month/day. The safest habit is to use the date picker instead of typing, every time.
Flight number not recognised. Enter the airline code plus the number with no space, using the code of the carrier that actually operates the leg landing in Malé, not the one that sold you the ticket. Codeshares cause most of these failures. If you connect through Doha, Istanbul or Dubai, the relevant flight is the final one into the Maldives — our page on transit and connecting flights goes into that in detail.
In short: validation errors are almost always transcription errors.
Worth knowing: a rejected field does not mean the whole form is lost. Fix the flagged entry and the rest of your answers normally remain intact — unless the session has expired underneath you.
Error message, likely cause and what to do
| Message or symptom | Likely cause | Fix |
|---|---|---|
| Page blank or endlessly spinning | Cached assets or blocked scripts | Hard reload, then open a private window |
| "Invalid passport number" | Spaces, dashes, or O/0 confusion | Retype from the passport data page, no separators |
| "Date out of range" | Wrong window or day/month reversed | Use the date picker; check the permitted window |
| "Flight not found" | Codeshare or space in the code | Use the operating carrier code, no space |
| Form resets when you press next | Session expired | Start again in a private window and work faster |
| Submit button spins and never finishes | Weak connection or double click | Wait 60 seconds, do not click again, then reload |
| "An error has occurred, try later" | Server-side, generic | Wait 30–60 minutes and retry |
| Fields refuse to accept typing | Browser autofill conflict | Disable autofill or use a private window |
| Confirmation email never arrives | Spam filter or typo in the address | Search the inbox, then check the address you entered |
| Portal unreachable on every device | Genuine outage or network block | Try mobile data; if it persists, wait it out |
In short: match the symptom to the pattern before you start re-entering data.
Browser problems: cache, cookies, private mode
The portal is a modern web application, and modern web applications age badly in old browsers. If you use a device you rarely update, this section is your answer. Work through it in order and stop when it works:
- Hard reload the page.
- Clear the cache and cookies for that site alone, not your whole browsing history.
- Open a private or incognito window — this bypasses cache and extensions in one move, and is the single most effective trick in this article.
- Disable extensions, particularly ad blockers, script blockers and privacy tools that break form submissions silently.
- Update the browser, or switch to a different one. A current Chrome, Safari, Firefox or Edge will behave; a browser two major versions behind may not.
One caveat about private mode: it forgets everything when you close it. Do not use it to keep a half-finished form open overnight.
In short: private window first, extensions second, browser update third.
The session expires halfway through the form
This is the most demoralising failure, because you lose typed work. Sessions time out after a period of inactivity, and reading the health questions carefully counts as inactivity if you are not clicking. Prevention beats recovery:
- Gather everything first. Passport, flight numbers, accommodation name and address, dates. Have them in front of you before you open the form.
- Draft the awkward answers elsewhere. Long accommodation addresses are worth typing into a note and pasting in.
- Do not leave the tab open while you go and find a document. Come back to a fresh form instead.
- Fill it on a laptop if you can. Phone keyboards make everything take three times longer, and time is what kills the session.
If it has already happened, do not fight it. Reload the entry page, start again with everything to hand, and it will take four minutes rather than fourteen.
In short: a timeout is a time problem, not a data problem — prepare, then fill in one pass.
Submission stuck on loading
You press submit and the spinner never stops. The important rule: do not click submit repeatedly. Each click risks creating a duplicate declaration, which is more annoying to unpick than a single failed attempt. Instead:
- Wait a full minute. Slow does not mean broken.
- If nothing changes, note down what you entered, then reload the page.
- Check your email before resubmitting — the declaration may have gone through even though the screen never updated.
- Only if no confirmation exists after ten minutes, submit again.
- If you end up with two identical declarations, it is untidy but not an offence. See changing or cancelling a declaration.
In short: wait, check the inbox, and only then resubmit.
No confirmation email
The QR code arrives by email, so a missing confirmation feels like a failed submission. Usually it is not. In this order:
- Search the inbox for immigration, declaration or the portal name, rather than scrolling.
- Check spam, promotions and any corporate quarantine.
- Verify the address you typed. One wrong character is the most common cause by a wide margin.
- Wait. Delivery is normally quick but relays occasionally queue.
- Only resubmit if none of the above produces anything after a reasonable wait.
The lesson for next time is to use a personal address you can reach from a phone, which we cover in accounts and login on the IMUGA portal.
In short: search before you resubmit; the message is usually in the inbox already.
Worth knowing: work email addresses are the leading cause of missing confirmations. Corporate filters treat unfamiliar government domains with suspicion and quarantine them without telling you.
Peak hours and congestion
The portal is busiest when many travellers open their filing window at once — evenings in European time zones, and the hours before the daily bank of long-haul arrivals into Velana International. Weekend evenings before school holidays are noticeably worse. Two consequences follow:
- Do not leave it to the last hour. Aim to file when your window opens, not when it closes.
- If the portal is sluggish, come back later. An early morning attempt from Europe or a mid-morning one from Latin America usually sails through.
Congestion looks like generic errors, slow page loads and timeouts, all of which are easy to misdiagnose as faults on your side.
In short: file early in your window and avoid the evening rush.
Whose fault is it: yours or the system's?
Distinguishing the two saves time, because the fixes are opposite: your problem is solved by changing something, the system's by waiting. It is on your side when:
- Other websites work normally and only the portal misbehaves on one device.
- The error names a specific field.
- A private window or a different browser fixes it instantly.
- It happens consistently at the same step, every time.
It is on the portal's side when:
- Nothing loads on any device, on any network, for anyone travelling with you.
- The message is generic and mentions trying again later.
- It fails at random points rather than the same one.
- It resolves by itself after half an hour with nothing changed.
Health questions deserve one specific caution: answer them accurately rather than trying to force a value the form dislikes. The health section is short but it is not a formality.
In short: field-specific and reproducible means you; generic and universal means them.
Plan B when nothing works
Rare, but it happens. In order of preference:
- Change device and network at the same time. A phone on mobile data, from scratch, in a private window.
- Ask someone at home to file it for you. They only need your passport details and flight information, and their connection may be perfectly healthy.
- Ask your accommodation. Resorts and Malé hotels handle this constantly and often have a business centre with a working machine.
- Speak to the airline at check-in. Staff deal with declaration problems daily and know the current practice.
- Use a paid assistance service, ours or another. It is optional and the official route has no cost, but on a deadline it is a legitimate shortcut.
Whatever happens, keep any error screenshot with a timestamp. It is useful evidence if you have to explain the situation at the airport.
In short: escalate by changing conditions, not by repeating the same attempt.
Key points
- Nine failures out of ten are local: cache, browser, connection or a typo.
- A private window resolves more portal problems than any other single action.
- Validation messages point at a specific field; read it and retype from the passport itself.
- Never click submit twice — wait, check your email, then decide.
- Peak evening hours cause generic errors that look like your own mistakes.
- File early in your window so a bad night still leaves you time to retry.
FAQ about IMUGA portal errors
The portal will not load at all. Is it down?
Test another website, then another device, then mobile data. If everything else works and the portal does not on any device, it is probably a genuine outage. Wait thirty to sixty minutes.
Why does the portal reject my passport number?
Almost always formatting. Remove spaces and dashes, copy the number from the passport data page
rather than a booking, and check for 0 versus O and 1 versus I.
The flight number is not recognised. What do I enter?
Use the operating carrier's code with no space, for the flight that actually lands in the Maldives. Codeshare numbers printed on your ticket are the usual cause of rejection.
I clicked submit twice and now I think there are two declarations
Check your email for two confirmations. A duplicate is not an offence, and only one QR code will be scanned. If it worries you, contact the portal or ask at check-in.
My session expired and I lost everything. Do I have to start over?
Yes, but with everything prepared it takes a few minutes. Gather passport, flights and accommodation details first, then complete the form in a single pass without pausing.
Does incognito mode really help?
Often, yes. It bypasses cached files and disables most extensions, which are the two most common causes of a form that refuses to behave. Just do not leave work unfinished in it.
No confirmation email arrived. Did the declaration fail?
Not necessarily. Search the inbox thoroughly, check spam and quarantine, and confirm the address you typed. Resubmit only if nothing appears after a reasonable wait.
Can I fill in the form on my phone?
You can, and many travellers do. A laptop is faster and reduces the risk of a timeout, but a phone on a stable connection works fine if you have your details ready before you start.
Is the portal slower at certain times?
Yes. Evenings in European time zones and the run-up to the daily long-haul arrivals are the busiest periods. Filing early in the morning, or as soon as your window opens, avoids most congestion.
What if I cannot file before departure?
Speak to the airline at check-in and to immigration on arrival, and keep evidence of your attempts. Filing in advance is expected, so leave yourself margin rather than relying on goodwill.
Last updated: July 2026. Immigration rules change; always confirm current requirements on the official Maldives Immigration portal before travelling.