Just to update everyone, if you are getting an SSL certificate error, the site is safe, and you are fine to proceed to use it. I have had to disable Cloudflare, which is a service that helps to protect the Pride of Nottingham site.

I am troubleshooting some issues with the kind help from a dev and I am hoping to find the root cause soon.

However, certain parts of the site might be disabled as the issue is figured out. The site and our SSL certificate will be resolved very shortly. Please bear with me while I try to fix some user issues.

Thanks,
Chris (Pride of Nottingham team)

Thanks for keeping us updated, gaffer. I'm sure you'll get to the bottom of it. Considering how major the upgrade was, there really haven’t been many problems. Best of luck finding out what's causing the trouble.

I couldn't get on for 2 to 3 hours saying there was an error with the site certificate,

Earlier there were problems with the dashboard with some elements not visible.

Thanks for keeping us in the loop. It's much appreciated. Fingers crossed the problem can be sorted without too much trouble.

I couldn’t get on either, but this clears things up. I saw the message about the debugging apps and thought it might be linked.

No harm done, and thanks for keeping us informed.

I appreciate the understanding, and can assure you that even with the SSL certificate error, the site is safe. Cloudflare is again enabled, and I am sorting out the server side of things as I write this.

22 minutes ago, TheSkipper said:

Thanks for keeping us updated, gaffer. I'm sure you'll get to the bottom of it. Considering how major the upgrade was, there really haven’t been many problems. Best of luck finding out what's causing the trouble.

Communication and accountability are two things I believe are very important.

15 minutes ago, Robbie said:

I couldn't get on for 2 to 3 hours saying there was an error with the site certificate,

Earlier there were problems with the dashboard with some elements not visible.

Sorry about that @Robbie, it's me trying to fix things. In the future, I am going to try things more closely in the dev environment to avoid issues like this. At least where possible, as even live sites can have unforeseen issues, but this is related to my investigating. 🙂

No problem @Chris thanks for keeping us all updated. Google can go over the top sometimes with the warnings, but I suppose the warnings are a good thing.

At last I can now navigate the forum on my iPad without getting error messages, thanks for being patient with me while we tried different things @Chris , what a clever chap you are.

Has no one else had these problems? Surely I’m not the only one on here with an iPad?

I'm back to normal too. Thanks @Chris! Although I do miss the frisson of danger that came with the warnings...

Ditto 😉 Thought i was losing me marbles again.

It’s not always been easy for me to get connected, but I understand that the site has had a recent upgrade. It seems something hasn’t worked quite right since, but I’m glad to be kept in the loop.

I’m hopeful the site will be back to normal soon.

On 23/06/2025 at 22:35, Fan of Big Tone said:

Has no one else had these problems? Surely I’m not the only one on here with an iPad?

If any iPad users do have issues, it would be helpful for the gaffer to identify problems.

1 minute ago, TheSkipper said:

If any iPad users do have issues, it would be helpful for the gaffer to identify problems.

Err he's been working on it for the last few days trying to sort it. 😂

@Fan of Big Tone, still no luck?

6 minutes ago, Fan of Big Tone said:

Err he's been working on it for the last few days trying to sort it. 😂

Other team members, Mr. Smarty Pants. 😉

The site has mostly been returned to normal; I will still be trying to find the root cause, but I will be conducting more of the tests off the live site. Trying to replicate the issue is what I am working on right now. It is very important to take bugs which prevent site access very seriously, so I apologise for the issues I have caused looking into this. As I have mentioned before, sometimes the live environment is where the issue lies.

Choosing to ignore such a bug would not be smart.

5 minutes ago, liampie said:

@Fan of Big Tone, still no luck?

Without the actual device, it's very difficult; two devs have tried to help, and I have troubleshooted. I thought I might have had the issue, but it doesn't look like it. It's very challenging to resolve.