Search Support

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

push.services.mozilla.com/:443

  • 6 replies
  • 1 has this problem
  • 668 views
  • Last reply by n5mx

more options

Hi,I'm in trouble about upgrading, Please help..

After upgrading Firefox to 67.0.1, A lot of automatic access to https://push.services.mozilla.com/ came to occur.

As a result, the processing volume of proxy server is frequently exceeded. Delays and failures in web access began to occur frequently.

Please tell me about the causes of frequent access to https://push.services.mozilla.com/ and also please tell me about the resolution.

Thanks for your support.

Chosen solution

Setting the serverURL pref might be best, but there is nothing against modifying both prefs.

Read this answer in context 👍 0

All Replies (6)

more options

You can disable the Push service to prevent accessing this server.

  • dom.push.enabled = false

You can open the about:config page via the location/address bar. You can accept the warning and click "I accept the risk!" to continue.

See also:

more options

Thank you for your support! I'll try this setting today, and monitor web access whole day.

If the problem won't resolve , I'll ask more infomation.

more options

Hi. I post the result. dom.push.enabled = false doesn't work.

I tried 2(two) way. 1.dom.push.serverURL = ""(blank) 2.dom.push.connection.enabled = false

Each result was OK, any web access to https://push.services.mozilla.com/:443 didn't occur at all.

Anybody knows the difference of these two ways? I want to judge which way is better.

Thanks for your support.

more options

Chosen Solution

Setting the serverURL pref might be best, but there is nothing against modifying both prefs.

more options

Finally, I chosed serverURL and the problem was resolved. Thanks for your support.

Best regard.

more options

Many consider those push messages annoying SPAM so they disable it and set the url to sth. like

http://nowhere.LAN

where it goes nowhere (well actually I still did see it in my proxy log) but *.lan is unrouteable