SecGen

Same issue here, latest plugin and WP. Also tried reverting to 3.2.3, but still get errors:

“The HTTP response test get an error “SSL connect error”Not expected HTTP response body:”

(note it doesn’t actually show any output from the HTTP response)

I also have CloudFlare SSL.

Any idea when we can expect a fix for this?

I expect the API functionality for glacier will be near-identical to S3. Should be fairly easy for Daniel.

Still having this error despite having updated to the latest version of the plugin. Has anyone found a solution? The plugin was working fine before.

I second this!

That said, I’m still unable to actually use BackWPup due to ongoing errors…

I agree with klynam. BackWPup was working fine on my server for the past year, and only recently have I been having errors outlined in this post (with still no reply): https://www.ads-software.com/support/topic/backwpup-database-errors?replies=1

I don’t see how it can suddenly be a server limit problem…

It just happened again…

WordPress had its stuff at the bottom, and now its gone and written it AGAIN at the top, overwriting a bunch of my lines in the process:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILEAddOutputFilterByType DEFLATE text/css
AddOutputFilt# END WordPress
 text/x-js
AddOutputFilterByType DEFLATE application/xml
AddOutputFilterByType DEFLATE application/xhtml+xml
AddOutputFilterByType DEFLATE application/rss+xml
AddOutputFilterByType DEFLATE application/javascript
AddOutputFilterByType DEFLATE application/x-javascript
AddOutputFilterByType DEFLATE application/x-httpd-php
AddOutputFilterByType DEFLATE application/x-httpd-fastphp
AddOutputFilterByType DEFLATE image/svg+xml
</IfModule>

# Add WWW to URL
<IfModule mod_rewrite.c>
RewriteEngine on

RewriteCond %{SERVER_PORT} ^80$
RewriteCond %{http_host} ^domain.com [nc]
RewriteRule .? https://www.domain.com%{REQUEST_URI} [R=301,L]

RewriteCond %{SERVER_PORT} ^443$
RewriteCond %{http_host} ^domain.com [nc]
RewriteRule .? https://www.domain.com%{REQUEST_URI} [R=301,L]
</IfModule>

# Options
Options -Indexes
Options +FollowSymlinks

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

WTF.

Hi Phil,

Thanks for the prompt reply. My custom directives are indeed outside the WordPress BEGIN and END tags. It also doesn’t seem to make a difference if I put mine above or below.

I’ve just recreated a .htaccess from scratch, and WordPress re-added its stuff at the end of the file. I’ll keep an eye on it to see if it changes again.

Same here…

Hi xxdesmus,

Thanks. I’m already running this plugin. While the plugin correctly uses the CF-Connecting-IP header, I think that nginx changes this to HTTP_CF_CONNECTING_IP, so the CF plugin doesn’t pick it up?

I may be wrong though. All I know is that it didn’t work for me after I installed nginx, and had to use the solution above.

This was fixed by adding the following to wp-config.php:

if ( ! empty( $_SERVER[‘HTTP_CF_CONNECTING_IP’] ) && preg_match( ‘/^\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3}$/’, $_SERVER[‘HTTP_CF_CONNECTING_IP’] ) )
$_SERVER[‘REMOTE_ADDR’] = $_SERVER[‘HTTP_CF_CONNECTING_IP’];

Great thanks ??

Hi Matt,

Thanks, the sub-plugin fix worked.

I understand that there are many other plugins that can break Shadowbox, particularly all of the various gallery or image-handling plugins. WP-Minify doesn’t do any of these, however, as it merely tries to consolidate JS (and CSS) into a single file for efficiency. I don’t know why this would break Shadowbox, but I can’t imagine it would be terribly hard to fix. All of my other JS-based plugins work fine with it.

If you do get a chance to look into it, it’d be appreciated. I’m happy to turn WP-Minify back on on my site if you need.

Thanks again for all your efforts, your plugin is the best lightbox-style available.

Your latest update appears to fix the problem for me.

Everyone else?

Hi Matt,

Thanks for your reply. I admit my post was unhelpful as I didn’t have the time to give full details of my issue at the time. What I will try to do is provide the full HTML of the post, and the full HTML of the rendered page with a screenshot.

I can’t keep 3.0.3.3 active atm due to the issue however.

I hope this will help.

Same here, update broke posts and in my case made random images appear from my gallery.

I wish WordPress had an easy downgrade option, or the ability to revert to the previous version that was installed.