Portal loads for 10 seconds then reloads itself in a loop — cause and fix

[StreamKing]

My MAG shows the portal loading screen, briefly flashes the channel list, then reloads. This has been happening for two days. Was working fine before.

 

[MeshMaster]

Looping portal reload is usually a session token issue. The portal authenticated but when it tries to fetch channel data the token expires or is rejected.

 

[SpeedTest_Kim]

Had this exact issue. It started after my provider's system updated. The session timeout setting changed on their end.

 

[BobWifi]

Contact your provider support first and describe the exact behavior. They can check server-side logs to see what is happening during the reload loop.

 

[TechDad_Bill]

Before contacting support, try clearing the MAG browser cache:
1. Settings → Advanced Settings → Clear Cache.
2. Also clear the portal cache if that option is available.
3. Perform a full power cycle after clearing.
If the loop started recently, a corrupted cache entry is a common cause.

 

[LauraTech]

Is the looping happening at a specific time of day or is it continuous?

 

[LindaForum]

Important question. Looping only at certain times usually indicates a server load issue on the provider side. Continuous looping is more likely a local device or account issue.

 

[AppWizard]

My loop was time-based — happened between 7pm and 10pm but not during daytime. That was a clear sign of server congestion, not a device issue.

 

[RyanBuffer]

I solved my continuous looping by factory resetting the MAG and re-entering credentials. Something in the local storage had corrupted.

 

[DianaTV]

If factory reset is needed:
1. Back up your portal URL and any custom settings.
2. Settings → Advanced Settings → Factory Reset.
3. After reset, only enter the portal URL — nothing else initially.
4. If the loop persists after a clean factory reset, the issue is server-side.

 

[EricNetPro]

After a factory reset and re-entry, my portal worked fine. But the channel list was shorter — turned out the provider had changed which channels were in my package. Nothing was actually broken.

 

[GregWifi]

Interesting edge case. A channel count change after a reload loop can confuse users into thinking there is a persistent issue.

 

[LisaCache]

SOLVED: Provider confirmed a server migration that changed session handling. They pushed an update and the loop resolved within 24 hours. No action needed on my end.

 

[SuzieQ_Tech]

Good to document server-side resolutions. Shows that not every MAG issue is a local problem.