July/August 2018 issue of acmqueue The July/August issue of acmqueue is out now
Subscribers and ACM Professional members login here

Everything Sysadmin


  Download PDF version of this article PDF

Error 526 Ray ID: 46e49b182efd214a • 2018-10-23 13:38:45 UTC

Invalid SSL certificate








What happened?

The origin web server does not have a valid SSL certificate.

What can I do?

If you're a visitor of this website:

Please try again in a few minutes.

If you're the owner of this website:

The SSL certificate presented by the server did not pass validation. This could indicate an expired SSL certificate or a certificate that does not include the requested domain name. Please contact your hosting provider to ensure that an up-to-date and valid SSL certificate issued by a Certificate Authority is configured for this domain name on the origin server. Additional troubleshooting information here.


Originally published in Queue vol. 13, no. 8
see this item in the ACM Digital Library



Alpha Lam - Using Remote Cache Service for Bazel
Save time by sharing and reusing build and test output

Jez Humble - Continuous Delivery Sounds Great, but Will It Work Here?
It's not magic, it just requires continuous, daily improvement at all levels.

Nicole Forsgren, Mik Kersten - DevOps Metrics
Your biggest mistake might be collecting the wrong data.

Alvaro Videla - Metaphors We Compute By
Code is a story that explains how to solve a particular problem.


(newest first)

Richard Swan | Fri, 29 Dec 2017 01:08:37 UTC

Fascinating discussion. Thank you. The logic given seems to argue that reliable total automation is often not possible but the better it works the more the humans ready to take over will get bored and ineffective.

Another line of reasoning is that it is poorly designed, often legacy, software that begs to be automated. That is, the worse the underlying components the higher the business pressure to paper over them. This explains why reliable complete automation is rare. The "left over" functionality may be too difficult because the underlying components are poorly design. May, in fact, be impossible to reliably automate without re implementing some of the underlying components.

In my experience production automation projects promise much, take much longer than expected, and do not meet the original goals. While likely to be very unpopular with management, perhaps the right path is to design out many of the problematic components and establish clean APIs before attempting to layer more software on top?

faga moses | Tue, 14 Jun 2016 19:40:33 UTC

What a wanderful I live in this crazy world.

Steve | Fri, 11 Dec 2015 07:48:30 UTC

Thank you for the article. These are really great observations. Does it follow that if you create a script or program that just does one thing and does it really well, that you can take a bunch of these "one" scripts and use them as in the article?

Leave this field empty

Post a Comment:

© 2018 ACM, Inc. All Rights Reserved.