jsnowbusiness

I figured it out – it was my .htaccess from BulletProof Security blocking wget from my home-server from hitting the wp-cron of my webhost!

(My crap webhost doesn’t provide Cron, so I use Task Scheduler and wget on my Windows home-server to hit wp-cron.. mehh.. it works..)

I didn’t open a new thread since I got it figured out, figured I’d leave a note here though.

Dang, I seem to be having this same issue now – but I’m already hitting my wp-cron (hosted on a web-host) from my home-server every 10 minutes.

Current server time: Wednesday, February 11, 2015 @ 6:57 PM
Next backup scheduled for: Tuesday, February 10, 2015 @ 3:00 AM

Other plugins I am using that rely on wp-cron are all working fine, so I’m hoping that just disabling and enabling schedule as suggested will fix my issue..

Done – Now I’m off to check out your other plugins… Because if they are made like CYAN backup, and could be of use to me, then I will definitely start using them and switch from any other plugins I’m using. ?? Thanks again.

Thanks by the way – I love your plugin, especially now that I got remote storage working!

Oh, well I just changed my sftp server to 22 and it worked fine with just by dynamic-ip subdomain name, I’m not sure why it was on 2121 in the first place so 22 it is!

Thanks for the info – I think I tried adding :2121 before… but it didn’t work… but when i was just changing port in my router’s port-forwarding I noticed I had it set to 2122, not 2121.. Woops! I guess it would have worked if I didn’t goof the port number up in router. hehe

Crap… so a sftp port using a non-default port other than 22 won’t work without editing the plugin..

Guess I need to see about getting my sftp server onto port 22, it’s on 2121 currently..

Thanks for the reply!

I get what you mean, and I have had that issue in the past with SNAP in conjunction with WPeMatico/autoblogging, but that’s not the case here.

In the example I posted last, it is a post that I manually created, wrote, edited, and published. Nothing automated at all – that’s why I’m confused as to why it’s not working. ??

But it’s not empty! For Example:

https://www.evonyhookups.info/?p=8586

re-posted to tumblr as:

https://tmblr.co/ZXIC0t1X3FIO9

It has the content of my T&C page found at https://www.evonyhookups.info/?p=1127 – Any ideas?

-John

I just had one of my sites bought down, and I noticed the offending IPs were doing alot of POSTs to non-existant subdomains on my site, such as “dubyadubyadubya.site.com” and “nipple.site.com” and “xxx.site.com”, and many other adult/lude words along with the base64 functions.php injections they were up to.

It’s cache poisoning, it can not only open up security vulnerabilities, but also hurt your SEO since these people can make cached subdomain versions of your site for stop words and adult content, not to mention it’s duplicate content across two different subdomains which Google definitely doesn’t like.

I suggest you do the cname/arecord fix so this doesn’t happen to you.

-John

https://pastebin.com/dZZj0Shi That’s what I had in my old post-content.php and it worked fine, no errors… now I can’t put it anywhere in the new post-content.php without my site breaking.. ??

Not sure what you mean by “not ready”, the post was published over a week ago… nor am I sure how OG is going to fix it. Care to elaborate?

Yep – Thanks.

After reading this post, designating the location of a cacert.pem file in my IIS based server’s php.ini file (such as: curl.cainfo =”C:\cacert.pem”) solved the issue for me.

I tried the edit and it just made my site give 500 Internal Server Errors, so on to isolating the plugin on Twenty Thirteen.

Yes it IS the pro plugin version now that I’m looking at it (the site isn’t actually mine, just doing work on it) – and no I do NOT have debug enabled in my config, that’s why this is a problem.

If I deactivate the membership plugin, going to my site with or without www. both resolve properly. With the plugin activated, if I go to my page without www. then I get this error on an otherwise blank page.

I will try the edit and see what happens. I will also try the plugin alone and with Twenty Thirteen to see if it resolves the issue. If need be, I will ask the site owner for credentials needed for Membership Premium support.

Thanks!

Linkedin SNAP Captcha Error Screenshot