SOLVED Working app shows "not responding" in dashboard

[Dreamcatch22]

A unmanaged wordpress app shows "not responding" in the dashboard but it is live and working.

Tried resetting it as well as restoring it from a backup but nothing changes. I also do not see any errors in the log. It is a minor error but it is annoying.

Any suggestions?

[girish]

@Dreamcatch22 Cloudron tries to query https://site.com/wp-includes/version.php to check if the app is "responding". I guess you have some plugin installed which blocks that?

[Dreamcatch22]

Hey @girish thanks for replying. I will see if disabling the security plugin will do anything.

The interesting part is that all of my unmanaged wordpress apps are pretty much configured the same. The other ones are working fine and show no error on the dashboard. Just this one random one.

[girish]

@dreamcatch22 In the app logs, you will see the response of the healthcheck. Can you paste like say the last 10-20 lines of the logs here? It will say something like Nov 10 16:16:00 172.18.0.1 - - [11/Nov/2020:00:16:00 +0000] "GET / HTTP/1.1" 200 14554 "-" "Mozilla (CloudronHealth)"

[Dreamcatch22]

@girish Does this help?

[11/Nov/2020:00:34:00 +0000] "GET /wp-includes/version.php HTTP/1.1" 403 289 "-" "Mozilla (CloudronHealth)"

[girish]

@dreamcatch22 Indeed, that's the problem. Some plugin is making WP respond with 403. I think in Cloudron 6 I will just make the change in our health checker to check for any response and not just 2xx code. So maybe you can just ignore it for now and the problem will resolve itself in the next release.

[Dreamcatch22]

@girish Understood. Thanks for taking the time to help me out.

[Lonk]

@girish said in Working app shows "not responding" in dashboard:

@dreamcatch22 Indeed, that's the problem. Some plugin is making WP respond with 403. I think in Cloudron 6 I will just make the change in our health checker to check for any response and not just 2xx code. So maybe you can just ignore it for now and the problem will resolve itself in the next release.

I like that idea, but a blacklist should be used. And def make sure 503 bad gateway stays in the unhealthy category.

[girish]

Right, for the moment it accepts everything till 403