It produced this output:
Traceback (most recent call last):
File “c:\python27\lib\runpy.py”, line 174, in _run_module_as_main
"main", fname, loader, pkg_name)
File “c:\python27\lib\runpy.py”, line 72, in run_code
exec code in run_globals
File "C:\Python27\Scripts\certbot.exe_main.py", line 5, in
File “c:\python27\lib\site-packages\certbot\main.py”, line 16, in
from certbot import account
File “c:\python27\lib\site-packages\certbot\account.py”, line 21, in
from certbot import util
File “c:\python27\lib\site-packages\certbot\util.py”, line 23, in
from certbot import lock
File “c:\python27\lib\site-packages\certbot\lock.py”, line 3, in
import fcntl
ImportError: No module named fcntl
My web server is (include version): N/A, using Windows PowerShell
The operating system my web server runs on is (include version): Windows 10
My hosting provider, if applicable, is: N/A
I can login to a root shell on my machine (yes or no, or I don’t know): I don’t know
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): No
Did you see a suggestion to use Certbot on Windows somewhere? Our documentation tries to suggest that Certbot isn't ready for use on Windows currently:
Instead, we would typically suggest using one of the Windows client listed at
although several of the Unix clients there are also cross-platform enough to work on Windows too.
As I’m told, Windows can now run Linux code natively (haven’t tried it myself thou - yet).
Sure, Microsoft does have
available now. However, this doesn't mean that all Linux software will immediately run directly in every Windows environment! If you're not actually using WSL with a Linux distribution, you can expect to encounter compatibility problems with Certbot, which is still designed for a Unix environment. Users who aren't intentionally using WSL this way should probably currently use a Windows Let's Encrypt client, not Certbot.