While working on my new site for an online printing service I encountered a strange problem. I was wondering about the Google Search Console complaining that the robots.txt is throwing a 404. But I could see the correct content in the browser! The following was kind of unexpected.
While setting up Nginx I followed various guides on the web — but was primarily inspired by https://codex.wordpress.org/Nginx, which suggested this configuration:
location = /robots.txt {
allow all;
log_not_found off;
access_log off;
}Looks nice, right? Everyone can access it and no spamming the logs.
Wrong.
The problem is based on my situation in that I was having PHP generate the robots.txt on demand. I’ve installed a very nice plugin called “XML Sitemap & Google News feeds” which does all the heavy lifting for me. This also means that there is no physical robots.txt …
After moving my WordPress site from a LAMP to a LEMP stack (replacing Apache with Nginx), I wanted to upload some new images — but I couldn’t. I either got a “HTTP Error” or “413 Request Entity Too Large”. So I started my research.
Some minutes later I stumbled upon a little older blog post of Dave Perrett, which suggests increasing the max allowed body size. In fact my images were a little bigger than small.
After adding “client_max_body_size 20M;” to the server section of the nginx site configuration the upload worked as expected.
Originally published at Coding, beautiful appearances and some.
Currently I’m uploading about 16GB of images into my Google Drive account. At first I tried to copy them into my local drive folder in order to let the Files.app synchronize everything automatically. Only to discover that the process takes decades to finish and is even having problems while uploading. Lucky I was, the solution is simple.
I opened https://drive.google.com and began uploading them again. This actually works much better and without all those sync errors and retries. Only caveat is that I have to leave the Chromebook running. I’m using the Keep Awake extension for such tasks.
While browsing the web whether other people would have the same bad experience using the local drive sync I stumbled upon the Image loader extension. You can see it in the task manager, consuming not only a subtle amount of RAM. Nobody installed it and nearly nobody knows what it does. …
About
