jarnovos

Hi @hans410947,

That’s great to hear, thank you for the update. I’m glad that the solution turned out to be this simple after all ??

Kind regards, Jarno

Hi @cke11y,

Please note that this message is not specifically from this plugin, but it concerns the error/status which is being reported by Let’s Encrypt during the generation of your SSL certificate.

Unfortunately, there’s not much I can do to affect the behavior of the Let’s Encrypt certificate generation on your site.

All I can really do is suggest to “Refresh” once more, to check if that allows the generation to proceed; or “Reset Let’s Encrypt” and go through the process again.

Kind regards, Jarno

Hi @cke11y,

You will see in your video that the Wizard mentions that you should wait for “X” amount of time before re-checking, because your new DNS record hasn’t fully propagated yet. That’s why it fails at the moment, since it can’t find your new record yet.

The main thing seems to be that you’ve added the DNS record correctly, however, the record has a TTL value of 14400 which equates to 4 hours. I’d use a TTL value such as 300 (5 minutes) for this record, so you don’t have to wait for 4 hours.

I’d threfeore recommend to Reset the Let’s Encrypt Wizard to start with a clean slate. Go through the process again, and when you’ve reached the DNS Verification step it should present you with a new TXT record. Add it to the DNS section in cPanel with a shorter TTL (e.g., 300), and make sure to actually wait for these 5-10 minutes before trying to proceed.

In addition; because you’ve tried too many times in a short time period by now, you are now rate limited by Let’s Encrypt (we don’t have any influence over this). You’ll have to allow some time before trying to generate a certificate again.

Kind regards, Jarno

Hi @hans410947,

I see, there’s at least an error being reported which is almost certainly related to the issue; though it is unfortunately not very descriptive on it’s own.

The first steps I would recommend trying, to rule out some things as being potentially related:

1) Try opening the Security -> Settings page in an Incognito/Private Browsing window in your browser, to rule out any browser extensions (e.g., ad-blockers) as being related

2) If the above didn’t help yet, navigate to the Dashboard of the plugin and then open the browser’s Developer Tools once more; but this time, navigate to the “Network” tab instead. With this section open, navigate to the Settings page in the plugin again (you might have to refresh the page once).

This should display all of the resources that are being loaded, and I would expect that there are certain REST API requests from the plugin which are failing in your case. These should be indicated in red. Could you click one of those requests and check the “Response” tab, to see if they might be getting blocked?

Kind regards, Jarno

• This reply was modified 4 months, 1 week ago by jarnovos.

Hi @hans410947,

The “Settings” panel is also available in the Free plugin. If it doesn’t load correctly, there might be an issue such as REST API requests from the plugin being blocked on your server (or failing for some other reason); and it can’t load properly as a result anymore.

Could you navigate to the “Settings” page once more, then open the Developer Tools of your browser (CTRL + Shift + C in Google Chrome) and click the “Console” tab here?

Please attach a screenshot of any errors you see being logged in the “Console” tab. You can upload the screenshot on a service like https://snipboard.io/ and share the link here.

Kind regards, Jarno

Hi @zsoca,

Glad to hear that you’ve already been able to solve this, I was just about to write a response when I noticed your follow-up message come through.

If you have any further questions about the plugin, let me know as well.

Kind regards, Jarno

Hi @tatyanaviktorovna,

Glad to hear that the problem is fixed, thank you for your quick replies & confirmation as well.

Kind regards, Jarno

Hi @tatyanaviktorovna,

Great, that confirms that the behavior was unrelated to this plugin!

You can therefore re-enable the plugin on your site, and as long as you leave the setting “Disable the built-in file editors” disabled under Security -> Settings -> Hardening -> Basic, the issue will not return anymore.

Kind regards, Jarno

Hi @tatyanaviktorovna,

Please see what I mentioned in my first message:

“Some themes, such as the default Twenty Twenty-Four theme from WordPress, will also deactivate these editors. And if they are hidden by another theme/plugin on your site, the setting in this plugin won’t affect that.

Seeing as you don’t have this plugin enabled anymore, but these fields are still hidden; this is caused by something else, outside of this plugin. I expect it occurs due to the default theme that your site uses (as the Twenty-Twenty themes are known to do this as well), so you can switch to a different theme to see if that’s the case.

Kind regards, Jarno

• This reply was modified 4 months, 2 weeks ago by jarnovos.

Hi @tatyanaviktorovna,

If this issue persists even after deleting or disabling this plugin, then it is caused by something other than this plugin; because after the plugin has been deleted or disabled, it will not be able to affect your site anymore either.

Kind regards, Jarno

Hi @tatyanaviktorovna,

This plugin will only disable the “Plugin and Theme Editor” fields when the setting “Disable the built-in file editors” under Security -> Settings -> Hardening -> Basic mentioned above has been enabled. But it doesn’t “move” these fields to a different tab when this setting is enabled, it just disables them.

But when this setting is not enabled in the plugin; it will also not disable or otherwise change anything about the Plugin or Theme Editor options anymore.

Kind regards, Jarno

Hi @tatyanaviktorovna,

If the file/theme editors are disabled by this plugin, you can de-activate the setting “Disable the built-in file editors” under Security -> Settings -> Hardening -> Basic to re-enable these options on your site.

But please note that some themes, such as the Twenty Twenty-Four theme, will also deactivate these editors. And if they are hidden by another theme/plugin on your site, the setting in this plugin won’t affect that.

Kind regards, Jarno

Hi @mohammedays,

It looks like these 404 errors are being triggered by automated scanning tools/bots. They are attempting to scan your site for vulnerable parts to exploit, and searching for configuration files that might contain sensitive data (as evidenced by the request to /.env).

To further illustrate the potentially malicious nature of these requests: the request to /?author=1 is an attempt to enumerate the username of a WordPress Account on your site by trying author IDs (ID 1 is typically the Administrator). Requests such as /admin.php, /simple.php are attempts to find admin interfaces on your site.

This is why your monitoring plugin reports “404 Not Found” errors on those pages, as these bots are requesting pages that do not exist on your site; thereby triggering various 404’s in the process.

You can consider using a security plugin for WordPress to detect such malicious traffic, and block them from accessing your site.

I hope this helps to clarify the behavior you’re experiencing.
Kind regards, Jarno

• This reply was modified 4 months, 3 weeks ago by jarnovos.

Hi @cascinacomina,

Could the issue be that you have correctly added your Google Tag Manager snippet to the site; but that you haven’t created the Google Ads Conversion tag in your Tag Manager container yet?

Or perhaps you did create the Google Ads Conversion tag in Tag Manager, but haven’t published the container yet, so the tag does not fire as a result?

Kind regards, Jarno

Hi @mossifer,

That’s strange, can’t say we’ve had other reports about such behavior yet; so I would be interested to know what this might be related to.

Does the decreased performance occur on both the front & back-end, or is it isolated to just the back-end for example?

As we currently don’t have much to work with; any additional information about the issue e.g., whether there are any related errors being logged in the browser console, or in your PHP error logs, would help us determine what this might be related to.

Kind regards, Jarno