Hello, there.
It looks like your site currently has a “coming soon” / “under construction” mode up at the moment, so Jetpack is unable to properly connect with it.
In order for Jetpack’s features to work, the site must first be accessible to the public.
Once it is ready and up again, please try connecting Jetpack once more and we can go from there. Thanks!
This feels like such a canned response. Unfortunately, all of what you typed isn’t true. I’ve put it into that mode *because* Jetpack doesn’t function. Disabling the maintenance mode it still has issues. This is because I am being *denied* to contact the servers Jetpack is using. If you looked at the screenshots.
Here is a video demonstration showing the site is *not* in maintenance mode and yet Jetpack still fails. https://youtu.be/Ij3_1b_HG8o
Hi @icedterminal
Well, I’m not having any issue activating any features of Jetpack from the WordPress.com dashboard. Please see here: https://d.pr/v/xgzXMS
Is the problem only coming on WP Admin? Or the issue is already solved?
If not, can you try the following:
- Log in to your site via _FTP_ or _SFTP_ or _cPanel > File Manager_ and go to the
wp-content/plugins/ folder and delete the folder named jetpack. After that, reinstall Jetpack plugin from WP Admin.
- I can see you are using Cloudflare, and Cloudflare is already optimized for Jetpack, but when I’m trying to access your XML-RPC file from my browser:
https://YOURSITE.com/xmlrpc.php?for=jetpack it is showing me Access denied message, I think this is only showing in my browser, but XML-RPC is not blocked by Cloudflare. But I might be wrong, so it is better to try again after temporarily disabling the Cloudflare.
@bizanimesh
– I have tried both manual deletion and WP Admin deletion. Either route does not affect the outcome.
– Cloudflare firewall has a rule for XMLRPC to allow the entirety of AUTOM-93. Jetpack included. It is expected that you are denied. Server logs show that in fact Jetpack is allowed. What little bit of it that works.
https://jetpack.com/support/hosting-faq/
http://whois.arin.net/rest/org/AUTOM-93/nets
Here is a video demo showing Jetpack removed, site disconnected, not in maintenance mode, and Cloudflare disabled. Before I recorded I let some time pass to verify that it was in fact disabled. A ping test verifies this showing the true IP and not the Cloudflare proxy IP. System DNS cache was cleared. https://youtu.be/Ai5LbchddSo
Additionally, server logs report 200 when Jetpack runs its routines up until I get,
Uncaught (in promise) DOMException: Failed to register a ServiceWorker for scope ('https://cloud.jetpack.com/') with script ('https://cloud.jetpack.com/service-worker.js'): The user denied permission to use Service Worker.
and
wpcom-xhr-request.19123d4ba738a6188afb.min.js:1 GET https://public-api.wordpress.com/rest/v1.1/me?meta=flags 403 – this particular error sends back An active access token must be used to query information about the current user.
I then start getting 400 requests when I go to change settings.
Anonymous User 18700194
(@anonymized-18700194)
Hi there –
Thanks for your patience as we continue to troubleshoot this. Please confirm that you have configured Cloudflare and Jetpack to work together based on this document:
https://support.cloudflare.com/hc/en-us/articles/218377098-WordPress-Jetpack-and-Cloudflare
Do you have any additional firewall rules that might be conflicting setup in Cloudflare? If so, could you temporarily remove them?
@bobmatyas
Dude. If you read in my previous comment and watch the linked video…
Here is a video demo showing Jetpack removed, site disconnected, not in maintenance mode, and Cloudflare disabled. Before I recorded I let some time pass to verify that it was in fact disabled. A ping test verifies this showing the true IP and not the Cloudflare proxy IP. System DNS cache was cleared. https://youtu.be/Ai5LbchddSo
I have already proven by temporarily disabling Cloudflare, as a whole not just firewall, showing it is not interfering. Again, this feels like another canned response. Three different support individuals have chimed in at this point. I feel like I’ll just end up in loops here.
Hi @icedterminal,
I did some more tests and the debugger returned a different error when trying to connect to your site now:
Your server did not successfully connect to the Jetpack server using HTTPS
Please ask your hosting provider to confirm your server can make outbound requests to jetpack.com.
I wonder if your host (or Cloudflare, since the error popped up while Cloudflare is enabled) are explicitly blocking these requests from not Jetpack.com.
There is definitely a block somewhere at your server’s end (the Console errors in the video I checked confirmed it), the trouble is that we’re having problems pinpointing it.
Can you circle back with your host once again, and see what they find out?
I appreciate your cooperation on this, thanks!
@icedterminal, sorry for the second message. I just had another thought about that and I’d like you to do some due diligence on your SSL certificate as well, just to stay on the safe side.
If it’s not rated as A and is rated anything below (for example, B or worse), then this could be something to address that can help fix the connection hiccup.
Let me know what you find out about that too. Thanks!
Hi @erania-pinnera
Thank you for your feedback and assistance. Yes you are correct. An audit was made and resolved the problem.
There is definitely a block somewhere at your server’s end (the Console errors in the video I checked confirmed it), the trouble is that we’re having problems pinpointing it.
There was a server side software update that was not noticed that changed buffer sizes. Cloudflare was not involved. When updates were ran on WordPress it appeared on the surface Jetpack/WordPress combo were at fault. I forgot to marked this as closed. You may have ran a debug test on the site when it was being debugged internally thus you got an error. It was solved last night. In fact even Google console was emailing about 5xx errors. Haha.
Regarding SSL, the B grade exists when using Cloudflare. If I disable it, for a direction connection, the grade jumps to an A+. I was unaware of this. Did a quick search and found it was a simple setting change in the Cloudflare dash, TLS version. It now shows an A+. Thanks for your tip!
-
This reply was modified 4 years, 11 months ago by
icedterminal.
