Mark

Thanks, yes all sorted. Not sure about the cause as never seen before, even though all my sites are hosted with the same provider. Perhaps it was a DNS issue after all.

I tried again this morning to get jetpack to connect and it was back to how it should be. I honestly have no idea why I had these problems. The CDN had been re-enabled. The only possible cause I can think of is possibly slow recognition of DNS changes (nameservers).

Scratch the reply I made above as a possible red herring ?? The original error message is back and I can no longer get to the CONNECT screen.

It would be helpful to know what ‘registration secrets’ Jetpack is looking for and we might be able to make a bit more progress on this. Incidentally, I’m using Chrome.

PS – there is an EDGE caching CDN network running with this host, but changing settings to those elements appear to be a factor – if I switch those into development mode (disables all caching) I can get to the CONNECT screen, then it switches to the WP site.

I can then click APPROVE but, although it tries authorizing, it errors out, refreshes, and lets me try again. So far, I’m stuck in that loop, but I’ll give it an hour or 2 just in case there is any leftover cache to expire.

I’ve just installed a new site with 20i hosting and I’m encountering the exact same issue. There are no plugins installed yet apart from Jetpack, but it comes up with that registration secrets message when trying to get to the screen that would NORMALLY allow me to connect to JetPack. I’ve run a permissions check on the files but this did not help.

It’s a brand new, one-click install hosted WordPress site – I thought it might be down to propagation issues with DNS as the nameservers were only changed a couple of days ago, but it’s still doing it today.

Never seen this message ever before on any of my WP sites, and I have quite a lot of them!

I have a possible workaround – I am using PayPal Pro Hosted although it is also not sending for any other gateway or Local Pickup etc.

It appears that it works OK when selecting the plain text option within the WooCommerce Email settings. It stops working when selecting HTML.

This might be a workaround for anyone having similar problems.

Rgds, Mark

• This reply was modified 6 years, 10 months ago by Mark.

Same here – using PayPal Pro Hosted. Although, sometimes it seems to work, most of the time it doesn’t. No rhyme or reason. Using our VPS but email components/SMTP etc all OK. Very frustrating and rather strange.

I’ve just re-tried – works like a charm, thanks!

Hi it’s version 1.0.4

Have just generated crash report via app to you. Hope this helps. Rgds Mark

Right now, I seem to have overcome this problem by completely removing Jetpack and reinstalling it. If the problem reoccurs I’ll post via that form. I can’t really provide any more useful information right now – it was working then it wasn’t and nothing was changed on the site (although I was tinkering with W3 cache plugin – but unsure how that would affect the connection).

Really strange though to see a valid padlock in the backend prior to connecting, then an invalid padlock when being returned to my site!

Thanks for now anyways.

Yes!

Actually, I don’t have this quite right. Upon further investigation, it seems that Let’s Encrypt is working fine. I get the valid padlock when logged into the back end of WordPress.

However, when going through the connection process to Jetpack, authorization, etc, Jetpack then passes me back to the dashboard. From then on, the padlock is broken (the https is crossed out in the url).

It’s very strange. I administer the vps myself and the server is fine and the certificate for Let’s Encrypt is up to date.

It’s the process of being passed back to the dashboard from Jetpack which throws the SSL error.

I’m getting this too. I have a VPS running Let’s Encrypt but, for some reason, I get the https version of the site when viewing front end validating OK. When I’m in the dashboard, the https is crossed out in the browser address bar (invalid). So the certificate seems fine when you are viewing the site from the front end, but not the dashboard (backend). This only started happening this week.

I’m out of knowledge on this one unfortunately. I don’t think my problem is XMLRPC related – Let’s Encrypt seems to be securing the public part of the website correctly, but not the wp-admin side!!

https://www.scentperfique.com

Did you get anywhere with this at all? I’ve a site running on a Vultr VPS and I’ve just sterted to get this too. Using Let’s Encrypt as the SSL. Thanks (in hope rather than expectation)!

I don’t know if this is relevant but I’m trying to integrate Trusted Store too. I’ve also tried manually inserting the JS direct into the theme but no luck.

I do not even get a progress bar when testing it out from the Google link supplied. However, the JS code is definitely there when I check the source code.

I’ll raise this with Google in the hope they may have an explanation but I’d be interested to find out if anyone ever got this to work with Woocommerce and, if so, how they tackled it!

• This reply was modified 7 years, 9 months ago by Mark. Reason: typo