<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:series="https://publishpress.com/"
	>

<channel>
	<title>ssl &#8211; DevOps Lite</title>
	<atom:link href="https://devopslite.com/tag/ssl/feed/" rel="self" type="application/rss+xml" />
	<link>https://devopslite.com</link>
	<description>DevOps Howtos, Tutorials &#38; Guides</description>
	<lastBuildDate>Thu, 09 Jan 2025 16:04:41 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://devopslite.com/wp-content/uploads/2024/02/favicon.ico</url>
	<title>ssl &#8211; DevOps Lite</title>
	<link>https://devopslite.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Vagrant was unable to check revocation for the certificate</title>
		<link>https://devopslite.com/vagrant-was-unable-to-check-revocation-for-the-certificate/</link>
					<comments>https://devopslite.com/vagrant-was-unable-to-check-revocation-for-the-certificate/#comments</comments>
		
		<dc:creator><![CDATA[Daniel Pham]]></dc:creator>
		<pubDate>Sun, 05 Jun 2022 09:45:46 +0000</pubDate>
				<category><![CDATA[Vagrant]]></category>
		<category><![CDATA[vagrant]]></category>
		<category><![CDATA[ubuntu]]></category>
		<category><![CDATA[curl]]></category>
		<category><![CDATA[ssl]]></category>
		<guid isPermaLink="false">https://devopslite.com/?p=353</guid>

					<description><![CDATA[<p>&#8220;Error: schannel: next InitializeSecurityContext failed: Unknown error (0x80092012) &#8211; The revocation function was unable to check revocation for the certificate.&#8221; If you&#8217;re facing the error above when using Vagrant then&#8230;</p>
<p>The post <a rel="nofollow" href="https://devopslite.com/vagrant-was-unable-to-check-revocation-for-the-certificate/">Vagrant was unable to check revocation for the certificate</a> appeared first on <a rel="nofollow" href="https://devopslite.com">DevOps Lite</a>.</p>
]]></description>
		
					<wfw:commentRss>https://devopslite.com/vagrant-was-unable-to-check-revocation-for-the-certificate/feed/</wfw:commentRss>
			<slash:comments>30</slash:comments>
		
		
			</item>
		<item>
		<title>Access aaPanel through domain</title>
		<link>https://devopslite.com/access-aapanel-through-domain/</link>
					<comments>https://devopslite.com/access-aapanel-through-domain/#respond</comments>
		
		<dc:creator><![CDATA[Daniel Pham]]></dc:creator>
		<pubDate>Fri, 23 Jul 2021 08:41:22 +0000</pubDate>
				<category><![CDATA[aaPanel]]></category>
		<category><![CDATA[panel]]></category>
		<category><![CDATA[hosting panel]]></category>
		<category><![CDATA[domain]]></category>
		<category><![CDATA[ssl]]></category>
		<category><![CDATA[hosting]]></category>
		<category><![CDATA[let's encrypt]]></category>
		<category><![CDATA[aapanel]]></category>
		<guid isPermaLink="false">https://devopslite.com/?p=496</guid>

					<description><![CDATA[<p>In this article, I will guide you to set up aaPanel access through domain. Once you have installed aaPanel, you will access it via a link like https://192.168.10.10:8888/abcxyz. This is&#8230;</p>
<p>The post <a rel="nofollow" href="https://devopslite.com/access-aapanel-through-domain/">Access aaPanel through domain</a> appeared first on <a rel="nofollow" href="https://devopslite.com">DevOps Lite</a>.</p>
]]></description>
		
					<wfw:commentRss>https://devopslite.com/access-aapanel-through-domain/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Monitor website and SSL with blackbox exporter</title>
		<link>https://devopslite.com/monitor-website-and-ssl-with-blackbox-exporter/</link>
					<comments>https://devopslite.com/monitor-website-and-ssl-with-blackbox-exporter/#respond</comments>
		
		<dc:creator><![CDATA[Daniel Pham]]></dc:creator>
		<pubDate>Sat, 15 Aug 2020 09:24:04 +0000</pubDate>
				<category><![CDATA[Prometheus-Grafana]]></category>
		<category><![CDATA[blackbox exporter]]></category>
		<category><![CDATA[website]]></category>
		<category><![CDATA[ssl]]></category>
		<category><![CDATA[prometheus]]></category>
		<category><![CDATA[grafana]]></category>
		<guid isPermaLink="false">https://devopslite.com/?p=325</guid>

					<description><![CDATA[<p>In this article, I will guide you to monitor website and SSL with blackbox exporter. In the previous article, you learned how to use blackbox exporter to monitor host ping.&#8230;</p>
<p>The post <a rel="nofollow" href="https://devopslite.com/monitor-website-and-ssl-with-blackbox-exporter/">Monitor website and SSL with blackbox exporter</a> appeared first on <a rel="nofollow" href="https://devopslite.com">DevOps Lite</a>.</p>
]]></description>
		
					<wfw:commentRss>https://devopslite.com/monitor-website-and-ssl-with-blackbox-exporter/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		
		<series:name><![CDATA[Install Prometheus and Grafana on Ubuntu 18]]></series:name>
	</item>
		<item>
		<title>Set up nginx proxy for Prometheus and Grafana</title>
		<link>https://devopslite.com/set-up-nginx-proxy-for-prometheus-and-grafana/</link>
					<comments>https://devopslite.com/set-up-nginx-proxy-for-prometheus-and-grafana/#respond</comments>
		
		<dc:creator><![CDATA[Daniel Pham]]></dc:creator>
		<pubDate>Sat, 15 Aug 2020 03:39:49 +0000</pubDate>
				<category><![CDATA[Prometheus-Grafana]]></category>
		<category><![CDATA[prometheus]]></category>
		<category><![CDATA[grafana]]></category>
		<category><![CDATA[proxy]]></category>
		<category><![CDATA[ssl]]></category>
		<category><![CDATA[nginx]]></category>
		<category><![CDATA[let's encrypt]]></category>
		<guid isPermaLink="false">https://devopslite.com/?p=295</guid>

					<description><![CDATA[<p>In this article we will set up nginx proxy for prometheus and grafana. In the previous article, you could access prometheus and grafana via IP:Port. However, this does not guarantee&#8230;</p>
<p>The post <a rel="nofollow" href="https://devopslite.com/set-up-nginx-proxy-for-prometheus-and-grafana/">Set up nginx proxy for Prometheus and Grafana</a> appeared first on <a rel="nofollow" href="https://devopslite.com">DevOps Lite</a>.</p>
]]></description>
		
					<wfw:commentRss>https://devopslite.com/set-up-nginx-proxy-for-prometheus-and-grafana/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		
		<series:name><![CDATA[Install Prometheus and Grafana on Ubuntu 18]]></series:name>
	</item>
		<item>
		<title>Upgrade to the new version of Certbot Zimbra 0.7.10</title>
		<link>https://devopslite.com/upgrade-to-the-new-version-of-certbot-zimbra-0-7-10/</link>
					<comments>https://devopslite.com/upgrade-to-the-new-version-of-certbot-zimbra-0-7-10/#comments</comments>
		
		<dc:creator><![CDATA[Daniel Pham]]></dc:creator>
		<pubDate>Mon, 16 Mar 2020 16:08:37 +0000</pubDate>
				<category><![CDATA[Zimbra]]></category>
		<category><![CDATA[ssl]]></category>
		<category><![CDATA[certbot]]></category>
		<category><![CDATA[mail server]]></category>
		<category><![CDATA[zimbra]]></category>
		<guid isPermaLink="false">https://devopslite.com/?p=530</guid>

					<description><![CDATA[<p>Upgrade to the new version of Certbot Zimbra. This is the content of this article. If you&#8217;ve read the previous article that I wrote about how to use Certbot Zimbra&#8230;</p>
<p>The post <a rel="nofollow" href="https://devopslite.com/upgrade-to-the-new-version-of-certbot-zimbra-0-7-10/">Upgrade to the new version of Certbot Zimbra 0.7.10</a> appeared first on <a rel="nofollow" href="https://devopslite.com">DevOps Lite</a>.</p>
]]></description>
		
					<wfw:commentRss>https://devopslite.com/upgrade-to-the-new-version-of-certbot-zimbra-0-7-10/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
		<item>
		<title>Let&#8217;s Encrypt renew error could not bind to IPv4 or IPv6</title>
		<link>https://devopslite.com/lets-encrypt-renew-error-could-not-bind-to-ipv4-or-ipv6/</link>
					<comments>https://devopslite.com/lets-encrypt-renew-error-could-not-bind-to-ipv4-or-ipv6/#respond</comments>
		
		<dc:creator><![CDATA[Daniel Pham]]></dc:creator>
		<pubDate>Thu, 09 Jan 2020 03:07:32 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[ssl]]></category>
		<category><![CDATA[linux tutorial]]></category>
		<category><![CDATA[letencrypt]]></category>
		<category><![CDATA[linux]]></category>
		<guid isPermaLink="false">https://devopslite.com/?p=518</guid>

					<description><![CDATA[<p>Let&#8217;s Encrypt renew error could not bind to IPv4 or IPv6. If you encounter this error when renewing Let&#8217;s Encrypt ssl certificate, maybe this post will help you. This is&#8230;</p>
<p>The post <a rel="nofollow" href="https://devopslite.com/lets-encrypt-renew-error-could-not-bind-to-ipv4-or-ipv6/">Let&#8217;s Encrypt renew error could not bind to IPv4 or IPv6</a> appeared first on <a rel="nofollow" href="https://devopslite.com">DevOps Lite</a>.</p>
]]></description>
		
					<wfw:commentRss>https://devopslite.com/lets-encrypt-renew-error-could-not-bind-to-ipv4-or-ipv6/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Set up Let&#8217;s Encrypt Certbot auto renew</title>
		<link>https://devopslite.com/set-up-lets-encrypt-certbot-auto-renew/</link>
					<comments>https://devopslite.com/set-up-lets-encrypt-certbot-auto-renew/#respond</comments>
		
		<dc:creator><![CDATA[Daniel Pham]]></dc:creator>
		<pubDate>Tue, 07 Jan 2020 05:07:59 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[certbot]]></category>
		<category><![CDATA[linux tutorial]]></category>
		<category><![CDATA[letencrypt]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[ssl]]></category>
		<guid isPermaLink="false">https://devopslite.com/?p=516</guid>

					<description><![CDATA[<p>Set up Let&#8217;s Encrypt Certbot auto renew. This article will guide you to do this. Let&#8217;s Encrypt in the past few years is no stranger to website or system administrators.&#8230;</p>
<p>The post <a rel="nofollow" href="https://devopslite.com/set-up-lets-encrypt-certbot-auto-renew/">Set up Let&#8217;s Encrypt Certbot auto renew</a> appeared first on <a rel="nofollow" href="https://devopslite.com">DevOps Lite</a>.</p>
]]></description>
		
					<wfw:commentRss>https://devopslite.com/set-up-lets-encrypt-certbot-auto-renew/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>How to set up HTTPS for InfluxDB server</title>
		<link>https://devopslite.com/how-to-set-up-https-for-influxdb-server/</link>
					<comments>https://devopslite.com/how-to-set-up-https-for-influxdb-server/#respond</comments>
		
		<dc:creator><![CDATA[Daniel Pham]]></dc:creator>
		<pubDate>Thu, 01 Aug 2019 04:03:06 +0000</pubDate>
				<category><![CDATA[InfluxDB]]></category>
		<category><![CDATA[ssl]]></category>
		<category><![CDATA[database]]></category>
		<category><![CDATA[influxdb]]></category>
		<category><![CDATA[https]]></category>
		<guid isPermaLink="false">https://devopslite.com/?p=462</guid>

					<description><![CDATA[<p>How to set up HTTPS for InfluxDB server? You know, in today&#8217;s internet environment, data security is very important. Using HTTPS in database will make the data transfer between client&#8230;</p>
<p>The post <a rel="nofollow" href="https://devopslite.com/how-to-set-up-https-for-influxdb-server/">How to set up HTTPS for InfluxDB server</a> appeared first on <a rel="nofollow" href="https://devopslite.com">DevOps Lite</a>.</p>
]]></description>
		
					<wfw:commentRss>https://devopslite.com/how-to-set-up-https-for-influxdb-server/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>How to use Let&#8217;s Encrypt SSL in CentminMod</title>
		<link>https://devopslite.com/how-to-use-lets-encrypt-ssl-in-centminmod/</link>
					<comments>https://devopslite.com/how-to-use-lets-encrypt-ssl-in-centminmod/#respond</comments>
		
		<dc:creator><![CDATA[Daniel Pham]]></dc:creator>
		<pubDate>Tue, 30 Jul 2019 08:16:03 +0000</pubDate>
				<category><![CDATA[CentminMod]]></category>
		<category><![CDATA[ssl]]></category>
		<category><![CDATA[centminmod]]></category>
		<category><![CDATA[letencrypt]]></category>
		<guid isPermaLink="false">https://devopslite.com/?p=439</guid>

					<description><![CDATA[<p>How to use Let&#8217;s Encrypt SSL in CentminMod? By default, this script does not enable Let&#8217;s Encrypt SSL. You know, Let&#8217;s Encrypt is a free tool that makes your website&#8230;</p>
<p>The post <a rel="nofollow" href="https://devopslite.com/how-to-use-lets-encrypt-ssl-in-centminmod/">How to use Let&#8217;s Encrypt SSL in CentminMod</a> appeared first on <a rel="nofollow" href="https://devopslite.com">DevOps Lite</a>.</p>
]]></description>
		
					<wfw:commentRss>https://devopslite.com/how-to-use-lets-encrypt-ssl-in-centminmod/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Zimbra unable to start TLS: hostname verification failed</title>
		<link>https://devopslite.com/zimbra-unable-to-start-tls-hostname-verification-failed/</link>
					<comments>https://devopslite.com/zimbra-unable-to-start-tls-hostname-verification-failed/#respond</comments>
		
		<dc:creator><![CDATA[Daniel Pham]]></dc:creator>
		<pubDate>Mon, 17 Jun 2019 08:00:01 +0000</pubDate>
				<category><![CDATA[Zimbra]]></category>
		<category><![CDATA[mail]]></category>
		<category><![CDATA[ssl]]></category>
		<category><![CDATA[mail server]]></category>
		<category><![CDATA[zimbra]]></category>
		<category><![CDATA[ldap]]></category>
		<guid isPermaLink="false">https://devopslite.com/?p=399</guid>

					<description><![CDATA[<p>Zimbra unable to start TLS: hostname verification failed. Have you ever faced this error. Its full content is &#8220;Unable to start TLS: hostname verification failed when connecting to ldap master.&#8220;&#8230;</p>
<p>The post <a rel="nofollow" href="https://devopslite.com/zimbra-unable-to-start-tls-hostname-verification-failed/">Zimbra unable to start TLS: hostname verification failed</a> appeared first on <a rel="nofollow" href="https://devopslite.com">DevOps Lite</a>.</p>
]]></description>
		
					<wfw:commentRss>https://devopslite.com/zimbra-unable-to-start-tls-hostname-verification-failed/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
