Just a quick one, hoping it will help someone,
If you have a wordpress site with WPBakery Page Builder running on it, and find the frontend builder is not working, and if you also happen to use cloudflare – Rocket Loader™ is your issue.
Go to cloudflare and under speed –> Optimization –> turn off Rocket Loader™
Go back to WordPress and within a few mins, or the time your cache takes to update – your visual composer/WPBakery Page Builder will be working again.
Ubiquiti kit is great, and Unifi is by far the best value for money WiFi kit out there. However once you get beneath the beautifully crafted UI and you’ll soon struggle to find CLI info and configuration help.
SSH into your USG, using your site specified SSH credentials, or if you have never set any, then ubnt/ubnt.
Then simply type:
show vpn log
or:
cat /var/log/charon.log | tail -n 100
Simple.
As a wordpress user, or hosting admin i’m sure you have seen it before – the dreaded err_too_many_redirects page.
This is caused by a number of issues, including:
There are countless reasons that could cause this error, and most of them are easily fixable with a quick google. However Yesterday i came across a new one.
If you came here for the Solution here it is:
Edit your wp-config.php file and at the bottom add:
if (strpos($_SERVER['HTTP_X_FORWARDED_PROTO'], 'https') !== false)
$_SERVER['HTTPS']='on';
Well, in this case it was a combination of things, this is very specific to three things in this environment. 1) Shared Hosting. 2)No root SSL Certificate. 3)CloudFlare ‘Always use HTTPS’ settings.
After taking a step back and working out the basics of what i had, and why other ‘fixes’ that usually work, weren’t- i realised what i had here, was a simply reverse proxy. That is, that where the files are hosted without SSL, but the reverse proxy (in this case CloudFlare) was using SSL.
Finally, i found this nugget in the WordPress Codex:
https://codex.wordpress.org/Administration_Over_SSL#Using_a_Reverse_Proxy
And it all clicked.
“If WordPress is hosted behind a reverse proxy that provides SSL, but is hosted itself without SSL, these options will initially send any requests into an infinite redirect loop.
And that is why we need to tell wordpress to force SSL to prevent this WordPress redirect loop when using CloudFlare.
Hope that someone finds this helpful!
Well thanks for that, now what am i supposed to gain by knowing this information!?
Simply put, this is a technical jargon inside joke – and something that we can learn a couple of lessons from,
Video here:
Full transcript below:
“For a number of years now, work has been proceeding in order to bring perfection to the crudely conceived idea of a transmission that would not only supply inverse reactive current for use in unilateral phase detractors, but would also be capable of automatically synchronizing cardinal grammeters. Such an instrument is the turbo encabulator.
Now basically the only new principle involved is that instead of power being generated by the relative motion of conductors and fluxes, it is produced by the modial interaction of magneto-reluctance and capacitive diractance.
The original machine had a base plate of pre-famulated amulite surmounted by a malleable logarithmic casing in such a way that the two spurving bearings were in a direct line with the panametric fan. The latter consisted simply of six hydrocoptic marzlevanes, so fitted to the ambifacient lunar waneshaft that side fumbling was effectively prevented.
The main winding was of the normal lotus-o-delta type placed in panendermic semi-boloid slots of the stator, every seventh conductor being connected by a non-reversible tremie pipe to the differential girdle spring on the “up” end of the grammeters.
The turbo-encabulator has now reached a high level of development, and it’s being successfully used in the operation of novertrunnions. Moreover, whenever a forescent skor motion is required, it may also be employed in conjunction with a drawn reciprocation dingle arm, to reduce sinusoidal repleneration.
Further information is available about this great device is available here on its own Wikipedia page: Turboencabulator Transcript is from TheChiefStoryteller.
