A healthy connection ensures Jetpack essential services are provided to your Wor

Gene,

I took a look at https://blogger.howardstx.com and it appears not to be responding at all.

I would recommend reaching out to your webhost so they can check on this issue, and then once the site is publicly available again, you can try the reconnection instructions in Jetpack support link to see if they work now.

Please let us know if you have any other questions!

Sorry this is not on the default port 80
https://blogger.howardstx.com:9898
This has been up and working fine.

I tested the xmlrpc with curl and was able to get a response as well.
So not really sure what is going on.

Sorry this is not on the default port 80
https://blogger.howardstx.com:9898

Ah, that’s the issue then! Jetpack doesn’t support non-standard ports (port 80 for HTTP and port 443 for HTTPS) for it’s connection.

You should switch it so you’re using port 80 and you should be able to connect Jetpack without any issue.

I hope that clarifies things! Let us know if you have any questions or need help with anything else.

Ok so is there a way to turn off the health check warning that you know of?

If you’d prefer to continue to use the alternate port, you can add this line to the site’s wp-config.php file:

define( 'JETPACK_SIGNATURE__HTTP_PORT', 9898 );

That should fix the connection to Jetpack and clear the error.

Let us know how that goes!

so this caused the following error:
( ! ) Parse error: syntax error, unexpected ‘&’ in C:\wamp64\www\site2\wp-config.php on line 58

this is what I added:

define('AUTH_KEY',         'xxxxxxx');
define('SECURE_AUTH_KEY',  'xxxxx');
define('LOGGED_IN_KEY',    'xxxxx');
define('NONCE_KEY',        'xxxxxxx');
define('AUTH_SALT',        'xxxxxxx');
define('SECURE_AUTH_SALT', 'xxxxxxx');
define('LOGGED_IN_SALT',   'xxxxxx');
define('NONCE_SALT',       'xxxxxx');
define( 'JETPACK_SIGNATURE__HTTP_PORT', 9898 );

• This reply was modified 4 years, 3 months ago by Steven Stern (sterndata).

I tried changing it to:
define('JETPACK_SIGNATURE__HTTP_PORT', '9898' );
to match the existing format this prevents the configuration error but still have the connection error.

• This reply was modified 4 years, 3 months ago by Steven Stern (sterndata).

Hello @gohowardtx,

Please do not reveal your salt keys in your wp-config.php file. You will want to consider updating new keys from this page https://api.www.ads-software.com/secret-key/1.1/salt/

I tried changing it to:
define(‘JETPACK_SIGNATURE__HTTP_PORT’, ‘9898’ );
to match the existing format this prevents the configuration error but still have the connection error.

We’re sorry for the confusion here. Actually, we can not support if your site address having port numbers like this https://blogger.howardstx.com:9898/

You may implement other proxy/caching servers with other port numbers (e.g. 9898) between your real web servers and the address that your site receives HTTP requests. To use Jetpack, your site should be accessible from the public with either https://blogger.howardstx.com or https://blogger.howardstx.com in other words with either port 80 or 443.

In case, you need a reference, here is the implementation of this part.
https://github.com/Automattic/jetpack/blob/fda2cc32dbd11b28cd1acd44a1aa892263d88eaf/packages/connection/legacy/class-jetpack-signature.php#L348-L380