X
Tap here to go to the mobile version of the site.

Support Forum

push.services.mozilla.com/:443

Posted

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.

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
Quote

Additional System Details

Application

  • User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:67.0) Gecko/20100101 Firefox/67.0

More Information

cor-el
  • Top 10 Contributor
  • Moderator
17334 solutions 156717 answers

Helpful Reply

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:

You can disable the Push service to prevent accessing this server. *dom.push.enabled = false You can open the <b>about:config</b> page via the location/address bar. You can accept the warning and click "I accept the risk!" to continue. *http://kb.mozillazine.org/about:config See also: *https://support.mozilla.org/en-US/kb/push-notifications-firefox
Was this helpful to you? 1
Quote

Question owner

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.

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.
Was this helpful to you?
Quote

Question owner

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.

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.
Was this helpful to you?
Quote
cor-el
  • Top 10 Contributor
  • Moderator
17334 solutions 156717 answers

Chosen Solution

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

Setting the serverURL pref might be best, but there is nothing against modifying both prefs. *https://dxr.mozilla.org/mozilla-release/source/dom/push/PushService.jsm
Was this helpful to you?
Quote

Question owner

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

Best regard.

Finally, I chosed serverURL and the problem was resolved. Thanks for your support. Best regard.
Was this helpful to you?
Quote
n5mx 2 solutions 15 answers

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

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
Was this helpful to you?
Quote
Ask a question

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.