The Lemon Fool

moorfield wrote:Anyone else having problems using Chrome today?

NET ERR CERT COMMON NAME INVALID

IE and Firefox seem ok.

I have similar problems using Firefox. Sometimes I sail through, sometimes I get an error message:

Warning: Potential Security Risk Ahead

Firefox detected a potential security threat and did not continue to http://www.lemonfool.co.uk. If you visit this site, attackers could try to steal information like your passwords, emails, or credit card details.

What can you do about it?

The issue is most likely with the web site, and there is nothing you can do to resolve it. You can notify the web site’s administrator about the problem.


I've deleted the LMF cookies, but it makes no difference, the problem is deeper and appears to be almost random. I might be able to post this - I might not. If not, I will wait a while, and then Firefox will let me through security. You'd expect such a thing to either work or not work, but not vary.

Infrasonic wrote:If anyone is still getting cert/404 issues on Android devices try settings/storage/apps and then on each browser app clear cache.
Restart (cold boot) your device.

Some combinations of browser and internet provider still don't work and no amount of fiddling with cache etc will fix it.

Non-technical users out there will be assuming the site has been dead for days and there's a danger they'll be permanently lost.

Hopefully the issue will be fixed centrally before too long.

Scott.

Still getting problems, works most of the time, but ten minutes ago Windows 10 on my Surface Pro, Edge, protested strongly, No Certificate, site not secure, etc...It had worked well for an hour before that. My iPad Pro, Safari, also has its moments with it too, can't test currently as my wife is using it at the mo looking at elections data, and our two ISAs, which have gone crazily up, being 'FTSE250 richer.'

So I would say Lemonfool not rock solid yet at all. But way better than yesterday, when it mostly failed on both tablets.

Bagger

I've just run a load of MX toolbox diagnostics on the domain, everything on the DNS and web server side is fine, Green ticks all the way.

The only issues being flagged are 3 minor email ones.1 SPF and 2 DMARC.

Infrasonic wrote:I've just run a load of MX toolbox diagnostics on the domain, everything on the DNS and web server side is fine, Green ticks all the way.

The only issues being flagged are 3 minor email ones.1 SPF and 2 DMARC.

That's as may be, but there's obviously still a problem somewhere, that end users can't circumvent.

Scott.

swill453 wrote:

Infrasonic wrote:I've just run a load of MX toolbox diagnostics on the domain, everything on the DNS and web server side is fine, Green ticks all the way.

The only issues being flagged are 3 minor email ones.1 SPF and 2 DMARC.

That's as may be, but there's obviously still a problem somewhere, that end users can't circumvent.

Scott.

You can sit there commenting negatively on my posts all day or actually do something positive to try and help others...

Infrasonic wrote:You can sit there commenting negatively on my posts all day or actually do something positive to try and help others...

I don't mean to come across negative to you, but it's the "others" who can't even see this thread I'm concerned about. A proportion of users will simply think the site is dead, and nothing you or I can do will help them.

I'm kind of hoping the problem can be fixed by those with the actual capability to do so. And my reason for posting is to keep the conversation going so there's no misconception that all is well.

Scott.

I now seem to have stable access on both Windows10/Edge (two PCs) and Android/Chrome (1 phone)
And the Site seems to be a lot zippier - thanks

Finally managed to get back in.

I initially thought the problem was that someone had forgotten to reduce the TTL on the lemonfool.co.uk DNS entry from 24hrs to a much smaller value at least 24 hrs before starting the migration to new servers/ip addresses which would mean that the new addresses wouldn't propogate for upto 24 hrs depending on when the old cached values timed out. However although that may have been one of the problems there were obviously others.

swill453 wrote:

Infrasonic wrote:You can sit there commenting negatively on my posts all day or actually do something positive to try and help others...

I don't mean to come across negative to you, but it's the "others" who can't even see this thread I'm concerned about. A proportion of users will simply think the site is dead, and nothing you or I can do will help them.

I'm kind of hoping the problem can be fixed by those with the actual capability to do so. And my reason for posting is to keep the conversation going so there's no misconception that all is well.

Scott.

Agreed.

