<p>
	Let's Encrypt requires a bit of initial configuration.
</p>
<p>
	First of all, the system must be reachable from the Internet for validation! To verify that, the host command may be used.
</p>
<pre>
host -t A service1.example.com
service1.example.com has address 1.2.3.4
</pre>
<p>
	To configure the service, switch to the App Settings below. Set your desired domain(s) and services and click &quot;Save changes&quot;. The configured services will be restarted, once the certificate has been obtained and configured.
	<br>
</p>
<p>
	The app always starts obtaining a new certificate when changes are saved! Once the certificate is successfully obtained, Let's Encrypt is fully set up and renews the certificate on it's own.
</p>
<p>
	If you want to change the hostname in the certificate later on, just change the configuration in the App Settings and save.
	<br>
	&nbsp;
	<br>
	In certain scenarios, which incorporate NAT, or cloud environments like AWS, the internal domain verification of the App might fail, despite the DNS being configured correctly and Let's Encrypt being able to issue a certificate for the server.
	<br>
	In these cases, adding a manual DNS entry on the system running the Let's Encrypt App can help:
	<br>
</p>
<pre>
ucr set hosts/static/&lt;EXTERNAL-IPADDRESS&gt;=&lt;LETS-ENCRYPT-HOSTNAME&gt;
</pre>
<p>
</p>
<p>
	If you encounter problems with the obtained certificate, please have a look at the status of the App via the App Settings page and the log file <b>/var/log/univention/letsencrypt.log</b>. All actions of the app are written to this log file. Also, refer to the &quot;Troubleshooting&quot; section in the original <a href="http://wiki.univention.com/index.php?title=Cool_Solutions_-_Let%27s_Encrypt#Troubleshooting" target="_blank">article about Let's Encrypt</a> in the Univention Wiki.
</p>
