thanks @jsha
i tried with the folders specified with no luck
below is a screenshot
I can see certbot created the right directories (so no issues with /etc, which i honestly thought would be an issue)
from the log file
2017-02-16 10:58:19,432:WARNING:certbot.client:Non-standard path(s), might not work with crontab installed by your operating system package manager
2017-02-16 10:58:19,432:DEBUG:certbot.storage:Archive directory C:\etc\letsencrypt\archive\certbot-windows.firecube.xyz-0001 and live directory C:\etc\letsencrypt\live\certbot-windows.firecube.xyz-0001 created.
2017-02-16 10:58:19,448:DEBUG:certbot.main:Exiting abnormally:
Traceback (most recent call last):
File “C:\Python36\Scripts\certbot-script.py”, line 11, in
load_entry_point(‘certbot==0.11.1’, ‘console_scripts’, ‘certbot’)()
File “c:\python36\lib\site-packages\certbot\main.py”, line 882, in main
return config.func(config, plugins)
File “c:\python36\lib\site-packages\certbot\main.py”, line 659, in obtain_cert
action, _ = _auth_from_available(le_client, config, domains, certname, lineage)
File “c:\python36\lib\site-packages\certbot\main.py”, line 108, in _auth_from_available
lineage = le_client.obtain_and_enroll_certificate(domains, certname)
File “c:\python36\lib\site-packages\certbot\client.py”, line 312, in obtain_and_enroll_certificate
self.config)
File “c:\python36\lib\site-packages\certbot\storage.py”, line 966, in new_lineage
target[kind])
OSError: symbolic link privilege not held
I can see in storage.py that os.symlink is used and thought that was the problem however have a look at it i can the method is ok for windows
so the question I am trying to figure out is since we are fine to this point (csrs are created and keys are created) is there a way on not using symlinks at the final stage for the certs
will continue to wade through code
so closseeeeeeee!