Forum adverts like this one are shown to any user who is not logged in. Join us by filling out a tiny 3 field form and you will get your own, free, dakka user account which gives a good range of benefits to you: No adverts like this in the forums anymore. Times and dates in your local timezone. Full tracking of what you have read so you can skip to your first unread post, easily see what has changed since you last logged in, and easily see what is new at a glance. Email notifications for threads you want to watch closely. Being a part of the oldest wargaming community on the net. If you are already a member then feel free to login now.

Mark of Nurgle still on the website.
Still recommended to move to safety.
Still getting virus warnings and data theft risk warnings.

Lego is likely on hols.

Thankfully it isnt worrisome or too intrusive, but every second page redirects to a warning is getting old fast, and I am buffering my replies in case I lose them between page changes.


Automatically Appended Next Post:
....and it just happened now, after pressing send.

Had two interrupts, had to confim that I wanted to proceed to this dangerous website before I could get here.

But while the above message was deliberatelty kept in my text buffer, the post did appear. So data transfer is working normally, only page access is being interrupted.


Automatically Appended Next Post:
..... and happened again.

It appears to be happening every time I post a message.

It has been hanging up on me too.

This is what I get:


***
Your connection is not private
Attackers might be trying to steal your information from www.dakkadakka.com (for example, passwords, messages, or credit cards).

NET::ERR_CERT_DATE_INVALID [blue box containing words 'Back to Safety']

Help me understand [ this is also a hotlink revealing below text:]

***
This server could not prove that it is www.dakkadakka.com; its security certificate expired 2 days ago. This may be caused by a misconfiguration or an attacker intercepting your connection. Your computer's clock is currently set to Saturday, 18 December 2021. Does that look right? If not, you should correct your system's clock and then refresh this page.

Proceed to www.dakkadakka.com (unsafe) [this last line is in grey text to emphasise dodginess].
***

Absolutely identical (barring clock times) to the warning messages received on this thread.

https://www.dakkadakka.com/dakkaforum/posts/list/0/800430.page

I also had to use astersks here because the hypertext is not working, no quote function, text colour changes etc. Basic html only, presumably to spare me or you from cyber-covid.



Send the Yaksignal.

Still getting it here as well. I'll ignore the warning and it'll work a while in that window or one I open via right click through it but it eventually comes back or immediately returns if I refresh the page.

Ditto

happens if I use brave

it's appearing randomly for me too today



a refresh or going back to the page i was on and forward again and its gone so nothing major but useful to get it sorted when Lego has time

Glad I clicked b4 starting another thread about the same issue. I got the screen reported twice today.

Win10
Edge browser
Wifi
Charter Spectrum internet service

Thanks,

Jason

People, the issue is an expired certificate, the problem is on the server side, not on yours.

