WPIntell

Source evidence

504 error

Missed Scheduled Posts Publisher by WPBeginner · support · 2021-08-25T08:31:00+00:00

Missed Scheduled Posts Publisher by WPBeginner plugin evidence original source source API
mixedsentiment
mediumseverity
0.85relevance
5replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

7 / 35 rows with source links

20.0% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

28 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
bpathania resolved
The URL that is being hit on those 504s is also all /wp-admin/admin-ajax.php?action=wpb_missed_scheduled_posts_publisher could you please help me on this as I have activated this plugin for network site and it’s throwing lots of 504 errors again, which is burning up the overall server. Is it possible to resolve this This topic was modified 4 years, 9 months ago by bpathania . this was not working fine with lastest version of WordPress, could you please make is compatible with latest verison This reply was modified 4 years, 9 months ago by bpathania . Hi @bpathania , I’ll test this on a multisite install. Are you using a sub-directory or a sub-domain configuration? A 504 HTTP header usually indicates a proxy server is timing out but I’ll get back to you to ensure the web server isn’t the underlying cause of the issue. Thanks for your response. In multisite we are using sub-domains. I tested this with a multisite install using the latest version of WP and was unable to reproduce the error, I’m afraid. I ended up testing both sub-domain and sub-directory configurations and both tests were successfully running the AJAX request and returning 200 HTTP response codes. It might be worth checking with your hosting provider to see if any configuration changes have been made recently. A 504 header usually indicates an error between the php server and the client. Yes, We have also tested it in various other ways like, downgrading the WordPress version and update the plugins. But it looks like the issue with the hosting configurations will check it with the provider. Thank you for your quick response.

Comments

5 shown
bpathania 2021-09-01T12:39:00+00:00

this was not working fine with lastest version of WordPress, could you please make is compatible with latest verison This reply was modified 4 years, 9 months ago by bpathania .

Peter Wilson 2021-10-12T23:35:00+00:00

Hi @bpathania , I’ll test this on a multisite install. Are you using a sub-directory or a sub-domain configuration? A 504 HTTP header usually indicates a proxy server is timing out but I’ll get back to you to ensure the web server isn’t the underlying cause of the issue.

bpathania 2021-10-13T04:41:00+00:00

Thanks for your response. In multisite we are using sub-domains.

Peter Wilson 2021-10-15T02:19:00+00:00

I tested this with a multisite install using the latest version of WP and was unable to reproduce the error, I’m afraid. I ended up testing both sub-domain and sub-directory configurations and both tests were successfully running the AJAX request and returning 200 HTTP response codes. It might be worth checking with your hosting provider to see if any configuration changes have been made recently. A 504 header usually indicates an error between the php server and the client.

bpathania 2021-10-15T03:34:00+00:00

Yes, We have also tested it in various other ways like, downgrading the WordPress version and update the plugins. But it looks like the issue with the hosting configurations will check it with the provider. Thank you for your quick response.