Motorola phone internet stopped after restart — what to check safely next

Hey! If your Motorola phone internet stopped after a restart, we can narrow it down safely without doing anything extreme (no “factory reset” advice, no random setting-flipping). First, I want to identify which “internet” layer failed, because Motorola devices can show very different symptoms depending on whether it’s Wi-Fi, mobile data (LTE/5G), DNS/VPN, or a carrier provisioning/APN issue.

A few common patterns after a reboot:
• Wi-Fi connects but pages won’t load: captive portal, router/DNS issue, Private DNS, VPN, or “Connected without internet.”
• Cellular shows bars/4G/5G but data doesn’t work: mobile data toggle/data limit, APN mismatch, SIM not fully registered, carrier settings not applied yet, roaming rules, or temporary network registration glitch.
• Everything looks “connected” but apps can’t reach the internet: VPN, Private DNS, Data Saver restrictions, or an app firewall/parental control profile.

Quick questions so we choose the right checks and avoid doorway-ish “try everything” steps:
1) What Motorola model (Moto G / Edge / Razr) and Android version if you know it?
2) After the restart, is the problem on Wi-Fi, mobile data, or both?
3) What do you see in the status bar: LTE/5G icon, any ! on the signal, or “Connected without internet” on Wi-Fi?
4) Did this start right after an Android update, SIM swap, new eSIM, traveling/roaming, or enabling a VPN/Private DNS?

That’s a helpful detail: if Wi-Fi looks connected and LTE is showing but both fail to load anything, it often points to something “above” the connection layer—like VPN, Private DNS, a profile/app that filters traffic, or a system setting that blocks background data. A restart can re-enable a VPN automatically or switch DNS behavior, so we’ll check those first (safe, reversible).

Safe Step 1 — Quick “is it DNS/VPN?” test (no permanent changes)
• Do you see a key icon (VPN) in the status bar, or a VPN app notification after reboot?
• In Settings, do you have Private DNS set to something like “hostname” instead of Automatic/Off?

I’m not asking you to delete anything yet—just tell me what you see. Also: does anything work at all (for example, can you open a speed test app, or do you get a “No internet” error everywhere)?

Got it. The “no connection everywhere” symptom still fits DNS/VPN, but it can also be a router-side issue on Wi-Fi plus a separate registration hiccup on LTE. So we’ll split the diagnosis cleanly.

Safe Step 2 — Separate Wi-Fi vs mobile data (fast isolate)
1) With Wi-Fi ON, try opening your router’s captive portal scenario: does the Wi-Fi network show “Connected without internet” anywhere in the Wi-Fi details?
2) Then turn Wi-Fi OFF (only), keep LTE/5G on, and see if a single lightweight thing loads (even a weather card or a simple webpage).

If neither works, I want one more clean check: do you have Airplane mode available as a quick tile? A short Airplane-mode cycle can force a fresh network registration (it’s a diagnostic tool, not a “magic fix”). Before you try it: are you traveling/roaming right now, or is this your normal area?

Thanks—being at home rules out a bunch of roaming edge cases. Since both Wi-Fi and LTE fail, we’ll check two “system-wide blockers” next: Data Saver / background data restrictions and Private DNS.

Safe Step 3 — Check for system-wide internet blockers (Motorola/Android)
• Data Saver: if it’s enabled, some apps behave like there’s “no internet,” especially right after a reboot when background sync is restricted. If it’s on, don’t change it yet—just note it.
• Private DNS: if it’s set to a custom hostname (common with ad-block DNS), a restart can make it fail and break browsing on both Wi-Fi and mobile data. Again, just tell me whether it’s Automatic/Off vs custom.

Also, one subtle clue: when you try to load a page, do you get a “DNS” style error (like “server IP address could not be found”), or is it just spinning/timeout?

That’s a strong lead. A custom Private DNS hostname is one of the few settings that can break internet access on both Wi-Fi and LTE/5G at the same time—especially after restart if the resolver becomes unreachable. I won’t push you into flipping it blindly here, but it’s very likely the “why now” trigger.

Safe Step 4 — Confirm if Private DNS is the culprit (controlled test)
The safest way is to do a temporary change and immediately retest (so you can revert if needed):
• Note the exact hostname currently set.
• Switch Private DNS to Automatic (or Off, depending on what your Moto G offers).
• Test one thing on Wi-Fi, then one thing on LTE (with Wi-Fi off).

If that restores internet, you’ve identified the cause (then the “next step” is deciding whether to use a different hostname or let it stay Automatic). If it doesn’t restore internet, we move to the next likely bucket: APN/carrier registration for LTE plus possible Wi-Fi DNS/router issues.

