My Tax Return Was Ready. The VPN Was the Only Part That Failed.

The Indian income-tax portal loaded just far enough to make the failure feel personal. I entered my PAN, completed the security check and clicked Continue. The page went white, then returned a DNS error. I refreshed it, changed browsers and cleared the cache. The login page reappeared, accepted the same details and failed in the same place. It was 11:18 p.m. in India on July 31, 2026. My return was complete, but I had forty-two minutes to submit it before the filing deadline.

I was in a hotel room in Frankfurt, finishing an Indian return that included rental income from an apartment in Bengaluru.

My accountant had prepared the figures earlier that day. All I needed to do was review the pre-filled information, submit the return and complete verification.

The July 31 deadline had not been extended. Taxpayers who missed it could still file later, but a belated return could involve a fee of up to ₹5,000 and other consequences. (Economictimes)

The arithmetic was finished.

The portal was the only thing standing between me and the acknowledgement receipt.

The page worked until the VPN was on

I first blamed deadline traffic.

Reports of portal glitches had circulated during the final week, and millions of taxpayers were trying to finish at roughly the same time. A slow login seemed believable.

I tried again.

The homepage opened. The help pages opened. The secure login either timed out or produced a DNS failure.

Then I noticed the VPN.

It had connected automatically when my laptop joined the hotel Wi-Fi. I disconnected it and reloaded the portal.

The dashboard appeared.

That identified the problem, but it did not give me a solution. The hotel network was shared by hundreds of rooms, and I was about to open tax records, bank-linked information and an account protected by one-time passwords.

I turned the VPN back on.

The portal stopped working again.

The task had changed. I did not need general advice for a slow government website. I needed a protected connection the tax portal would accept from login through verification.

An Indian server label did not solve it

My established VPN seemed like the obvious place to start.

It had years of public history, polished applications and a large network. I opened its location list and selected India.

The connection formed quickly.

The tax portal did not.

The first attempt failed before the login form appeared. The second reached the form, then froze after I submitted my PAN. A third opened the dashboard but logged me out when I selected the prepared return.

I switched to another Indian location.

The error changed to DNS_PROBE_FINISHED_NXDOMAIN.

That looked like progress only because I had started grading failures.

I tried Singapore, then the United Kingdom, hoping a different route would avoid the problem. Both connections handled video and ordinary browsing without difficulty. Neither completed the tax login.

The provider’s broad network was normally a strength. That night, it gave me more routes to test without showing which one could carry the portal all the way to submission.

With twenty-nine minutes remaining, the location list had become another delay.

The protected route was breaking the tax session

The return itself was not being rejected. The browser was failing earlier, while trying to reach parts of the government portal through the VPN.

A documented issue involving incometax.gov.in showed how this can happen: the site resolved normally outside a protected gateway, while certain secure routes encountered DNSSEC-related failures. The workaround was to bypass the affected domain or use supported Indian routes. (Broadcom)

That matched what I could see on the laptop.

With the VPN off, the portal loaded.

With the VPN on, the rest of the internet worked while the tax portal failed.

The protection layer was not simply making the page slower. It was sending the session through a route the portal could not complete.

Indians living abroad describe the same practical frustration in public discussions: government websites may time out overseas, and using an Indian VPN location does not guarantee that every service will work. (Reddit)

I did not need more forum theories.

I needed a different route before midnight.

Turning off the VPN created a second risk

The fastest workaround was to leave the VPN disabled.

I tried it for a moment.

The portal opened, and I reached the income summary. Then the hotel Wi-Fi weakened. The page stalled while loading my Annual Information Statement and returned me to the dashboard.

I had reached the site, but I could not rely on the connection staying stable through submission and verification.

The official process also does not end when the return is uploaded. The return must be verified; otherwise, it is treated as invalid. (Gov)

I could have submitted first and dealt with verification later. But that would have turned an urgent filing into another unfinished task hanging over the next month.

I wanted the acknowledgement and verification confirmation before closing the laptop.

There were twenty-one minutes left.

I stopped trying to repair the established route.

The smaller app began with what I needed to do

OnlydogVPN was already installed as a travel backup.

It had fewer locations, a shorter public history and fewer independent reviews than the provider I had been testing. Those were the reasons I had not opened it first.

But it did not begin by asking me to choose a country.

The app presented a small set of situation-based options. I selected the preset for secure browsing on sensitive services and connected.

Then I reopened the tax portal.

The login form appeared.

I entered my PAN and password.

The dashboard loaded.

I selected the prepared return and moved through the income summary, deductions and tax calculation. Each page opened without the DNS error that had interrupted the previous routes.

I reached the declaration.

The VPN was still active.

I clicked Submit.

The portal generated an acknowledgement number.

That was the first result that mattered.

Not a green VPN icon.

Not a server labelled India.

Not a homepage that opened before failing at the next step.

The return had been accepted.

The explanation could wait until after the receipt

Only after the acknowledgement appeared did I look at why the smaller app had worked.

It used HTTP/3-based transport with traffic obfuscation, giving the portal a different connection path from the routes that had repeatedly failed. The practical difference was simple: the browser reached the login, kept the session alive and completed the submission.

I could not see the hotel network’s internal filtering rules or either provider’s complete routing decisions. I could see the outcome: the larger service connected successfully to several VPN servers but repeatedly lost the tax portal, while the smaller app carried the return from login to acknowledgement.

There was still one step left.

I selected e-verification by Aadhaar OTP.

The Wi-Fi dropped during verification

The portal sent the code.

At almost the same moment, the hotel Wi-Fi disconnected.

The browser stopped responding. The network icon changed, and my laptop switched to the phone hotspot I had prepared earlier.

I expected the portal to send me back to the login page.

Instead, the connection paused and resumed.

The verification screen remained open.

The app’s HTTP/3-based connection was built to recover when the underlying network changed. (IETF) Here, that meant the protected session survived the move from hotel Wi-Fi to mobile data.

The OTP arrived on my Indian number.

I entered it.

The portal displayed the verification confirmation and allowed me to download the final acknowledgement.

The time was 11:48 p.m. in India.

Twelve minutes remained.

A fast VPN was not necessarily a usable VPN

Nothing about the first provider appeared generally broken.

Its application connected quickly. Its speed tests were good. Streaming and ordinary browsing worked through every location I tried.

The failure appeared only when I attempted the task that mattered.

That is why a tax portal can stop working with a VPN even when the rest of the internet looks normal. Government and financial services rely on several domains, authentication requests and security checks. If the VPN route mishandles one part of that chain, the homepage may open while the secure session fails.

Changing countries can produce a working route.

It can also create another twenty-minute guessing game.

The useful test is not whether the VPN opens the portal’s front page.

It is whether the same connection completes login, submission and verification.

I had been choosing the wrong kind of control

At the start of the evening, I wanted the reassurance of a familiar provider and a long list of Indian servers.

The list made me feel that one of the options must work.

But every option required another login attempt, another timeout and another decision. The network was large; the path to the tax receipt remained incomplete.

The smaller app offered fewer visible choices.

Its preset opened the portal, carried the return through submission and preserved the verification screen when the laptop moved from hotel Wi-Fi to mobile data.

For this task, control did not mean choosing among more flags.

It meant reaching the acknowledgement before midnight.