Upload error 413 “Request Entity Too Large” on Nginx

When trying to upload files to a Drupal installation running on nginx, we got a 413 error: Request Entity too large.   We had gone through and updated the php files with regard to max upload file size limits, but had neglected to do the same to the nginx config file (/etc/nginx/nginx.conf on Debian). We had to add the following line:
client_max_body_size 20M;
  in the http block and restart the nginx server to get uploads working again. The above will set the limit to 20MB; change it to suit your own environment and needs.   You can also add this to the server or location blocks.

Securing Dokuwiki with nginx

After migrating a server from Apache2.4 to nginx a Dokuwiki install was complaining about the following on the admin page:
Dokuwiki security error with nginx
Dokuwiki security error with nginx
  Previously .htaccess files were controlling access, which aren’t used by nginx. You can test your Dokuwiki install’s access by attempting to visit the following url:  
http://yourserver.com/data/pages/wiki/dokuwiki.txt
  If you can see any content there, you need to fix your permissions. We fixed this by adding the following to the site’s nginx config file (e.g. /etc/nginx/sites-available/sitename):  
location ~ ^/(data|conf|bin|inc) { deny all; }
  …in the same section as the other “location” stanzas, then restarted nginx (whether the latter is necessary or not I don’t know, force of habit).

Drupal 7 – Two administrative menus after module installed

In Drupal 7 when trying to use the module “Administration Menu” (quite a handy module) after enabling it we ended up with two menus or toolbars: Drupal 7 - Two menus or toolbars The fix for this is to disable the existing “Toolbar” module – this should remove the original toolbar and leave you with just the new Administration Menu menu/toolbar.

OpenSMTPD and Thunderbird: smtp-in: Bad input on session 5.5.1 Invalid command: Pipelining not supported

While trying to connect to OpenSMTPD running on Debian Stretch Thunderbird couldn’t auto-configure the account and provided the following error in the logs:  
email smtpd[566]: smtp-in: Bad input on session 6567905e3020707c: 500 5.5.1 Invalid command: Pipelining not supported
  This is a Thunderbird config issue, not a server side issue. Change the settings from SSL/TLS to STARTTLS and that should sort it.

Adobe Photoshop Lightroom 5.7 and Mac OS X – will no longer open

After upgrading Lightroom 5.6 to 5.7, it refused to open with the error:
  Library not loaded: @executable_path/../Frameworks/asneu.framework/versions/a/asneu
  This problem stems from the fact that the system drive is a case sensitive file system; in a similar vein, we were recently unable to install Adobe CC on a similar system as it is also incompatible with a case sensitive file system. We fixed our Lightroom issue by changing the path from:  
/Applications/Adobe Photoshop Lightroom 5.app/Contents/Frameworks/asneu.framework/Versions/A
  to:  
/Applications/Adobe Photoshop Lightroom 5.app/Contents/Frameworks/asneu.framework/versions/a
  The above assumes a normal install to the /Applications directory. If you are game to try the change yourself, you make the change via Terminal:  
cd /Applications/Adobe\ Photoshop\ Lightroom\ 5.app/Contents/Frameworks/asneu.framework sudo mv Versions versions cd versions sudo mv A a
  Now try and start Lightroom and you should be successful.

Proxmox KVM virtual machine: Cannot delete due to missing storage

Today we encountered a situation where a Proxmox system’s KVM virtual machine refused to delete after the storage volume that it’s virtual HDD resided on was lost; trying to delete the KVM from the web GUI resulted in the following error:  
TASK ERROR: storage ‘proxmoxHDD’ does not exists
  Attempting to delete it from the command line using:  
qm destroy [VM ID]
  …resulted in:  
storage ‘proxmoxHDD’ does not exists
  Fortunately, there’s a way around this. The KVM config files live in:  
/etc/pve/qemu-server
  Move or erase the [VM ID].conf file and when you refresh your web GUI the VM should be gone.