KartHost

@salvatorenoschese For me it would be very helpful to know the following, besides just fails.

• What version of WordPress was this on
• What browsers did you try that had the problem of blocking Comments and Registration.
• What were your plugins settings and any other helpful info.

Funny I was reading this ticket a little after it was opened. And then our alarms went off 9 of our sites with the Shield Security Pro and The Event Calendar was knocking sites off. I ran over to The Events Calendar to let them know of this issue.

Looks like a roll back of ShieldSecurity until The Events Calendar releases an update.

• This reply was modified 1 year, 8 months ago by KartHost.

It seems to be working fine on WordPress 6.1.1. Of course, the original poster, didn’t give any useful information other than WP 6.1.1.

Installed on PHP 8.1.11

Web server nginx/1.22.0
Server architecture Linux 5.4.0-1087-gcp x86_64

PHP Memory as well as WP Memory 1024 MB

Hope this helps someone.

@s4shubhamverma I am about to try an Export, Import using this plugin.

Can you share what version of WordPress you are using and PHP version, please?

• This reply was modified 1 year, 10 months ago by KartHost.

It would be very helpful to the rest of the community when the OP makes claims something isn’t working correctly, they would at least reply to the Plugin Author who is making an attempt to help.

I have seen this before where the OP gives a 1-star rating for whatever reason says that they don’t have time to answer the Plugin Author questions, but they have time to post a bad review. Seems strange to me.

• This reply was modified 2 years, 7 months ago by KartHost. Reason: Clarity

@kpjjf Just curious, did you ever get BetterLinks Pro working on your sites?

@tomguk
This is in the Yith Subsccriptions here is a step by step
https://snipboard.io/STz0lD.jpg
let me know if that helps

hi @tomguk & @mikekmetz
it is in Yith Subscription > Subscrptions tab> on members that are now Suspended there is a place Yith Subscription > Subscrptions tab> on members that are now Suspended there is a Subscription Action drop down that allows you to try to pay the current renew order.

but when i tried it i still got the same error even after the beta update for Yith Subscriptions and the WooCommerce Stipe update last night.

How did you get yours to work or know it is working on the renewals?

Woocommerce just sent an update to Stripe extension of 5.6.1 I have installed it as well as the new version for Yith Subscriptions. Have gone to Yith subscriptions > to customer’s subscription > Actions > pay current renewal order
click and nothing is happening. Am I in the correct place to request the subscription payment again for all that have been failing since 10/1. Working on this with a client any help would be very much appreciated.

About the only big thing it needs now is “Fall Back” for SMTP service.

Meaning, for what ever reason your primary connection isn’t working maybe for just a few moments, the plugin will automatically try your fall back service.

Our experience using another outstanding SMTP plugin this has come in handy more than once, the primary SMTP couldn’t send, and the SMTP plugin instantly reverted to other Fall Back and the email was sent. I would highly recommend this on ANY eCommerce site or any site where your site is dependent heavily on sending emails.

I would recommend this WordPress plugin WP-Optimize – Clean, Compress, Cache.
I have used it to clean up leftover tables from a few different plugins I have removed from sites, does a good job.

• This reply was modified 3 years, 8 months ago by KartHost.

UPDATE – Please be advised as Paul mentioned, that the Shield Security version 10.2.2 is the fix to this problem. 10.2.2 is what you will want to be using at this time.

We have upgraded multiple sites with it, and all working fine on our end.
Sorry for any confusion I may have added.

• This reply was modified 3 years, 9 months ago by KartHost.

3rd Follow Up

OK, deleted Post SMTP (which worked fine with both Mailgun SMTP, and Mailgun API).
Then loaded FluentSMTP back and I did discover a mistake (since the plugin remembered my settings when I loaded it back) I used PORT 486, that is wrong, it should be PORT 465, but regardless 465 isn’t available on this server.
So changed to 587 and changed to TLS from SSL (although Mailgun says 25, 465 and 587 use SSL and TLS). Saved settings went back to test.

This time the Test email using Mailgun SMTP Worked without issue. Yeah!

Now going back to test Mailgun API again.
CORRECTION ON MY PART – When I first set up FluentSMTP I the API Key I obtained was from SENDING > Domain Settings > Sending API Keys > Add sending key
That didn’t work in FluentSMTP but DID work in Post SMTP.

So, I reviewed the FluentSMTP docs (its a guy thing right? Do not read instructions) and instead I am needing to use the PRIVATE Key obtained at Settings > API Keys and selecting the Private API Key. When I did that, and sent a Test Email sent successfully.

Not sure of the differnce of the two keys, but it does make a difference.

So, all working.

SUGGESTION – It would be REALLY NICE to add to FluentSMTP a pretest of all standard ports, 25, 465 and 587 to confirm which ones are OPEN (on the respective server), that is a very nice tool on Post SMTP and saves a lot of headache in setting up.

Hope all this helps someone.

• This reply was modified 3 years, 10 months ago by KartHost.

OK, I have done a little more testing.
I went back and set up SMTP to our Mailgun account to see if we could get things working. And didn’t work. Just got an error and a link to docs to trouble shot the error.

So I removed FluentSMTP and loaded up the old true and reliable ‘Post SMTP’ plugin to see if I got the same issues.

When I when through ‘Post SMTP’ set up wizard, I told ‘Post SMTP’ I was going to use regular ole’ SMTP connection. And I provided the Mailgun SMTP Server name smtp.mailgun.org. It ran the tests and listed ALL available PORTs to use to connect Mailgun. And only Port 25 and 587 was available. I used Port 465 when I set up FluentSMTP. And received the error and not any other reason or possible solution.

So continuing setting up SMTP to Mailgun using SMTP. And sent a Test email, the test email went through without issue. So much for my .htaccess theory being the problem.

Now I proved I can send, and confirmed which send ports are available.

Now I set up Post SMTP to connect with Mailgun API. After set up, I sent a test email in Post SMTP without issue.

I have NO idea now as to why FluentSMTP would not connect up to Mailgun using the API.
Cool thing with Post SMTP, it does have a Diagnostic Test, not going to help with FluentSMTP, but it does provide very good information when needing to troubleshoot. FluentSMTP should consider same or similar.

Another item Post SMTP has, valuable tool, is the Outgoing Mail server Hostname, Connectivity Test. I can place in the Mailgun API address or SMTP port info and provide connectivity report.
It provides for current Status and Service Available. And it is saying connection is available and open for Mailgun API connection and Ports 25 and 587 for SMTP.

I will remove Post SMTP reload FluentSMTP and see what happens since now I know port 465 is closed on this server.

@pesquerra it would be really simple to find out who was sending the spam, instead of “assuming” something happened. I doubt very seriously Ben and his team at Kadence WP would do something like this. This would be disastrous for their business.

All you had to do is simply obtain the ORIGINAL email that you suspect was sent as spam and obtain the forensic of that email called the email properties (header) and that will show the TRUE sender.

Just my opinion, but providing a 1-Star Rating for what seems like a 4 to 5-star product based on an assumption just isn’t right. A STRONG accusation like that needs proof and the email header can provide it. Otherwise, it’s just your word against the community.