Mozilla will shut down Pocket’s services on July 8, 2025. At that time users will no longer be able to access the Pocket website, apps and API. You can export your saved items and API data until October 8, 2025 before they are permanently removed. For more information, see this article.

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

I started getting a message at the top of my screen: You must log in to this network before you can access the Internet."

I started getting a message at the top of my screen: You must log in to this network before you can access the Internet." it goes away after a few seconds and i can use the browser without trouble, but why is this happening when it never has before?

I started getting a message at the top of my screen: You must log in to this network before you can access the Internet." it goes away after a few seconds and i can use the browser without trouble, but why is this happening when it never has before?

Chosen solution

This is about network detection done by Firefox on startup.

See Network Detection:

You can set network.captive-portal-service.enabled = false on the about:config page to disable this fesature.

You can open the about:config page via the location/address bar. You can click the button to "Accept the Risk and Continue".

Read this answer in context 👍 2

All Replies (4)

This could be a message from your ISP, or are you using a proxy?

FredMcD said

This could be a message from your ISP, or are you using a proxy?

no I am not using a proxy

Chosen Solution

This is about network detection done by Firefox on startup.

See Network Detection:

You can set network.captive-portal-service.enabled = false on the about:config page to disable this fesature.

You can open the about:config page via the location/address bar. You can click the button to "Accept the Risk and Continue".

Thanks for the help, glad to know its not malware. Adjusting the setting in about:config looks to have resolved the issue.