weslleysim
Forum Replies Created
-
Forum: Plugins
In reply to: [Cloudflare] Blank Plugin Page (no options) in version 4.14.2The problem has been solved! I believe it was something related to the browser. Thank you very much!
Thank you so much for the support!
So is the issue resolved? Can I continue using the low-resource scan? I found 11 minutes to be a very satisfactory time, even for this scan mode.
And thank you very much for your help!
- This reply was modified 5 months ago by weslleysim.
Hi, how are you?
I followed all the recommendations you provided and adjusted the relevant settings in Wordfence, including enabling debug mode.
Regarding the max_execution_time, Hostinger does not provide direct access to the php.ini for modification. However, they offer a PHP settings panel where various values can be changed, including max_execution_time, which I updated there. One thing that confused me was that you mentioned the value 480, but in my panel the value was 300 (I had never changed it before). I have now set it to 60.
After completing all your recommendations, including applying the wildcard patterns and enabling debug mode, I ran a new scan in low-resource mode as you suggested. The scan completed successfully in approximately 11 minutes, as shown in the image below.
[Should I disable debugging now?]
I also monitored the I/O in Hostinger’s panel during the scan and observed no spikes, unlike before.
Here are the last 20 lines (or a few more) of the log you requested.
- [Jan 06 03:23:35] Obteve o valor de wf config maxExecutionTime: 15
- [Jan 06 03:23:35] getMaxExecutionTime() retornando valor de configuração: 15
- [Jan 06 03:23:35] Resultado em cache para teste de início de varredura: true
- [Jan 06 03:23:35] Iniciando o cron com ajax normal no URL https://simstime.net/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=1&scanMode=custom&cronKey=08a91a787cce2c6f9e80d802293af78c&signature=666b7572b74eb9301b5b8f37223ebb51ba13a3526ed46a863a4dbf4e8bd98f46
- [Jan 06 03:23:36] O mecanismo de varredura recebeu solicitação.
- [Jan 06 03:23:36] Verificando a assinatura da solicitação de início.
- [Jan 06 03:23:36] Coletando cronkey armazenada para comparação.
- [Jan 06 03:23:36] Verificando cronkey: 08a91a787cce2c6f9e80d802293af78c (esperando 08a91a787cce2c6f9e80d802293af78c)
- [Jan 06 03:23:36] Verificando cronkey salva em comparação com parâmetro de cronkey
- [Jan 06 03:23:36] Solicitando memória máxima
- [Jan 06 03:23:36] Configurando ambiente de manejo de erros
- [Jan 06 03:23:36] Configurando scanRunning e iniciando varredura
- [Jan 06 03:23:36] Obteve um valor desserializado verdadeiro de “wfsd_engine” com tipo: object
- [Jan 06 03:23:36] O processo de varredura terminou após a bifurcação.
- [Jan 06 03:23:43] Chamando API do Wordfence v2.27:https://noc1.wordfence.com/v2.27/?k=31796dff373cfc4d25acc85d26f4a6743771f2dcfb76dead76b08f536b207f9c267ff2c4bead0dc7dc4ed924501ed6f7ea719c4eed4f942926ab0389d1d683c8&s=eyJ3cCI6IjYuOSIsIndmIjoiOC4xLjQiLCJtcyI6ZmFsc2UsImgiOiJodHRwczpcL1wvc2ltc3RpbWUubmV0Iiwic3NsdiI6ODA3NDAzNTUyLCJwdiI6IjguMy4xOSIsInB0IjoibGl0ZXNwZWVkIiwiY3YiOiI3Ljc2LjEiLCJjcyI6Ik9wZW5TU0xcLzMuMi4yIiwic3YiOiJMaXRlU3BlZWQiLCJkdiI6IjExLjguMy1NYXJpYURCLWxvZyIsImxhbmciOiJwdF9CUiJ9&action=suspicious_admin_usernames
- [Jan 06 03:23:44] Examinando URLs encontrados nas opções que verificamos em busca de sites perigosos
- [Jan 06 03:23:44] Reunindo as chaves de hospedagem.
- [Jan 06 03:23:44] Usando o MySQLi diretamente.
- [Jan 06 03:23:44] Análise de URLs concluída
- [Jan 06 03:23:44] ——————-
- [Jan 06 03:23:44] O Wordfence usou 24.18 MB de memória para a varredura. O pico de uso de memória do servidor foi: 74.18 MB
- [Jan 06 03:23:44] Varredura concluída. Foram examinados 16945 arquivos, 26 plugins, 2 temas, 2305 posts, 995 comentários e 11276 URLs em 11 minutos 40 segundos.
- [Jan 06 03:23:44] Chamando API do Wordfence v2.27:https://noc1.wordfence.com/v2.27/?k=31796dff373cfc4d25acc85d26f4a6743771f2dcfb76dead76b08f536b207f9c267ff2c4bead0dc7dc4ed924501ed6f7ea719c4eed4f942926ab0389d1d683c8&s=eyJ3cCI6IjYuOSIsIndmIjoiOC4xLjQiLCJtcyI6ZmFsc2UsImgiOiJodHRwczpcL1wvc2ltc3RpbWUubmV0Iiwic3NsdiI6ODA3NDAzNTUyLCJwdiI6IjguMy4xOSIsInB0IjoibGl0ZXNwZWVkIiwiY3YiOiI3Ljc2LjEiLCJjcyI6Ik9wZW5TU0xcLzMuMi4yIiwic3YiOiJMaXRlU3BlZWQiLCJkdiI6IjExLjguMy1NYXJpYURCLWxvZyIsImxhbmciOiJwdF9CUiJ9&action=record_scan_metrics
- [Jan 06 03:26:59] Chamando API do Wordfence v2.27:https://noc1.wordfence.com/v2.27/?k=31796dff373cfc4d25acc85d26f4a6743771f2dcfb76dead76b08f536b207f9c267ff2c4bead0dc7dc4ed924501ed6f7ea719c4eed4f942926ab0389d1d683c8&s=eyJ3cCI6IjYuOSIsIndmIjoiOC4xLjQiLCJtcyI6ZmFsc2UsImgiOiJodHRwczpcL1wvc2ltc3RpbWUubmV0Iiwic3NsdiI6ODA3NDAzNTUyLCJwdiI6IjguMy4xOSIsInB0IjoibGl0ZXNwZWVkIiwiY3YiOiI3Ljc2LjEiLCJjcyI6Ik9wZW5TU0xcLzMuMi4yIiwic3YiOiJMaXRlU3BlZWQiLCJkdiI6IjExLjguMy1NYXJpYURCLWxvZyIsImxhbmciOiJwdF9CUiJ9&action=timestamp
- [Jan 06 03:27:11] Calling Wordfence API v2.27:https://noc1.wordfence.com/v2.27/?k=31796dff373cfc4d25acc85d26f4a6743771f2dcfb76dead76b08f536b207f9c267ff2c4bead0dc7dc4ed924501ed6f7ea719c4eed4f942926ab0389d1d683c8&s=eyJ3cCI6IjYuOSIsIndmIjoiOC4xLjQiLCJtcyI6ZmFsc2UsImgiOiJodHRwczpcL1wvc2ltc3RpbWUubmV0Iiwic3NsdiI6ODA3NDAzNTUyLCJwdiI6IjguMy4xOSIsInB0IjoibGl0ZXNwZWVkIiwiY3YiOiI3Ljc2LjEiLCJjcyI6Ik9wZW5TU0xcLzMuMi4yIiwic3YiOiJMaXRlU3BlZWQiLCJkdiI6IjExLjguMy1NYXJpYURCLWxvZyIsImxhbmciOiJwdF9CUiJ9&action=timestamp
- [Jan 06 03:31:40] Calling Wordfence API v2.27:https://noc1.wordfence.com/v2.27/?k=31796dff373cfc4d25acc85d26f4a6743771f2dcfb76dead76b08f536b207f9c267ff2c4bead0dc7dc4ed924501ed6f7ea719c4eed4f942926ab0389d1d683c8&s=eyJ3cCI6IjYuOSIsIndmIjoi
- This reply was modified 5 months ago by weslleysim.
Hey, I’ve just sent you the report as requested, using my username from here.
Just as a reminder, this Wordfence setup is the second or third installation, including table removal, as I was investigating the slow scan issue. It is currently running in learning mode until tomorrow.
Before the last low-resource scan — which took about 6 hours to complete — the only changes I made were the following:
- I manually set the scan time limit to 3600 seconds (10 hours), since I wasn’t sure how long the scan would take to finish.
- I set the maximum execution time for each scan stage to 30.
———
I’m not sure if this is relevant, but I’m sharing some I/O data from the past 30 days for reference.
As mentioned earlier, after deleting the “potential threat”, which later appeared to be a false positive, I ran a standard scan, which completed quickly and didn’t report any new issues. After that, I ran a more advanced Wordfence scan, which also finished in a reasonable amount of time and did not flag anything serious.
However, a few hours later, out of an abundance of caution, I ran a third scan. That’s when I noticed it was taking significantly longer than usual, and this behavior has persisted ever since. The scan speed only returned to normal temporarily after reinstalling the plugin with table removal, but shortly afterward, it slowed down again.
- This reply was modified 5 months ago by weslleysim.
Today I ran a scan on my site using the “low resource usage” mode and managed to complete it in about 6 hours. To make this possible, I had to extend the scan duration. I also adjusted another setting, setting its value to “30”.
I chose to test the low resource mode because I wasn’t sure how long the standard scan would take if I increased the allowed runtime, especially since the standard mode naturally consumes more server resources. In low resource mode, the scan was running at a speed of around 0.50 per file, whereas the standard scan usually runs slightly faster, typically around 0.80.
What I find confusing is how slow the scan has become overall. I have made very few changes to my site, which is hosted on Hostinger’s Cloud Startup plan. I’ve been using Wordfence for about five years, including two to three years as a premium user, and I’ve never experienced this kind of issue before, not even when I was on less powerful hosting.
I’m not sure, but apparently, what Wordfence found related to LiteSpeed was a potential false positive? (The issue of slow scanning remains).
Thank you very much for the information. Do you have any suggestions for schemas for me to use in tutorial posts?
Okay, I’ve done a lot of testing, and I can provide you with a wide variety of information:
1. When I make new posts on my website, and use the howto block, the “howto” schema is identified by Google Rich Result.
2. When I created copies of my original tutorial post, obviously with new dates, in this case today, the “howto” schema was identified in Google rich results.
3. When I edited other already published posts, and added the howto block, Google was able to identify the “howto” schema in those posts.
4. I edited my original tutorial post in multiple ways, and nothing makes Google rich results identify the “howto” schema.
5. I changed the link to my original tutorial post, and even with a new link, it did not identify the “howto” schema post.
6. Apparently, google rich results no longer displays the “howto” schema on the first page of the result, or has it always been like this, and I don’t remember? I say this because I was only able to find the “type” data referring to the “howto” schema when I clicked on “article” in the rich results, and then I viewed the “article” schema data, and within it I found the “howto” data ” schema.
The problem is that if I don’t use the “article” schema or any other (I haven’t tested it), the data from the “howto” schema will not appear anywhere in the result, so I thought: the howto schema is now conditioned to the article schema or others? – obviously, this question has to do with new posts, and has no relation to the post I’m having problems with and the howto schema doesn’t appear anyway.
I made new posts only with the “howto” schema, and the howto structured data did not appear in Google rich results. They only appeared if I added the schema article, then the howto data was inside the article in Google test results.
Here an image: https://i.imgur.com/NN6Zj5M.jpeg
7. Although my original tutorial post does not present the howto schema in Google tests, on validator.schema.org, the howto schema appears in the results. You can see it in the photo, or test it for yourself with the link in the post:
View post on imgur.com
The link to the post i’m always talk about and I can’t see the howto data in google rich results:
https://simstime.net/2020/06/15/como-colocar-metade-do-piso-no-the-sims-4/
8.
Finally, something curious.
Do you remember that I said that I made several new test posts, and in them the “howto” schema appeared, but inside “article”? So!
I tested the link to this test post on schema.org, and there, the result appeared different from my tutorial post also tested on shema.org. In it, only one schema box appears, in this case article, and inside it, there is the data from the article schema, and also the “howto” schema, all within the same box.
View post on imgur.com
View post on imgur.com
————————
I’m so confused! I don’t understand why the howto data doesn’t appear in my tutorial post in the google test, but it appears in schema.org, in separate boxes.
And I don’t understand why the howto data is appearing in other posts, but within the article.
Help me understand.
I have one last question, and I thought I would use this topic to talk about it.
What type of schema provided by Rank Math can I use on my website’s homepage? Since the homepage isn’t a specific article, I thought about what I could use. If I remove the schema manually from the homepage, all that remains in Google tests is “Organization” and “Sitelinks search box”
Thank you for all the information, you clarified everything I needed!
I was worried because I paid for filebird PRO version so I was scared. But as you said that a new version will be released that is compatible with previous versions of php, I will be waiting. Thank you!
I’ve just performed a test on a 7.3 php staging version of my web site, which is not on my servers, but on BlogVault’s servers (a backup and staging service), and the error persists in the stagging. When I upload the Filebird 5.1.2 file and having activated it, the above mentioned error occurs as well.
I created a new staging version of my site on the BlogVault servers, this time in php version 7.4, and in this version, Filebird 5.1.2 could be successfully activated without any errors.
Does this mean Filebird no longer works on php 7.3 versions?
Hey Arnan, does that mean we don’t have to worry? I got a message on wordfence scam talking about this vulnerability in ad-rotate plugin, came here and came across this post 🙂
It helped! Thank you for the informations!