icedterminal
Forum Replies Created
-
Forum: Plugins
In reply to: [WP Crontrol] fatal errorForum: Plugins
In reply to: [WP Crontrol] Fatal Error on 1.13.x versions – only stable 1.12.1Forum: Plugins
In reply to: [WP Crontrol] Fatal error: 1.13.2Forum: Plugins
In reply to: [WP Crontrol] Version 1.13.1 crach my site – see log belowForum: Plugins
In reply to: [WP Crontrol] White Screen of DeathForum: Plugins
In reply to: [WP Crontrol] Plugin broke my siteForum: Plugins
In reply to: [Jetpack - WP Security, Backup, Speed, & Growth] Jetpack BrokenThank 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
Bgrade exists when using Cloudflare. If I disable it, for a direction connection, the grade jumps to anA+. 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 anA+. Thanks for your tip!- This reply was modified 4 years, 11 months ago by icedterminal.
Forum: Plugins
In reply to: [Jetpack - WP Security, Backup, Speed, & Growth] Jetpack Broken@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.
Forum: Plugins
In reply to: [Jetpack - WP Security, Backup, Speed, & Growth] Jetpack Broken– 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/netsHere 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
200when 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 backAn active access token must be used to query information about the current user.I then start getting
400requests when I go to change settings.Forum: Plugins
In reply to: [Jetpack - WP Security, Backup, Speed, & Growth] Jetpack BrokenThis 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