Skip to main content

What to do if you can’t access TaxTank while using NordVPN

Learn how to fix TaxTank access issues caused by NordVPN, DNS settings, or Threat Protection so you can load pages, dashboards, and tools correctly.

Updated this week

If you’re using NordVPN, it’s common to run into issues accessing TaxTank even if you’ve turned the VPN off. This usually happens because NordVPN changes your device’s DNS settings, which can stick around and prevent pages or features from loading properly. Don’t worry. These issues are easy to fix.

Common Symptoms

  • TaxTank pages won’t load or get stuck.

  • Forms, uploads, or reports fail to submit.

  • Charts, dashboards, or content appear broken or missing.

  • Switching browsers or devices doesn’t solve the issue.

Quick Fix Steps

1. Reset Your DNS

Even after disconnecting from NordVPN, your device may still use NordVPN DNS servers. Resetting them often fixes the problem.

Windows

  • Open Command Prompt as administrator and type ipconfig /flushdns

  • Restart your browser

macOS

  • Open Terminal and type sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

  • Restart your browser

iOS/Android

  • Turn Wi-Fi off and back on or restart your device

2. Test TaxTank in a Clean Browser Session

  • Try Incognito or Private mode or a different browser

  • Clear your cache and cookies

3. Disable NordVPN Threat Protection (if using the app)

Security features can sometimes block content even when the VPN is off

  • Windows/macOS (website version): Open NordVPN, click the Shield icon, go to Overview, and turn off features one by one

  • iOS/Android: Tap the shield icon and disable Use Threat Protection

4. Switch DNS Settings Manually (if needed)

If problems persist, set your DNS to automatic or a public DNS like Google DNS

  • Primary: 8.8.8.8

  • Secondary: 8.8.4.4

5. Contact TaxTank Support

If TaxTank still isn’t loading:

  • Reach out via our in-app chat or email and include your device, browser, and any error messages

  • We can help confirm whether the issue is DNS-related or something else

Did this answer your question?