Apps work but the browser doesn't
If native apps (Instagram, WhatsApp, etc.) work fine on your Eflexsim cellular but the browser (Safari, Chrome) won't load any website, the cause is almost always one of three things: a captive-portal prompt your browser is silently waiting for, a DNS issue specific to the browser's handling, or a certificate trust problem on the partner network. Captive portal is by far the most common; the fix is usually to navigate to a non-HTTPS site (like example.com) which triggers the portal prompt.
Below: each cause in detail, the fix, and what to do if none of them apply.
Why apps work but the browser doesn't
This pattern is more specific than "no internet" because most apps use a small set of network operations (HTTP/HTTPS to specific servers) while browsers use many more network features. When a layer specific to browsers breaks, apps keep working through their fixed servers but the browser fails on every site.
The three usual suspects:
1. Captive portal not triggering. Some networks (especially hotel Wi-Fi, some airport networks, and rarely some cellular carriers) require a one-time login or terms acceptance via a captive portal. Browsers usually trigger the portal automatically, but if the portal redirect breaks, you get "no internet" in the browser even though direct app traffic works.
2. DNS issue specific to browser handling. Browsers often use DNS-over-HTTPS (DoH) by default, routing DNS through a specific provider's HTTPS endpoint. If that endpoint can't be reached on the partner network, the browser fails while apps using system DNS keep working.
3. Certificate trust issue. Less common: the partner network is doing some kind of HTTPS interception or you've installed a corporate certificate that conflicts with browser security checks.
Fix 1: Trigger the captive portal manually
If a captive portal is the issue, you need to force the browser to load a non-HTTPS site to trigger the redirect.
Try this:
- Open Safari or Chrome.
- In the address bar type:
http://example.com(NOT https โ the http is important). - Press Go.
If a captive portal exists, it will redirect you to the portal page. Accept terms, log in, or just dismiss the page if it's already cleared. Browser traffic should now work.
Other useful test URLs (all non-HTTPS):
http://neverssl.comhttp://detectportal.firefox.comhttp://captive.apple.com
These exist specifically to be plain HTTP and trigger captive portals.
Fix 2: Disable browser DNS-over-HTTPS
If the browser is using DoH and the partner network blocks or doesn't route the DoH endpoint, disabling DoH temporarily falls back to system DNS (which usually works).
Chrome (desktop and mobile):
- Open Chrome settings.
- Privacy and security โ Security.
- Find "Use secure DNS" and toggle off.
- Restart Chrome.
Safari:
Safari doesn't expose DoH controls directly; iOS handles DNS at the OS level. Toggling Settings โ General โ VPN & Device Management โ check for any DNS profile installed and remove it.
Firefox:
- Settings โ Privacy & Security โ DNS over HTTPS.
- Select Off temporarily.
After disabling, try loading a website. If it works, DoH was the problem. You can re-enable DoH with a different provider (Cloudflare, NextDNS) once you're back on Wi-Fi.
Fix 3: Clear browser cache and cookies
Stale browser state sometimes causes weird "won't load anything" behavior. Clearing it removes that variable.
Safari (iPhone):
- Settings โ Safari โ Clear History and Website Data.
Chrome (mobile or desktop):
- Settings โ Privacy and security โ Clear browsing data โ All time.
- Check Cookies, Cached images.
- Click Clear data.
This is a sledgehammer approach but rules out a stale-cache issue.
Fix 4: Try a different browser
If Safari fails, try Chrome. If Chrome fails, try Firefox or Edge. If only one browser fails, it's a browser-side issue (likely cache or a setting). If all browsers fail, the issue is below the browser layer (DNS, captive portal, or partner network).
Fix 5: Restart the phone
As with most network issues, a full restart clears the most categories of stuck state. Power off, wait 30 seconds, power back on, and test again.
What this isn't
If apps ALSO don't work, this isn't the right troubleshooting article. See data is on but apps won't connect instead.
If the browser is slow but does load, see why are my eSIM speeds slow.
If specific apps fail (not browser-wide), see app-specific troubleshooting. For example, iMessage and FaceTime have known issues on travel eSIMs documented in iMessage and FaceTime not working with your eSIM.
Country-specific browser blocks
A few countries block specific sites at the network level regardless of carrier:
- China: blocks Google, Facebook, Instagram, YouTube, WhatsApp, many news sites, and most VPNs. Eflexsim plans for China have to work within these rules.
- Iran, North Korea: broad blocks on Western services.
- Russia: rotating blocks on various sites.
- Turkey, UAE: occasional blocks on specific services or VoIP apps.
If a specific blocked site fails but others work, that's the country's policy, not a phone issue. A VPN to your home country usually bypasses, though VPN legality varies by country.
Frequently asked questions
QWhy does the browser specifically fail?
Browsers use more network features than apps (DoH, certificate checking, captive portal handling, multiple protocols). Any of these breaking causes the browser to fail while apps keep working.
QWill reinstalling Safari or Chrome fix it?
Probably not. The issue is network-side, not the browser itself. Try the network fixes first.
QShould I use mobile data or Wi-Fi to fix this?
You're already on cellular by assumption. The fixes are cellular-relevant. If Wi-Fi works in your hotel, use that as a temporary backup while troubleshooting.
QWhy does HTTPS specifically fail when HTTP works?
If only HTTPS fails, that's often a certificate trust issue or HTTPS-aware filtering on the network. Try loading a known-good site like https://www.google.com to confirm.
QDoes my phone need to be restarted after a captive portal login?
Usually no. The browser session continues normally once the portal is dismissed.
QWhy doesn't the captive portal appear automatically like at home?
iOS and Android usually auto-trigger the portal, but it depends on the network handshake. Some networks don't include the standard captive-portal signals, so the device doesn't know to open it.
For broader app failures, see data is on but apps won't connect. For slow speeds, see why are my eSIM speeds slow. For total signal loss, see my eSIM has no signal.
Was this article helpful?
Your feedback helps us write better guides.
Heading somewhere new?
Browse plans for 200+ destinations. Active before you've cleared customs.
Browse destinations