Mike Witt

Something is very strange here. It looks like your browser doesn’t like the SSL Certificate on the SC site. Or is having some other problem with the SSL protocol. I’m seeing a valid certificate which is good until 19 Jan 2025. Can you trying viewing the certificate in your browser? (If you know how to do that.)

You might try a different device or different browser and see if you get the same result. Also, if you’re currently on a vlan, try from a non-vlan connection.

I’m only answering because SC is in the India time zone and you might not hear back from them right away. I don’t have any special knowledge about the SC site. Just what I can see from here.

Hi @patiohq,

I’m just a user like you, but I thought I would check that you’re going to:

https://supportcandy.net/

I’m able to get there and log in to my account. I’m in Vancouver BC for what it’s worth.

Hi @bigbear67,

I’ve never gotten a reply to my post here. I got those deprecated messages on a test site, when I tried running PHP 8.2. That site hadn’t updated to bbPress 2.6.11 yet, and I didn’t know if it was actually BP or bbP that was responsible for the deprecateds.

I haven’t had a chance to try this again since the new bbP came out.

What bbPress are you running? If it’s the current one then it might be worth posting on the bbPress forum to see if anybody there knows whether it’s coming from bbPress or not. It doesn’t appear that there’s going to be any answer here.

But I’d really like to know what you find out. Please either post back here or email me if you’d rather (email in my profile).

Mike

@nanosani, just in case nothing else turns up, what I have been doing is just opening up the tabs first and then opening the tickets I want in those tabs. Don’t know if that helps or not.

Could this maybe be fixed? I appear to be seeing normal connections to WF central now.

For what it’s worth, I’ve got sites on Siteground and Lightsail. So far I’m seeing the problem on Siteground but not Lightsail. Has anybody asked on Premium support?

Thanks @sterndata, I got it on Protonmail. So at least I know that the general problem has something to do with mxroute. Thanks for your help!

Hi @advanpix,

Sorry about the delay. As far as “testing” it, the warning is only going to happen once in a while. But the change in 3.8.8 looks equivalent to the patch I’ve been using for a long time. So AFAICT that’s good.

It’s nice to see wp-quicklatex getting updated. (Not that I’d want to see a lot of updates!) But nice to know that it’s still alive.

Cheers,

Mike

OK, @sterndata (or anybody), I changed to a protonmail address. If I could just get one more reply, then we’ll see if it comes to protonmail. That will help figure out if MXroute was in fact somehow filtering the notification emails.

I don’t really want to waste a lot of your time on this. If you don’t know of anything obvious I’m doing wrong, and it in fact there are not supposed to be any notifications in the admin bar, then the only other possibility is that (somehow) they’re getting filtered out by mxroute (or somebody). I’ll just have to look further into that.

Email is handled by MXroute. You need to look at the MX records:

mike@Acer2:~$ nslookup

set type=mx
num9.com
Server: 127.0.0.53
Address: 127.0.0.53#53

Non-authoritative answer:
num9.com mail exchanger = 10 taylor.mxrouting.net.
num9.com mail exchanger = 20 taylor-relay.mxrouting.net.

Hi @sterndata,

I’ve been all through that. They are not being filtered out by MXroute as far as I can determine.

Shouldn’t I also see a notification on the Admin Bar?

Thanks @wfpeter. That is quite interesting and explains a number of Cron messages I never understood before!

• This reply was modified 5 months ago by Mike Witt.

Hi @threadi, thanks for that Info. The result wasn’t very satisfying. I deactivated everything and then activated them one by one. And the warning never came back. So I guess something got “reset” in that process. I suppose unless it comes back again I’ll never know which plugin was causing it. If it does I’ll try deactivating them one by one next time. (Actually maybe that’s what you were suggesting.)

Anyway, unless you have any other suggestions. I’ll just mark this resolved.

@wfpeter,

I did a bit more testing. It looks to me like if two different admins log in, one after the other, they both get alerted every time. As if admin2 resets the cookie for admin1, then admin1 resets for admin2. Is that possible? Or am I confused somehow?

Is there any way to simply tell WF not to alert for logins from my primary home address?