To explain the problem in the simplest way possible, certificates are files which are created by a certificate authority (https://letsencrypt.org in dakka's case) that allows dakka to identify itself to your browser. Just like an ID, these certificates expire at some point, to make sure that the web page is still under the control of its original owner and that a stolen certificate isn't re-used indefinitely.
The certificate which is causing the problems has expired on the 16th of December.

So, why are we seeing this issue only sometime and not at other times? Hard to tell exactly without knowing the internals of dakka itself. However, most web pages of this size aren't a single application but a number of clones of an application that are accessed through something like a load balancer. The load balancer is kind of like the guy standing in front of the entry queues of an entertainment park telling you to one of the shorter queues when you arrive.

Essentially the load balancer is sending you to a different version of dakka each time you load a page. Nerds like me call those "instances". Most of those instances seem to have a newer certificate which expires in March 2022(see you back here then ), but at least one doesn't. This might either be one of the clones that has not been updated or an older version of dakka that has not been powered down when it should have.

While it's admirable that you are trying to help, further screenshots and browser information will not provide any new information. It's the same problem for everyone.

Is this actually dangerous to someone choosing to ignore the warning? Unlikely, but maybe. While it is likely that this is just yet another expired certiticate that wasn't updated, it also is possible that this instance running the old certificate is not under dakka's control. Since there currently is a major loophole that allows people to hijack webservers with the right tech stack at will, I personally would not take the risk, especially since you can avoid contacting the faulty instance by just refreshing.

Source: I design systems like this for a living. Part of my job is telling people to update their fething certificates.

I was indeed on holiday, sorry and thanks all. One last symptom of the server move was the SSL updater had gotten glitchy. All fixed now and for the future, thanks!

Was just about to post that I hadn't gotten the message tonight. Woohoo! Lego has freed us from the tyrannical certificate overlords! It's a Festivus miracle.

Yeah I always get that from Dakka - old coding I guess for google chrome

...but I enjoyed my dreams of going against the scheme of Tzeentch or the rot of Nurgle infesting my favored digital hive of scum and villainy...

I started getting general https problems sometime this past Fall, I want to say it must have been early October or late September.

A lot of sites changed in this way, for me, with some that are no longer functional as they were before that. For instance, there is a real estate site that I hade been using and now on the laptop - after the safety warning - it doesn't render properly, and many functions are not available. On the phone, on the tablet, no problem. Trouble is likely that this is an older operating system, no longer updated.

I read around and found that something changed, around the world and not just local to Dakka... I had not had anything like this happenn before that time, iirc, Dakka or really anywhere else.

So, I am wondering if these two things are related?

It's likely that when you are running an outdated system that your browser is outdated as well. When pages updated to support https (or demised other outdated technologies), they most likely also updated other parts of their system which your browser doesn't know how to display properly - newer html5 and javascript features come to mind.

So, no they are not. Your system simply can't handle modern web technology and https is merely a part of that.

Yeah, my browser likes https, but gives me warnings for sites that seem not to comply with what it’s expecting, so after passing safety screen it displays those pages with https crossed out in the url and with less functionality.
Something changed worldwide this last fall, and I had begun getting that safety warning about dakka at that same time…

Most pages and sites display without trouble, https being the first letters of these urls.

Don't take this as a personal attack, but I doubt that I could explain the problem to you in a way that you would understand. There is just too much of a knowledge gap. If you are still curious, I suggest watching some videos explaining what HTTPS is.

The only things I can tell you is that when a page works fine on your tablet, but not on your PC, it's extremely likely that your system is the issue.

If you want the web to work properly, you should be running a current OS with the most recent version of a modern browser.

And I assure you that absolutely nothing changes worldwide within a single season
It's most likely just the time that your system started being so outdated that it could no longer display modern pages.

I understand man. Just sayin this dakka thing started for me on my laptop same time other sites started acting screwy. Not happening with other devices. I will search up again what the big web change was this past Fall. Will post a link here when I find it again. Late here now so tomorrow I will try to get that done.

 Jidmah wrote:
Don't take this as a personal attack, but I doubt that I could explain the problem to you in a way that you would understand. There is just too much of a knowledge gap. If you are still curious, I suggest watching some videos explaining what HTTPS is.

For what it's worth, I think the longer explanation above about instances made perfect sense but I admit that's only because I know the basics of what an 'instance' is because of video games and such XD

 LordofHats wrote:

 Jidmah wrote:
Don't take this as a personal attack, but I doubt that I could explain the problem to you in a way that you would understand. There is just too much of a knowledge gap. If you are still curious, I suggest watching some videos explaining what HTTPS is.

For what it's worth, I think the longer explanation above about instances made perfect sense but I admit that's only because I know the basics of what an 'instance' is because of video games and such XD

Thanks for the feedback - and it's actually quite likely that an instance in a video game and an instance of a web service is the exact same thing. Essentially the entry portal (or whatever your game is using) would be the load balancer that is distributing groups of players to different instances of your game.

This is when I started seeing problems, and the broad issue to which I had been pointing, no load balancer invoked:

The “Your connection is not private” error made headlines in September 2021, thanks to the scheduled expiration of the digital certificates issued by Let’s Encrypt.

Let's Encrypt is one of the biggest issuers of the HTTPS certificates that encrypt or scramble the connections between your smartphones, laptops and other devices and the Internet. These certificates and the encryption they provide ensure that snoops can't steal your data as you search the web.

Thanks to these certificates, cybercriminals can't read your log-in information when you connect to your online bank, snatch your passwords when you sign into your online credit card portal or snoop on emails between you and your healthcare providers.

In late September, though, Let's Encrypt saw its root certificate expire. Those relying on older devices to connect to the Internet, then, might have seen an increase in the number of "Your connection is not private" errors as they searched the web.

The root certificate that Let's Encrypt uses — known as the IdentTrust DST Root CA X3 — was scheduled to expire on September 30, which it did. Because of this, computers, devices, and browsers after this date no longer trust the certificates that had been issued by Let's Encrypt. Tech experts say this wouldn’t cause problems for most consumers. But they did say that devices running older software, such as older model smartphones, are most likely to see more “Your connection is not private” errors because of the Let’s Encrypt certificate expiration.

https://us.norton.com/internetsecurity-how-to-your-connection-is-not-private.html

Interesting.

The issue is still your system though - you are stuck with a certificate that has it's certificate authority expired, which makes any certificate issued by that authority invalid. It's like an old country-specific drivers license that has been replaced with the EU drivers licenses. Drivers licenses that have been issued by countries after a certain date are just no longer valid.
Old OS and browsers cannot handle that issue, newer ones would automatically get a new certificate from the webpage and store them on your device.

For those pages not working properly, you can try deleting the expired certificates manually, which will then cause your browser to pick up new ones.

I'd still heavily suggest updating to a newer operating system and browser or disconnect that device from the net for good.

Yes I think that you are correct. Deleting manually and/or upgrading is where I left it. I have too much work to do on that machine to bother just now with some web weirdness. My research is so far unaffected. I am waiting for either intel’s or amd’s answers to the m1, picking up an m1 system or waiting for the m2s, or maybe both. Anyways, neither here nor there…

Someone forgot to put gasoline in the modem.