Howdy, Stranger!
We are about to switch to a new forum software. Until then we have removed the registration on this forum.
Categories
- All Categories 25.7K
- Announcements & Guidelines 13
- Common Questions 30
- Using Processing 22.1K
- Programming Questions 12.2K
- Questions about Code 6.4K
- How To... 4.2K
- Hello Processing 72
- GLSL / Shaders 292
- Library Questions 4K
- Hardware, Integration & Other Languages 2.7K
- Kinect 668
- Arduino 1K
- Raspberry PI 188
- Questions about Modes 2K
- Android Mode 1.3K
- JavaScript Mode 413
- Python Mode 205
- Questions about Tools 100
- Espanol 5
- Developing Processing 548
- Create & Announce Libraries 211
- Create & Announce Modes 19
- Create & Announce Tools 29
- Summer of Code 2018 93
- Rails Girls Summer of Code 2017 3
- Summer of Code 2017 49
- Summer of Code 2016 4
- Summer of Code 2015 40
- Summer of Code 2014 22
- p5.js 1.6K
- p5.js Programming Questions 947
- p5.js Library Questions 315
- p5.js Development Questions 31
- General 1.4K
- Events & Opportunities 288
- General Discussion 365
"forum.processing.org uses an invalid security certificate."
forum.processing.org uses an invalid security certificate.
The certificate expired on 11 March 2018, 23:59. The current time is 12 March 2018, 09:35.
Error code: SEC_ERROR_EXPIRED_CERTIFICATE
Comments
@koogs===
i get the same...
I had to move to another browser in order to have the option to assign an exception for the forum's expired certificate. [-(
main processing.org site is ok, forum.processing.org isn't
It's fixed now! Back to my main browser!!! <:-P
I ran into the same issue. Thxs for the updates @koogs @akenaton @GoToLoop
Kf
I had it too
Yes, I think this was resolved.
Last night I was getting incorrect time errors on mobile Chrome (not Safari) -- it seemed as if (?) the server time had not updated to match daylight savings, triggering an error. Chrome's guess was that my system clock was incorrect -- although it was not.
The certificate had expired; I replaced it earlier today.
thank you!