david

UPDATE. I had a problem with wordpress 6.3 yesterday afternoon and just redid the settings of this plugin and now everything WORKS!!!! I regret any confusion. This is a super plugin.

Thank you. I was overthinking. It’s now working beautifully. Very nice. I appreciate the prompt response.

A BIG thanks. That would indicate that I resolved my problem when I removed posts and the ability to comment, having nothing to do with the security of SSL. Have you posted this to the support forum? This is good to know.

Just a followup: I did get authority and set SSL to HTTPS and the security problem disappeared. Thanks for that tip. All is working well. Thanks for your help.

Thanks for the feedback. I plan to do that as soon as I get access to the server. That may be a week or more. If I should reopen at that time, please mark it closed for now. Otherwise, I’ll update as soon as I have https set.

Yes, all up to date. There were six attempts in the past hour.

I do not have access to server, but I use Wordfence for security and it displayed these failed logins from today:

test1 165.22.211.2048 hours 46 minutes ago

12345678 206.189.139.1789 hours 16 minutes ago

12345678 162.255.118.2059 hours 16 minutes ago

vrzwk 143.110.149.6111 hours 6 minutes ago

tester 89.46.106.17711 hours 46 minutes ago

laszzy 68.178.225.22412 hours 19 minutes ago

laszzy 44.203.51.24312 hours 49 minutes ago

sinpetra 85.158.200.10712 hours 49 minutes ago

sinpetra 202.191.60.14513 hours 31 minutes ago

wwwadm 8.134.90.22414 hours 44 minutes ago

All I can say is that attempted logins continued after installing the plugin. I’m puzzled that the attempts continue.

UPDATE: I was using the wrong widget. My error.

Thanks for writing back. It took almost a week, but yesterday afternoon, Wordfence removed its warning message. But thanks for the tip on how to confirm this in the future. Much appreciated.
david

A BIG thanks to you. Worked fine. I’ve been struggling with this for months and months. cron stuff is greek to me, and I am very appreciative. I posted here because it was affecting Wordfence and I felt you would have a good suggestion – which you did. Thanks again.
david

Steven, You were right. I contacted developer and issue resolved from theme.

Thanks for reply, Steven. Your CSS code removed my anxiety (MUCH appreciated), but I agree it would be better to clean it up. I followed your suggestion and wrote to developer, but my memory is that this was never there until I installed Jetpack. I’m sure I will learn from this experience.
david

WOW! That was easy! Thank you, thank you. I was imagining a lot of work, but that did it. Much appreciated.
david

First, start your own separate thread.
Second, explain more detail on the website’s complete URL
Third, explain or show the exact error you are seeing.
Fourth, use the right forum. It is NOT this one.