topic Re: Here we go again in Get Support

Here we go again

will13am — Wed, 05 Jan 2022 15:39:05 GMT

The screen cap says it all.

Re: Here we go again

gblackma — Sun, 16 Feb 2020 14:50:17 GMT

Could be wrong @will13am , but the last time this happened, the consensus was to ignore it and continue. Out of curiosity did your browser receive an update? And which browser are you using?

@will13am wrote:
The screen cap says it all.

Re: Here we go again

will13am — Sun, 16 Feb 2020 15:13:16 GMT

@gblackma wrote:
Could be wrong @will13am , but the last time this happened, the consensus was to ignore it and continue. Out of curiosity did your browser receive an update? And which browser are you using?
@will13am wrote:
The screen cap says it all.

Running latest version of chrome on my phone which is on android 10. I cannot ignore and move on. Deleting cache, rebooting and other fidgety techniques eventually overcomes the problem. It's only a forum. I would crap myself if this was a bank website.

Re: Here we go again

gblackma — Sun, 16 Feb 2020 15:42:23 GMT

@will13am I'm not getting the same PM message logging into my self service / my account using Edge or Chrome on Windows 10. Is anyone else getting the message using Chrome, Edge, Firefox, or any other browser?

Re: Here we go again

Glenn1 — Sun, 16 Feb 2020 15:52:37 GMT

Using Chrome here and no problems

Re: Here we go again

Dunkman — Sun, 16 Feb 2020 15:53:37 GMT

I am using Chrome Windows 10 and Safari and no warnings at this time.

Re: Here we go again

killerofmusic — Sun, 16 Feb 2020 15:54:59 GMT

Yeah i am getting the same error on my smartphone. However no safety warning on my computer. Maybe some problem with Java Script scripting on the website.

Re: Here we go again

john567 — Sun, 16 Feb 2020 15:57:47 GMT

I had checked yesterday, site SSL certificates for *.publicmobile.ca had expired Feb 7, 2020 and in some cases a self-signed cert was being presented. This is most likley the result of the Browser errors - Chrome/IE/FF dont accept these conditions without warning.

As of this morning 10h30 EST valid certificate are being presented for *.publicmobile.ca - at least from what I can tell.

Re: Here we go again

TheAlex — Sun, 16 Feb 2020 15:59:15 GMT

Hi!

Have you tried checking if your device's date is the current time? You could try other browsers or try using a different DNS (not sure about this).

Hope this helps!

Re: Here we go again

john567 — Sun, 16 Feb 2020 16:08:22 GMT

Site SSL certs were expired ( from what I can tell this happened - Feb 7, based on the old certificate ), and in some cases a self-signed cert was being presented. Chrome/IE/FF will throw warning when this happens.

as of 10:30 EST I believe the issue has been resolved.

Re: Here we go again

will13am — Sun, 16 Feb 2020 16:29:29 GMT

@TheAlex wrote:
Hi!

Have you tried checking if your device's date is the current time? You could try other browsers or try using a different DNS (not sure about this).

Hope this helps!

I am not sure what the problem is. I use cloudflare DNS. I am not really sure what the cause is and problem comes and goes. This SSL certificates here could be part of the problem.

Re: Here we go again

TheAlex — Sun, 16 Feb 2020 19:28:35 GMT

@will13am a écrit :
@TheAlex wrote:
Hi!

Have you tried checking if your device's date is the current time? You could try other browsers or try using a different DNS (not sure about this).

Hope this helps!

I am not sure what the problem is. I use cloudflare DNS. I am not really sure what the cause is and problem comes and goes. This SSL certificates here could be part of the problem.

Indeed! It could be that it is expired (even though the website is working fine for me) or you possibly changed the time on your device, which lead to the certificate being interpreted as expired.

Cheers!