I’ve had this issue a couple of times and I formulated a devops-stackexchange question eventually. Although I do not yet really have a way to debug the NEW state, there is some information there: Docker container stuck in “new” state – Docker swarm – service stack
Because since recently, whenever I update Docker, my docker-machine command is gone and I keep forgetting how to re-install it: This is to save time next time it happens. Instructions provided on docker/machine Github.
Just a repost to remember: How to install VirtualBox Guest Additions on a GUI-less Ubuntu server host
HSTS is for security, I get it. But it can be so fucking annoying. Here is how to clear it for specific domains: superuser: How to stop an automatic redirect from “http://” to “https://” in Chrome
This is just a quick repost of RUN A SHELL FROM JENKINS USING SUDO (UBUNTU) Disclaimer: This is UNSAFE and you should NEVER do it unless in a protected, shielded and non-public-accessible dev environment. This is not even safe enough for a permanent testing environment.
Google has HSTS and some domains fall under it automatically. This makes Chrome automatically use HTTPS instead of HTTP. As I often work on local/development/testing environments in internal, protected networks HTTPS is not necessary. Yet Chrome forces me to HTTPS everytime anywas. This thread to the rescue: How to stop an automatic redirect from “http://”… Continue Reading Disabling HSTS for any domain
This is a nifty script I found to manually test SMTP servers: Script for testing SMTP with Telnet
Sometimes there are problems to export a website certificate that is not trusted by one of the major CAs (self-signed or development certificates for example). Usually you’d open the certificate details in Chrome, then drag and drop the image icon to any folder on your computer (for example your Desktop). Then you’d double click it and import… Continue Reading Export Website Certificate from Chrome on OSX
When creating new docker-machine Docker nodes, one needs to add necessary root CA certificates to them in order to let them communicate with SSL protected services. The easiest, if manual, method is to copy the ca certificate (in .pem format) to /var/lib/boot2docker/certs on EVERY swarm node (if running in swarm mode).
What the shait this has been annoying… Well, here is the bottom line: Issue Your Own Self-Signed S/MIME Certs with OpenSSL by using these two shell scripts: makeauthority.sh makecert.sh