s2Member not behaving in the way it suppose to

Yes, totally. I have it set up but it does not work well because I use cloudflare and the loopback is broken due to security certificate issues (I don’t buy one but use cloudflare’s free one instead, a workaround is using your VPS’s hosts file to make it use cloudflare ip to reach your domain, silly, I know… alternatively you can use the -k flag on your curl inside your crontab file).

This is what I have on my crontab:

# Edit this file to introduce tasks to be run by cron.
# Each task to run has to be defined through a single line
# indicating with different fields when the task will be run
# and what command to run for the task
# To define the time you can provide concrete values for
# minute (m), hour (h), day of month (dom), month (mon),
# and day of week (dow) or use '*' in these fields (for 'any').#
# Notice that tasks will be started based on the cron's system
# daemon's notion of time and timezones.
# Output of the crontab jobs (including errors) is sent through
# email to the user the crontab file belongs to (unless redirected).
# For example, you can run a backup of all your user accounts
# at 5 a.m every week with:
# 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/
# For more information see the manual pages of crontab(5) and cron(8)
# min hour dayofmonth month dayofweek  command
*/10 * * * * curl -s -k https://domain.tld/?s2member_auto_eot_system_via_cron=1 >/dev/null 2>&1
30 * * * * curl -s -k https://domain.tld/wp-cron.php >/dev/null 2>&1

Replace “domain.tld” with your own domain :wink: