animagic

Hi there,

I have not looked at the issue lately as I have been doing manual updates nearly daily anyways. After looking through my files, I still have no automated backups. I am guessing there is a cross-server issue. My SQL DB has its own server and is not on the same server as WordPress is so the WordPress server would have to FTP the backup file from the SQL server to the Web server which is where the issue lies.

Reopening the ticket.

This is a side-issue that possibly pertains to my conversion to https://.

I have 2 sites, 1 live and 1 dev. the dev site has been successfully flipped to https:// but in doing so, either I edited some code or the database in some fashion so that the Cookie Based Brute Force Protection does not correctly redirect attempts at /wp-login.php to my current redirect of https://127.0.0.1. It still provides the login page at /?mysecretword=1 thought which is odd. My live site is not https:// yet as we have not finished testing the theme, etc. on the dev site and the redirect works correctly there.

I have edited the htaccess file in the dev site to reflect the change to https in the Cookie BF section and it is identical to the live site’s htaccess in all other regards. I also don’t see any anomalies or differences in the database, thought I may be missing something.

Any thoughts?

Resolved

Just an update for anyone having HTTPS issues. I found that my issue was the Load Balancer that my server pair is behind. My host had not configured it properly to send the X-Forward-Proto header that a proxy requires. The LB is doing the SSL handling so it requires the header.

wp-config.php requires the following which is noted in the wiki page https://codex.www.ads-software.com/Administration_Over_SSL

define(‘FORCE_SSL_ADMIN’, true);
if ($_SERVER[‘HTTP_X_FORWARDED_PROTO’\ == ‘https’)
$_SERVER[‘HTTPS’]=’on’;

What is not noted is a working 301 Redirect for proxy to make the entire site https://. I used the following:

RewriteCond %{HTTP_HOST} ^my.example.com$ [NC]
RewriteCond %{HTTP:X-Forwarded-Proto} !https
RewriteCond %{HTTPS} off
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]

I found it was not an issue with the plugin. My pair of web servers are behind a Load Balancer that our host runs and the LB was not setup properly to send the X-Forwarded-Proto header. All is well now!

Update, I have fixed the issue with my CSS. Needed to place a parse_url( ,PHP_URL_PATH) around get_template_directory.

I still have an issue with wp-login.php being unaccessible though.

Still not having any luck. Reactivate and deactivate does not write to the cronjob.txt file. I’ve looked at the cronjob-handler.php file and related files and I don’t see any errors in my files either. I can’t speak for the previous developer before me but I don’t see any edits or changes to the files so they should all be base install .php files. Possibly uninstall and reinstall the plugin?

I have the backup interval set to every 1 Day, with Keep 30 and it is enabled. I have tried every 1 Hour, 2 Days and a few other intervals but nothing works. It also looks like the wp-security-log-cron-job.txt file is empty as if it’s never even fired before. This goes for all 4 locations of the file.

Web Server 1 – Development and Production directories (with singular installs of AIO Security, not a multi-site install)
Web Server 2 (redundant mirror) – Development and Production directories