Troubleshooting TLS Certificates
I was recently working on a blog post involving the use of TLS certificates for encryption and authentication, and was running into errors. I’d checked all the “usual suspects”—AWS security groups, host-level firewall rules (via iptables), and the application configuration itself—but still couldn’t get it to work. When I did finally find the error, I figured it was probably worth sharing the commands I used in the event others might find it helpful.
The error was manifesting itself in that I was able to successfully connect to the application (with TLS) on the loopback address, but not the IP address assigned to the network adapter. Using ss -lnt, I verified that the application was listening on all IP addresses (not just loopback), and as I mentioned earlier I had also verified that AWS security groups and host-level firewall weren’t in play. This lead me to believe that there was something wrong with my TLS configuration.
Since the application’s error message was extremely vague (and not even remotely TLS-related), I decided to try using curl to verify that TLS was working correctly. First I ran this command:
curl --cacert /path/to/CA/certificate https://127.0.0.1 -v
After some output, curl Continue reading


Michael Wood took another emerging technology vendor, VeloCloud, to the top of the SD-WAN market. Apstra wants him to do the same for its company and intent-based networking.
Hybrid cloud computing for high performance computing is quickly becoming commonplace, but there are certain challenges that CIOs must overcome in order to reap all the benefits.
The vendor has sidled up next to Nokia and Ericsson as a dominant 5G equipment supplier to the largest carriers in the U.S.
The cloud is too big to fail. And Microsoft doesn’t want to hoard the emulation technology.