April 14, 2019 at 6:42 am #6180April 15, 2019 at 5:18 am #6189
The plugin does not ever throw a 502 error, therefore it doesn’t look like your request is reaching the plugin.
You should check intermediate things, like your CDN, .htaccess file, check your access logs, etc.
Can you enable verbose debug output and check if the cron job starts? i.e.
1. Go to Wallets -> Cron job -> Verbose log output (debug) and enable the setting.
2. Check your WordPress debug log. When you trigger the cron link, it should write to the logs:
cron jobs STARTED
cron jobs FINISHED
Do you see the start and finish lines?
If you see only the start but not the finish, please let me know, because the cron jobs are crashing mid way for some reason.
If you do not see the start message, the problem is not with the plugin and you should try configuring your CDN, firewalls, etc.
Let me know please what you find.
with regardsMay 14, 2019 at 9:16 am #6306
dynamitemediaParticipantMay 15, 2019 at 7:53 am #6312
Error 502 means that the PHP service did not respond to your nginx, possibly because it was too busy. It’s way too general of an error to draw any meaningful conclusions. I would look around in the server logs for anything strange. Think access logs, nginx error logs, mysql error logs, etc.
Also, I would like to ask you the following:
1. Do you get the 502 error every time you follow the cron job link, or only some times?
2. Since you have enabled the WordPress debug log, do you see any other errors in the
3. Which coin adapter or adapters are you using? If you are using any RPC-API wallets, could it be that a connection is timing out due to some firewall?
4. Did you change anything around the time when this problem first occurred?
5. Go to the dashboard, and inspect all the debug info about cron jobs: Cron jobs last ran on, Cron jobs last runtime (sec), Cron jobs peak memory, Cron jobs memory delta. What do these read?
You must be logged in to reply to this topic.