I’ve been getting the following error recently when making multiple calls using PHP curl (specifically Laravel’s artisan tinker)
If you’re here because the playhead is doing some sort of dance – 6 frames forward, 4 frames back, repeat – and you use some sort of non-standard audio interface (In my case Voicemeeter Banana) make sure that audio interface is available and in the case of a software interface make sure it’s running.
I go just long enough between websites that I’m always forgetting this little number. Putting it here so I can just grab it next time.
Ok this has been bugging me. I recently got a notification from Facebook saying I had been blocked from creating Open Graph things for a day. Honestly couldn’t think of any reason as to why. As for you folks out there that just want to get to the part where I tell you how to remove all apps from Facebook in one go just jump down underneath the images it’s there under its own heading. I do apologise for waffling it’s just that without typing a bunch of stuff Google doesn’t care about your content so you never get listed anywhere on its search engine. Hence this story. Such is life.
Blast off! Oh that’s cheesy. If you’re into your code and you’re into your space you may be interested in hearing that the source code for the Apollo 11 guidance computer has been put up on GitHub: Apollo 11 Guidance Computer source code.
Of course the internet is having its way with it right now, filing issues such as adding a pull request that provides an extension pack for picking up Matt Damon. There have also been some important typo fixes that were missed originally that the internet of course has now fixed.
Other issues include a request to modernise the code by adding a Dockerfile. Finally there’s also a request to tidy up the repository, as having all of the source code in the top level is disturbing.
In all seriousness, it is quite an interesting one to have a look around even if you don’t understand it. Just to see how much (rather, how little?) code it took to get man to the moon. This is a part of our history here nerds. Browse it, read it, love it!
Like most of the posts on this site something’s been bugging me for almost years at this point (ok, a year.. probably less) and it’s finally pushed me over the edge to try to fix it. – My screen keeps going black, seemingly randomly whenever it decides it wants a breather. Let me preface I’ve got an NVIDIA GPU of some sort for the gaming and whatnot. It uses the NVIDIA GeForce control panel to sort its inner workings. If you’ve not got that you might be able to play along here but also you might be out of luck. Let me know in the comments if this helps either way.
What is a thud?
It’s a loud sudden noise, hyuk hyuk.
Oh man. Whoo-boy. I have tripped over.
No I don’t mean the event that caused the actual hip break, I have a full on post about what happened there in the works but it’s a wordy boring one.
Christmas with a broken hip. Not a good idea! Whatever happened to the days when people would give you shower gels, deodorants and socks? This year it was all chocolate! No word of a lie I wouldn’t be surprised if the amount of chocolate in the house right now weighs more than me!
I’ve been using Laravel a lot lately. Like seriously, a lot. I’m using it for Pdcast as well as a project in my day job.
Part of the draw to using Laravel was that there’s a LTS (Long Term Support) release available now, version 5.1! This version requires PHP 5.5.9+, however that’s not included in your bog standard CentOS or EPEL repositories.
Nice and quickly then, lets get the latest PHP installed so we can use the new Laravel. We’re assuming you’ve already got PHP installed, if not then replace the following “update” command with a yum install php command, keeping the enablerepos intact.
yum install http://rpms.famillecollet.com/enterprise/remi-release-6.rpm yum update --enablerepo remi --enablerepo remi-php55
You should now be at (at the time of writing) PHP version 5.5.26. Get your Laravel 5.1 on!
Well here’s one to get into straight away! Recently tried activating Jetpack but had this pop up instead?
Your Jetpack has a glitch. Something went wrong that’s never supposed to happen. Guess you’re just lucky:
Try connecting again.
Error Details: The Jetpack server could not communicate with your site’s XML-RPC URL. Please check to make sure https://icnerd.com/xmlrpc.php is working properly. It should show ‘XML‑RPC server accepts POST requests only.’ on a line by itself when viewed in a browser and should not have any blank links or extra output anywhere.
I’m betting either you have indeed blocked the xmlrpc file (and if you have why would you be here, you know what’s wrong!) or you are using CloudFlare?
Basically the problem is that CloudFlare is blocking access to the URL
Unfortunately the only quick solution would be to disable CloudFlare, enable Jetpack and re-enable Cloudflare. I’m uncertain if Jetpack ever really tries to reconnect via this endpoint however, so i might be the case later that your Jetpack plugin stops working again if you do this.
If you absolutely need CloudFlare enabled, I’d say contact their support and see if there’s anything they can do to help you. Otherwise it might be worth either dropping either Jetpack or Cloudflare as unfortunate as that may be.
I’ll check on this in a month or so to see if there’s anything else out there on this issue! Let me know if you have found any other workarounds! Oddly enough it just worked on one of my sites while testing for this article, but not another site. Very odd behaviour. Just to note I’ve currently tried adding a page rule in to bypass caching/security on this specific URL however that did not resolve the issue. I’ll keep trying! 🙂