sarawildflower

The contact form uses Fluent Forms if that helps.

Thanks, The plugin updated automatically in WordPress to 6.38.

I have now disabled automatic updates for it, was planning to stay on 6.37 until next version released.

I did not get a response or find a solution to this, I had to disable the Wordfence 2FA and use another plugin: WP 2FA which seems to work. Then I had to hide all references to Wordfence 2FA so my admins didn’t get confused about which one to use.

Hello @wfmargaret , is there any response to this. It is for a website that was hacked (hackers disabled Wordfence) so it’s an important thing for it to work. Losing confidence in WF.

Hosting support confirms the NTP is fine. Though I still see it’s failing I don’t know if that would be the reason for the 2FA failing.

I have sent another diagnostic report as debug is on, so it might give you more insight?

Might it be to do with the NTP, here is the message on the dashboard:

• NTP
• NTP is a protocol that allows for remote time synchronization. Wordfence Login Security uses this protocol to ensure that it has the most accurate time which is necessary for TOTP-based two-factor authentication.NTP is currently?enabled.NTP updates are currently failing.?NTP will be automatically disabled after 2 more attempts.

How can I resolve this please?

This is still not working. Today I have tried:

• Disabled all plugins
• Changed Theme to 2024
• Purged all caches
• re-set up 2FA

When I activate Wordfence again, the 2FA continues to give me the same message when I try to log in: “CODE INVALID: The 2FA code provided is either expired or invalid. Please try again”

Thank you, I have just sent the diagnostic report.

Hello, I’m using the default WordPress login.

The solution of password+code doesn’t work either, I just get “ERROR: The username or password you entered is incorrect”

Any other suggestions please?

Updated to 6.2.2 and error appears to be resolved, thanks.

Hello, having a similar error:

Errors:
2021-07-12 12:45:39: Error occurred while checking account status. Error: CONNECTION_ERROR : “cURL error 28: Operation timed out after 10001 milliseconds with 0 out of 0 bytes received”
2021-07-12 12:45:39: Error occurred while API key validating. Error: Testing is failed. Please check the Access key.

Access key is definitely correct, I have several other websites set up with Cleantalk on exactly the same hosting and servers?

Thanks

https://share.getcloudapp.com/7KupgqK8
https://share.getcloudapp.com/12uoq0wN
https://share.getcloudapp.com/OAugE4kE

Thanks for that, so I did speak to the theme support (Codex The Gem FYI) and they couldn’t replicate the issue.

However, I think I solved it – I had “Prevent Cross Site Tracking” set in Safari and Chrome. Only found out because I went to debug my phone browsers. When I set the phone settings to allow cross site tracking in order to debug, it now works. I see that this can be an issue with connecting to third party systems – might be worth you guys noting down if you get similar queries coming in!

I also checked and the same behaviour was happening on Safari desktop until I went into preferences and disabled the “Prevent cross site tracking”

A quick browse shows it might be an issue with the cookies set by Stripe being samesite/cross site – is this something able/likely to be rectified? onsite Transactions are a standard process that aren’t necessarily something that should be lumped in with anti-tracking abilities? It’s a challenge for non-techy folks who wish to make a purchase.

Thanks

Hey Slickremix any update on this? I’ve got several clients using your premium plugin, will have to change if not available in next day or so.

Thanks @mibuthu, I have removed that and it now works.

Also just wanted to say the responses from @massimod were fairly impolite. I’m not sure if they are providing an official response from the Event List support team, but it’s not creating a great customer experience. SHOUTING at a user who has asked for support is never necessary.

• This reply was modified 7 years, 1 month ago by sarawildflower.

Yes it is a plugin conflict, the Event List plugin is causing the issue. When I disable it the page renders fine.

This is the shortcode I’m using on that page, it was working until the update: [event-list num_events=all show_cat=true show_filterbar=true filterbar_items=months_dropdown(show_all=false|show_upcoming=true),cats_dropdown;;reset_link collapse_details=true link_to_event=false date_filter=upcoming]

As I said, Event list is working fine on other pages when it’s activated. But on this page it causes the fatal error. Any ideas why?