2021-11-02 20:32:23 Connection: opening to 127.0.0.1:26, timeout=300, options=array()
2021-11-02 20:32:23 Connection: opened
2021-11-02 20:32:23 SMTP INBOUND: "220 REDACTED.atomicsites.net ESMTP Postfix (Debian/GNU)"
2021-11-02 20:32:23 SERVER -> CLIENT: 220 REDACTED.atomicsites.net ESMTP Postfix (Debian/GNU)
2021-11-02 20:32:23 CLIENT -> SERVER: EHLO REDACTED
2021-11-02 20:32:23 SMTP INBOUND: "250-REDACTED.atomicsites.net"
2021-11-02 20:32:23 SMTP INBOUND: "250-PIPELINING"
2021-11-02 20:32:23 SMTP INBOUND: "250-SIZE 10240000"
2021-11-02 20:32:23 SMTP INBOUND: "250-VRFY"
2021-11-02 20:32:23 SMTP INBOUND: "250-ETRN"
2021-11-02 20:32:23 SMTP INBOUND: "250-AUTH PLAIN"
2021-11-02 20:32:23 SMTP INBOUND: "250-ENHANCEDSTATUSCODES"
2021-11-02 20:32:23 SMTP INBOUND: "250-8BITMIME"
2021-11-02 20:32:23 SMTP INBOUND: "250 DSN"
2021-11-02 20:32:23 SERVER -> CLIENT: 250-REDACTED.atomicsites.net250-PIPELINING250-SIZE 10240000250-VRFY250-ETRN250-AUTH PLAIN250-ENHANCEDSTATUSCODES250-8BITMIME250 DSN
2021-11-02 20:32:23 CLIENT -> SERVER: STARTTLS
2021-11-02 20:32:23 SMTP INBOUND: "502 5.5.1 Error: command not implemented"
2021-11-02 20:32:23 SERVER -> CLIENT: 502 5.5.1 Error: command not implemented
2021-11-02 20:32:23 SMTP ERROR: STARTTLS command failed: 502 5.5.1 Error: command not implemented
SMTP Error: Could not connect to SMTP host.
2021-11-02 20:32:23 CLIENT -> SERVER: QUIT
2021-11-02 20:32:23 SMTP INBOUND: "221 2.0.0 Bye"
2021-11-02 20:32:23 SERVER -> CLIENT: 221 2.0.0 Bye
2021-11-02 20:32:23 Connection: closed
SMTP Error: Could not connect to SMTP host.

That first line seems like a problem. Pressable support says outgoing SMTP is allowed on their platform. This site was migrated from DreamHost, where SMTP Mailer was working correctly. The outgoing SMTP server is set to secure.emailsrvr.com, which is Rackspace.

This website is being hosted by Pressable and it would be ideal to have batcaching working on the site but it’s being prevented by the cookie called wpfront-notification-bar-landingpage. If a cookie contains wp then Batcache won’t cache the page.

I wanted to reach out to
1. Let you know of the incompatibility with Pressable’s caching system.
2. Is there a solution, like is it possible we can change the cookiename to not include “wp”

Thanks!

I am with Pressable Customer Support. I wanted to propose a change in the way the plugin defines paths for the WAF.

On line 7376 of wordfenceClass.php there is this function:

public static function getWAFBootstrapPath() {
return ABSPATH . ‘wordfence-waf.php’;
}

On Pressable, ABSPATH is the location of the core WordPress files. However, those core files are not the same location of the site root.

I’d like to suggest a possible workaround, which will at least work on Pressable sites:

public static function getWAFBootstrapPath() {
if (is_writeable(ABSPATH)) {
return ABSPATH . ‘wordfence-waf.php’;
} else {
return str_replace(‘/wp-content’,”,WP_CONTENT_DIR);
}
}

With a function like this, the Wordfence WAF would enable without issue.

Also, our Director of Support had previously requested a similar change a year ago: https://www.ads-software.com/support/topic/use-wp_content_dir-instead-of-abspath-for-wordfence-waf-php-creation/

Thanks in advance for your consideration!

Best,

Bradly M. Hale
Pressable Customer Support

Need to know if it’s worth migrating from hostgator to bluehost? Any suggestions appreciated.

Unfortunately it’s still acting like I’m just on wordpress.com, except I have an admin dashboard that Pressable gave me access to. I can’t do anything with plugins, can’t see the code, can’t upload my own theme… Why does it seem like I have to upgrade my wordpress.com site to Premium? Did I direct my domain to Pressable incorrectly?

flickr error: cURL Error Number 77: error setting certificate verify locations: CAfile: /wordpress/core/4.6.1/wp-content/plugins/wp-inject/cert/cacert.pem CApath: /etc/ssl/certs/

According to https://curl.haxx.se/libcurl/c/libcurl-errors.html :

– – – – –
CURLE_SSL_CACERT_BADFILE (77)
Problem with reading the SSL CA cert (path? access rights?)
– – – – –

At first I thought there was something wrong with my web host (Pressable), but they investigated this issue and came to the following conclusion:

– – – – –

The problem is that this plugin is trying to load the cert relative to ABSPATH.
With Pressable, ABSPATH only contains WordPress core files, and doesn’t include the plugin files.

CAfile: /wordpress/core/4.6.1/wp-content/plugins/wp-inject/cert/cacert.pem

This issue needs to be corrected by the plugin developer, as it is a design flaw.

They either need to use WP_PLUGIN_DIR or plugin_dir_path() or even better use the WordPress built in cacert bundle in wp-includes/certificates/ca-bundle.crt

It works on your other host only because most hosts have the plugins directory beneath ABSPATH, but not all hosts do.

Using WP_PLUGIN_DIR will guarantee compatibility with all path configuration across different hosts.

– – – – –

So posting this in the support forum because 1) I want to help others with the same problem 2) I do not know of any other way to submit a feature request to the developers of this plugin.