Before you try that: did this begin after a recent Android update or only after the restart you did today?

That timeline matches a settings-layer trigger perfectly. While you do that controlled test, here’s the “if it’s still broken” branch—so you’re not stuck.

Safe Step 5 — If LTE shows but mobile data won’t work: what we check next
On Motorola phones, “LTE icon present but no data” often comes from one of these after a reboot:
• APN missing/changed (Access Point Name): data can look “connected” but routing never starts.
• SIM registration glitch: the phone shows signal, but the data session doesn’t establish until it fully re-registers.
• Carrier/account provisioning: your plan line temporarily isn’t authorized for data (rare, but it happens).

Safe observations to report (no risky edits yet):
• Does the Moto G show a data indicator that changes (LTE ↔ 3G ↔ nothing)?
• Can you send/receive SMS (texts) during this problem? (It helps separate data vs full service.)
• Is the APN list present under the mobile network settings, and does it look like it belongs to your carrier (name matches carrier brand)?

If you tell me those outcomes, I can advise which next step is safest: a simple re-registration attempt (Airplane cycle), APN review, or preparing for a network reset (which has side effects).

Calls + SMS working is a great sign: the SIM is recognized and the line is active. The weird part is still “both Wi-Fi and LTE fail,” which keeps pointing back to DNS/VPN/proxy style interference more than a carrier-only issue. Private DNS is still the top suspect based on what you found.

Safe Step 6 — One more system check that can mimic “no internet”
• If you use any ad blocker, firewall, security/VPN, or “data optimizer” app: after a reboot it can auto-start and block traffic until it’s re-authorized. That affects both Wi-Fi and mobile data.
• Also check whether a proxy is set on your Wi-Fi network (some networks keep an old proxy configuration). You don’t need to change it—just confirm whether Proxy is “None” vs “Manual.”

If Private DNS set back to Automatic restores internet, we’ve basically solved the mystery without doing any destructive steps. If it doesn’t, the next safe-but-bigger diagnostic step is a network settings reset—but I only recommend that once we’ve written down what it will wipe (Wi-Fi passwords, Bluetooth pairings, sometimes APNs).

Do you want the “minimal-risk checklist” you can follow right now (no wipes), and then a separate “prepare for reset” checklist only if needed?

Totally fair. Here’s the minimal-risk diagnostic checklist for a Motorola where internet stopped after restart—no wipes, no “nuke it” steps, just controlled observations and reversible tests:

1) Confirm the scope (1 minute)
• Test Wi-Fi ON, then Wi-Fi OFF (LTE only). Note which one fails (you already did—both).

2) Check VPN / Private DNS status (2 minutes)
• Look for any active VPN indicator or VPN app notification.
• Private DNS: note if it’s set to a custom hostname. If yes, temporarily switch to Automatic and retest Wi-Fi and LTE separately (then you can decide whether to restore the hostname).

3) Check app-level blockers (2 minutes)
• Any firewall/adblock/security app that “filters internet”? If yes, check if it’s running and whether it shows blocked traffic right now.

4) Quick network refresh (optional, low risk)
• One Airplane-mode toggle cycle can force a new registration. If your issue is DNS/VPN, it won’t help; if it’s a stale session, it sometimes changes symptoms (useful info either way).

5) Gather details if it persists
• Screenshot: Private DNS setting page, VPN page, and Mobile Network/APN page. An expert can tell immediately if something looks off for your carrier without you editing APNs blindly.

If you’d like, paste what your Private DNS option shows (Automatic/Off/custom hostname) and whether your VPN app is set to “always-on” or “auto-connect.” That usually explains the “worked before reboot, broke after reboot” story.

Good question—and it’s exactly why I treat “reset network settings” as a planned step, not a first reaction.

A network settings reset (on Motorola/Android) typically does not delete photos, messages, or apps. It mainly resets connection-related items like:
• Saved Wi-Fi networks and passwords
• Bluetooth pairings
• Some cellular settings (and in some cases APNs you added manually)

It can be the right diagnostic move when internet fails after restart and we suspect a corrupted network config—but only after the smaller checks (Private DNS/VPN) because those don’t require re-entering anything.

If you get to that point, the best “next” step is to write down: your Wi-Fi password(s), whether you use an eSIM, and whether your carrier requires a specific APN. Then you can do the reset with minimal hassle—or ask an expert to confirm you’re not about to wipe an APN you’ll need to re-enter.