But...there are posters who have partial access, some devices, some browsers, but not across the board. I'm making suggestions based on what has worked for me.
I have access on all devices (W10/Chrome OS/Android) with all browsers now, consistently, but I worked around the certificate and 404 alerts that I was getting. It may not work for everyone, but that doesn't mean don't try...

There are posters accessing this thread with less technical knowledge who may be under the impression that the web servers are up the swanee (they were for a while with loads of DNS issues and a certificate issue), that is no longer the case, so I'm reporting it.

There will be downstream ripple issues that are out of Stooz's hands, but all of that side of things is currently a bit of a 'known unknown'.

Presumably if Stooz has access to the registered posters traffic numbers then he'll be able to work out how many regulars still aren't accessing the site and act accordingly (if it's within his control).
For the casual visitor checking the various search engine results regularly should reveal any access issues from that angle.

Sorry to say but emails are not going out yet so there will be registration and reminder/password reset difficulties - please bear with me.

monabri wrote:Windows 10 & Chrome seems to work ok but on my Android Tablet I need to go into incognito mode.

All seems OK now (including Tablet & mobile phone - both Android OS).


monabri

Infrasonic wrote:
There are posters accessing this thread with less technical knowledge who may be under the impression that the web servers are up the swanee (they were for a while with loads of DNS issues and a certificate issue), that is no longer the case, so I'm reporting it.

And if any of them want to gain more technical knowledge of Domain Name Servers, the Internet documents RFC 1034 and RFC 1035 should provide some excellent bed time reading .

scotia wrote:

Infrasonic wrote:There are posters accessing this thread with less technical knowledge who may be under the impression that the web servers are up the swanee (they were for a while with loads of DNS issues and a certificate issue), that is no longer the case, so I'm reporting it.

And if any of them want to gain more technical knowledge of Domain Name Servers, the Internet documents RFC 1034 and RFC 1035 should provide some excellent bed time reading .

Isn't the whole point of the internet that the average user doesn't need to know things like that?

45 years ago when I was at University, if I wanted to do some computing (as it was quaintly known back then), I'd have to book time on the department's DEC PDP-8 (correct me if I am wrong about that; it is from memory) and then punch up some holes in cards or tape to get a printed output.

32 years ago, I got my first use of a PC, thanks to work. I didn't buy my own machine until 2001.

In 1996 I used the internet for the first time.

All the above required specialised knowledge. Now even my 88 year old aunt uses the internet and is on WhatsApp. It's supposed to be easy.

PS: No criticism of stooz intended or should be inferred. It's all voluntary effort; we know this.

PPS: Two of my three machines are still giving me "security risk" warnings, but the third (newer) one is not. I'm sure it will all fix itself in time.

Http is incorrect, you should be directed to Https
Hence the browser warning.
Chrome had taken it upon themselves to warn everyone is sites that aren't https

Lootman wrote:

scotia wrote:And if any of them want to gain more technical knowledge of Domain Name Servers, the Internet documents RFC 1034 and RFC 1035 should provide some excellent bed time reading .

Isn't the whole point of the internet that the average user doesn't need to know things like that?

And I thought I was providing an excellent cure for insomnia

Being less frivolous, I should add that in technology time scales, these (published 1987) are positively ancient now - for during the intervening thirty odd years the Internet has expanded almost beyond comprehension. Yet the ground rules they laid down still work today. Back in those early days the big industrial computing companies and international standards agencies thought that the internet was run by a bunch of amateurs, and they could do significantly better. But they all dropped by the wayside, and the "amateurs" triumphed. I'm extremely impressed by the quality of their initial work which has allowed the internet to prosper.

As you will see from my duplicated entry, I am having some problems in submitting responses - the waiting circle goes round and round and round, then eventually the response is published and displayed - or in the above case it does not appear to have been published, so I pressed the submit button again, and there are now two entries.

stooz wrote:Http is incorrect, you should be directed to Https
Hence the browser warning.

Yes, http://www.lemonfool.co.uk should auto-redirect to https://www.lemonfool.co.uk. It does for me on both Waterfox and Chrome on W10. So the question is why isn't it doing so for some people?

I can record that for the first time since the outage, I have had a free of hassle day on my desktop, my laptop and my Ipad. I do not want to sound smug but for me it seems that TLF is back to normal.

Dod

Dod
My experience also, all good for me on Friday too.