atobias

I logged a ticket @ jetpack.me/support and they were able to help me solve this. Below their response:

It looks like your web server is incapable of sending outgoing requests over HTTPS (as opposed to HTTP). Jetpack should be able to detect this inability and work around it. We’ll work on making that check better in the next version of the Jetpack plugin.

In the meantime, if you are comfortable editing PHP files, you can modify wp-content/plugins/jetpack/jetpack.php.

On line 1290, change the current:

if ( $jetpack->use_ssl[$method] ) {

to the new:

if ( false && $jetpack->use_ssl[$method] ) {

Same error as others:

Your Jetpack has a glitch. Connecting this site with WordPress.com is not possible. This usually means your site is not publicly accessible (localhost).

The site IS public accessible (https://lekkerhapje.nl) and I currently use other WP.com plugins (Stats and Akismet) without any problems.

Hi, I have experienced a similar problem since upgrading to WP 2.0.

I have the permalink options set to Date and name based: https://www.lekkerhapje.nl/2006/03/13/bifteki/

When I create a new post, I have no problems, all permalinks still work fine. I am guessing that is beacause WP doesn’t touch the .htaccess in that case.

The problems come when I try to create (or update) a page. WP then tries to update .htaccess file. In the past it would add several lines to rewrite the page title in the url, but since WP 2.0 it changes the .htaccess into the new 9 line format. This causes all the permalinks to break, all of them leading to the home page when clicked.

I have replaced the classes.php and functions-post.php files as detailed in the thread, but that doesn;t solve anything.

Is there any way to get the “old?? way of generating .htaccess back? Right now the only thing I can do is revert to my old .htaccess file and manually add the rules for the new page evrytime I want to create one.