By John Bongiovanni on Saturday, 22 November 2014
Posted in Technical Issues
Replies 8
Likes 0
Views 878
Votes 0
Reference this discussion:

http://stackideas.com/forums/email-notification-of-new-blogs-not-working

which is now locked. There were several issues, including EasyBlog parameter settings, which Nick kindly helped with.

At this point, the parameters are set correctly, the mail is being generated (thanks to Nick for showing me how to verify that), but the cron job is not working.

The cron job command is the following:
wget -O - -t 1 "http://cal-sailing.org/index.php?option=com_easyblog&task=cron";

When it runs, or when I run the command from a shell, I get the following error:

calsaili@serv01 [~/public_html]# wget -O - -t 1 "http://cal-sailing.org/index.php?option=com_easyblog&task=cron";;echo "Easyblog job completed $(date)"
--2014-11-21 18:59:08-- http://cal-sailing.org/index.php?option=com_easyblog&task=cron
Resolving cal-sailing.org... 181.224.137.103
Connecting to cal-sailing.org|181.224.137.103|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://www.cal-sailing.org/index.php?option=com_easyblog&task=cron [following]
--2014-11-21 18:59:08-- http://www.cal-sailing.org/index.php?option=com_easyblog&task=cron
Resolving http://www.cal-sailing.org... 104.28.14.4, 104.28.15.4
Connecting to http://www.cal-sailing.org|104.28.14.4|:80... connected.
HTTP request sent, awaiting response... 409 Conflict
2014-11-21 18:59:08 ERROR 409: Conflict.

I am able to enter the following in a browser, and it all works:
http://cal-sailing.org/index.php?option=com_easyblog&task=cron

I entered a ticket with my web hosting provider, and they told me that EasyBlog was returning the 409 error, and so I should contact you.

I turned .htaccess off to see if that was the problem, and I got the same error.

TIA.
Hello John,

I am really sorry for the delay of this reply as it is a weekend for us here. Can I know how did you access the ssh of the site? Can you provide us with the ssh access so that we can try to simulate the same errors?
·
Saturday, 22 November 2014 16:47
·
0 Likes
·
0 Votes
·
0 Comments
·
Wow, that was quick. I knew it was your weekend, and I wasn't expecting a reply until your Monday morning. I have added ssh access details.
·
Saturday, 22 November 2014 23:48
·
0 Likes
·
0 Votes
·
0 Comments
·
Wow, that was quick. I knew it was your weekend, and I wasn't expecting a reply until your Monday morning. I have added ssh access details.
·
Saturday, 22 November 2014 23:49
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello John,

I am really sorry for the delay of this reply as it is a weekend for us here. I have tested this and it looks like the reason that you are getting the 409 errors is because Cloudflare is restricting the access . This is the error message that I get when I tried to use "lynx" to access your site http://screen.stackideas.com/2014-11-23_1451.png
·
Sunday, 23 November 2014 14:52
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks for the quick reply (and on a weekend!). I turned off CloudFlare, and it solved the problem. I'm working with the hosting provider to get it configured correctly.
·
Monday, 24 November 2014 06:23
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello John,

Glad your issue has resolved.
·
Monday, 24 November 2014 10:06
·
0 Likes
·
0 Votes
·
0 Comments
·
You guys are truly awesome. Our website hosting service identified some DNS problems, and it's all working with CloudFlare. I never expected this kind of response on a weekend.
·
Tuesday, 25 November 2014 09:44
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello John,

Great! I assume your issue has solved then.
·
Tuesday, 25 November 2014 10:27
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post