# Lestencrypt-Standalone cli.ini

**URL:** <https://community.letsencrypt.org/t/lestencrypt-standalone-cli-ini/43465>\
**Category:** Help\
**Created:** [October 3, 2017, 1:15pm UTC](https://community.letsencrypt.org/t/lestencrypt-standalone-cli-ini/43465 "2017-10-03T13:15:16Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![bainim](https://avatars.discourse-cdn.com/v4/letter/b/5fc32e/32.png) [@bainim](https://community.letsencrypt.org/u/bainim)\
**Post date:** [October 3, 2017, 1:15pm UTC](https://community.letsencrypt.org/t/lestencrypt-standalone-cli-ini/43465/1 "2017-10-03T13:15:16Z")

</div>

Hi every one,  
i'm working on generating letsencrypt certification using

> /opt/letsencrypt/letsencrypt-auto certonly --standalone -d [mydomiane.com](http://mydomiane.com)

but i got this response:

> certbot: error : Unexpected line 1 in /etc/letsencrypt/cli.ini: auth:

This is my cli.ini:

> email = [myemail.com](http://myemail.com)  
> auth:  
> method : standalone  
> type: http-01  
> port: 8080  
> agree\_tos = True  
> renew-by-default = True

i'm going to change it like this one:

> email = [myemail.com](http://myemail.com)  
> authentcator = standalone  
> standalone-supported-challenge = http-01  
> port: 8080 (How can i change llis line of the port ??)  
> agree\_tos = True  
> renew-by-default = True

This my question about the port , i don't have an idea how can i add it?  
Thank you

---

<div class="post-metadata">

**Author:** ![jared.m](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jared.m/32/17871_2.png) [@jared.m](https://community.letsencrypt.org/u/jared.m)\
**Post date:** [October 3, 2017, 3:19pm UTC](https://community.letsencrypt.org/t/lestencrypt-standalone-cli-ini/43465/2 "2017-10-03T15:19:23Z")

</div>

I don’t believe you can change the port - Let’s Encrypt will always reach out over 80/443 (for http-01 and tls-sni-01, respectively). This is a security measure, because being able to listen on an arbitrary high-numbered port is not equivalent to asserting control over a server in a multi-user environment.

---

<div class="post-metadata">

**Author:** ![sahsanu](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/sahsanu/32/89984_2.png) [@sahsanu](https://community.letsencrypt.org/u/sahsanu)\
**Post date:** [October 3, 2017, 3:45pm UTC](https://community.letsencrypt.org/t/lestencrypt-standalone-cli-ini/43465/3 "2017-10-03T15:45:24Z")

</div>

> [@jared.m](#):
>
> I don’t believe you can change the port

You can use the directives `--http-01-port` and `--tls-sni-01-port` to specify other ports where certbot will be listening but as you said, `Let’s Encrypt will always reach out over 80/443`, so these port directives are only useful in cases where you are forwarding port 80 or 443 from the router to a machine in your lan listening in another port or something similar 😉

---

<div class="post-metadata">

**Author:** ![jared.m](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jared.m/32/17871_2.png) [@jared.m](https://community.letsencrypt.org/u/jared.m)\
**Post date:** [October 3, 2017, 5:29pm UTC](https://community.letsencrypt.org/t/lestencrypt-standalone-cli-ini/43465/4 "2017-10-03T17:29:03Z")

</div>

Whoops, yep! Forgot about that use case.

---

<div class="post-metadata">

**Author:** ![Patches](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/patches/32/17145_2.png) [@Patches](https://community.letsencrypt.org/u/Patches)\
**Post date:** [October 3, 2017, 7:46pm UTC](https://community.letsencrypt.org/t/lestencrypt-standalone-cli-ini/43465/5 "2017-10-03T19:46:58Z")

</div>

This configuration file uses the equals sign (`=`) for option assignment, not the colon (`:`).

> **[User Guide — Certbot 0.19.0.dev0 documentation](https://certbot.eff.org/docs/using.html#configuration-file)**
>
> Automatically enable HTTPS on your website with EFF's Certbot, deploying Let's Encrypt certificates.

Maybe try `http-01-port = 8080` if you are really forwarding port 80 to 8080 with a firewall.

By the way, all of these options can be specified on the command-line more easily and they still will be remembered by `certbot renew`. You should only mess around with `cli.ini` if you have to issue hundreds of different certificates with the same settings or something.

---

<div class="post-metadata">

**Author:** ![bainim](https://avatars.discourse-cdn.com/v4/letter/b/5fc32e/32.png) [@bainim](https://community.letsencrypt.org/u/bainim)\
**Post date:** [October 3, 2017, 11:01pm UTC](https://community.letsencrypt.org/t/lestencrypt-standalone-cli-ini/43465/6 "2017-10-03T23:01:46Z")

</div>

Thank you for your response

email = [myemail.com](http://myemail.com)  
authentcator = standalone  
preferred-challenges = http  
http-01-port = 8080  
agree\_tos = True  
renew-by-default = True

I changed the config like this and i opened the port 8080 in the firewall , every thing is good

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [November 2, 2017, 11:01pm UTC](https://community.letsencrypt.org/t/lestencrypt-standalone-cli-ini/43465/7 "2017-11-02T23:01:48Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
