<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="nl">
	<id>https://www.vanderschaft.net/mediawiki/index.php?action=history&amp;feed=atom&amp;title=Certbot</id>
	<title>Certbot - Bewerkingsoverzicht</title>
	<link rel="self" type="application/atom+xml" href="https://www.vanderschaft.net/mediawiki/index.php?action=history&amp;feed=atom&amp;title=Certbot"/>
	<link rel="alternate" type="text/html" href="https://www.vanderschaft.net/mediawiki/index.php?title=Certbot&amp;action=history"/>
	<updated>2026-09-12T05:12:58Z</updated>
	<subtitle>Bewerkingsoverzicht voor deze pagina op de wiki</subtitle>
	<generator>MediaWiki 1.45.4</generator>
	<entry>
		<id>https://www.vanderschaft.net/mediawiki/index.php?title=Certbot&amp;diff=5&amp;oldid=prev</id>
		<title>Dschaft: Nieuwe pagina aangemaakt met &#039;Message from py311-certbot-3.1.0,1:  -- This port installs the &quot;standalone&quot; client only, which does not use and is not the certbot-auto bootstrap/wrapper script.  The simplest form of usage to obtain certificates is:   # sudo certbot certonly --standalone -d &lt;domain&gt;, [domain2, ... domainN]&gt;  NOTE:  The client requires the ability to bind on TCP port 80 or 443 (depending on the --preferred-challenges option used). If a server is running on that port, it will n...&#039;</title>
		<link rel="alternate" type="text/html" href="https://www.vanderschaft.net/mediawiki/index.php?title=Certbot&amp;diff=5&amp;oldid=prev"/>
		<updated>2025-06-24T12:54:52Z</updated>

		<summary type="html">&lt;p&gt;Nieuwe pagina aangemaakt met &amp;#039;Message from py311-certbot-3.1.0,1:  -- This port installs the &amp;quot;standalone&amp;quot; client only, which does not use and is not the certbot-auto bootstrap/wrapper script.  The simplest form of usage to obtain certificates is:   # sudo certbot certonly --standalone -d &amp;lt;domain&amp;gt;, [domain2, ... domainN]&amp;gt;  NOTE:  The client requires the ability to bind on TCP port 80 or 443 (depending on the --preferred-challenges option used). If a server is running on that port, it will n...&amp;#039;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;Nieuwe pagina&lt;/b&gt;&lt;/p&gt;&lt;div&gt;Message from py311-certbot-3.1.0,1:&lt;br /&gt;
&lt;br /&gt;
--&lt;br /&gt;
This port installs the &amp;quot;standalone&amp;quot; client only, which does not use and&lt;br /&gt;
is not the certbot-auto bootstrap/wrapper script.&lt;br /&gt;
&lt;br /&gt;
The simplest form of usage to obtain certificates is:&lt;br /&gt;
&lt;br /&gt;
 # sudo certbot certonly --standalone -d &amp;lt;domain&amp;gt;, [domain2, ... domainN]&amp;gt;&lt;br /&gt;
&lt;br /&gt;
NOTE:&lt;br /&gt;
&lt;br /&gt;
The client requires the ability to bind on TCP port 80 or 443 (depending&lt;br /&gt;
on the --preferred-challenges option used). If a server is running on that&lt;br /&gt;
port, it will need to be temporarily stopped so that the standalone server&lt;br /&gt;
can listen on that port to complete the challenge authentication process.&lt;br /&gt;
&lt;br /&gt;
For more information on the &amp;#039;standalone&amp;#039; mode, see:&lt;br /&gt;
&lt;br /&gt;
  https://certbot.eff.org/docs/using.html#standalone&lt;br /&gt;
&lt;br /&gt;
The certbot plugins to support apache and nginx certificate installation&lt;br /&gt;
will be made available in the following ports:&lt;br /&gt;
&lt;br /&gt;
 * Apache plugin: security/py-certbot-apache&lt;br /&gt;
 * Nginx plugin: security/py-certbot-nginx&lt;br /&gt;
&lt;br /&gt;
In order to automatically renew the certificates, add this line to&lt;br /&gt;
/etc/periodic.conf:&lt;br /&gt;
&lt;br /&gt;
    weekly_certbot_enable=&amp;quot;YES&amp;quot;&lt;br /&gt;
&lt;br /&gt;
More config details in the certbot periodic script:&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
 /usr/local/etc/periodic/weekly/500.certbot-3.11&lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
=====&lt;br /&gt;
Message from py311-urllib3-1.26.20,1:&lt;br /&gt;
&lt;br /&gt;
--&lt;br /&gt;
Since version 1.25 HTTPS connections are now verified by default which is done&lt;br /&gt;
via &amp;quot;cert_reqs = &amp;#039;CERT_REQUIRED&amp;#039;&amp;quot;.  While certificate verification can be&lt;br /&gt;
disabled via &amp;quot;cert_reqs = &amp;#039;CERT_NONE&amp;#039;&amp;quot;, it&amp;#039;s highly recommended to leave it on.&lt;br /&gt;
&lt;br /&gt;
Various consumers of net/py-urllib3 already have implemented routines that&lt;br /&gt;
either explicitly enable or disable HTTPS certificate verification (e.g. via&lt;br /&gt;
configuration settings, CLI arguments, etc.).&lt;br /&gt;
&lt;br /&gt;
Yet it may happen that there are still some consumers which don&amp;#039;t explicitly&lt;br /&gt;
enable/disable certificate verification for HTTPS connections which could then&lt;br /&gt;
lead to errors (as is often the case with self-signed certificates).&lt;br /&gt;
&lt;br /&gt;
In case of an error one should try first to temporarily disable certificate&lt;br /&gt;
verification of the problematic urllib3 consumer to see if that approach will&lt;br /&gt;
remedy the issue.&lt;br /&gt;
=====&lt;br /&gt;
Message from python311-3.11.12_1:&lt;br /&gt;
&lt;br /&gt;
--&lt;br /&gt;
Note that some standard Python modules are provided as separate ports&lt;br /&gt;
as they require additional dependencies. They are available as:&lt;br /&gt;
&lt;br /&gt;
py311-gdbm       databases/py-gdbm@py311&lt;br /&gt;
py311-sqlite3    databases/py-sqlite3@py311&lt;br /&gt;
py311-tkinter    x11-toolkits/py-tkinter@py311&lt;/div&gt;</summary>
		<author><name>Dschaft</name></author>
	</entry>
</feed>