Pale Moon forum

Because of a temporary misconfiguration of the unstable builds, it is possible that you are not getting updates automatically any longer for the unstable builds.
This is caused by a tightening of the certificate check when using the internal updater, which is needed in this day and age where anyone and their dog can get a valid SSL certificate mis-issued on domains ({{snide remark about Let's Encrypt! removed}}). The flag to check was enabled before the credentials to check were updated, and a build was triggered in-between those two commits.

Please check if you are being offered updates (help -> about) if your build date is 2017-09-02 or before. If not, go into about:config, and temporarily set app.update.cert.checkAttributes to false, get today's update, then set it back to true.

Moonchild wrote:This is caused by a tightening of the certificate check when using the internal updater

So, this is the latest change on internal updater codebase?

It's the most recent change made to the internal updater system, yes. Why do you ask?

Important: if you have updated the browser today to an unstable version of 2017-10-26, you may be stuck on a version that doesn't get automatic updates because of the change of infra and some unexpected Mozilla-isms in MAR generation.

You need to check the following:

• Go to about:config and check the value of "app.update.channel"
• If it is set to "unstable", you're good. Fast forward past the other points
• If it is set to "default", you're on a limbo version. You need to do the following:
  1. Exit the browser.
  2. Go to the folder where you installed the browser (application folder) or in case of the portable, go to Bin\Palemoon
  3. Go to defaults\pref\ inside that folder
  4. Edit the file "channel-prefs.js" and change the value of "default" to "unstable". Save.
  5. Start the unstable Pale Moon version and go to your about box. You should have an update available.
  6. Update! You're done.

Note that just changing the pref in about:config will not work (another Mozilla-ism getting in the way). You must edit the file as indicated to get out of limbo.