[SOLVED] future error problems but clocks are set accurately

Users and developers helping users with generic and technical Pale Moon issues on all operating systems.

Moderator: trava90

Forum rules
This board is for technical/general usage questions and troubleshooting for the Pale Moon browser only.
Technical issues and questions not related to the Pale Moon browser should be posted in other boards!
Please keep off-topic and general discussion out of this board, thank you!
dcc701

[SOLVED] future error problems but clocks are set accurately

Unread post by dcc701 » 2015-03-31, 16:15

I'm on puppy tahr w latest palemoon update. Using Palemoon for first time in recent days.
Get future response errors on a lot of pages, including sign-in page for this forum and the palemoon add-ons page.
(Error code: sec_error_ocsp_future_response)
However, my hw and desktop clocks are accurate and agree.

If I untick OCSP validation, then I can view pages. I'm pretty ignorant of these matters, but I guess that is not a good permanent fix.
Not having the same problem in another browser I use.

Another non-permanent workaround is that if I use "psync time server synchronisation" utility in puppy, then the pages load fine, but my desktop clock is catapulted 15 hours into the future (hw clock is unaffected).

Insight or fixes, anyone?
Last edited by trava90 on 2015-04-02, 04:35, edited 1 time in total.
Reason: Marked SOLVED

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 35477
Joined: 2011-08-28, 17:27
Location: Motala, SE
Contact:

Re: future error problems, but clocks are set accurately

Unread post by Moonchild » 2015-03-31, 16:24

Is your time zone also set correctly?
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite

dcc701

Re: future error problems, but clocks are set accurately

Unread post by dcc701 » 2015-03-31, 16:43

Hi Moonchild--thanks for reply and tip.
I reset the time zone in Set Timezone in pup and the problem is solved.
I had set it earlier during initial pup set up a few days ago to "Los Angeles, GMT-8"
However apparently the initial set up was somehow defective or I did something wrong.
The option listed now in Set Timezone is currently called "America/Los Angeles". Chose that, rebooted. Now works well.

Locked