# Renewing certificate

**URL:** <https://community.letsencrypt.org/t/renewing-certificate/137845>\
**Category:** Help\
**Created:** [November 8, 2020, 5:53pm UTC](https://community.letsencrypt.org/t/renewing-certificate/137845 "2020-11-08T17:53:59Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![pabloperez](https://avatars.discourse-cdn.com/v4/letter/p/8baadc/32.png) [@pabloperez](https://community.letsencrypt.org/u/pabloperez)\
**Post date:** [November 8, 2020, 5:53pm UTC](https://community.letsencrypt.org/t/renewing-certificate/137845/1 "2020-11-08T17:53:59Z")

</div>

Hi  
I have an ACME certificate on a pfsense firewall  
When renewing it gives me an error and no matter how much I look in forums, I cannot find a solution  
Friends, I appreciate the help

HOSTALCHAMU  
Renewing certificate  
account: HOSTALCHAMU-PROD-ACCKEYS  
server: letsencrypt-production-2

/usr/local/pkg/acme/acme.sh --issue -d 'hostalchamu.es' --standalone --listen-v4 --httpport '4002' -d 'www.hostalchamu.es' --standalone --listen-v4 --httpport '4002' --home '/tmp/acme/HOSTALCHAMU/' --accountconf '/tmp/acme/HOSTALCHAMU/accountconf.conf' --force --reloadCmd '/tmp/acme/HOSTALCHAMU/reloadcmd.sh' --log-level 3 --log '/tmp/acme/HOSTALCHAMU/acme\_issuecert.log'  
Array  
(  
[path] =\> /etc:/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin/  
[PATH] =\> /etc:/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin/  
[port] =\> 4002  
[ipv6] =\>  
)  
[Sun Nov 8 18:50:42 CET 2020] Standalone mode.  
[Sun Nov 8 18:50:42 CET 2020] Standalone mode.  
[Sun Nov 8 18:50:42 CET 2020] Multi domain='DNS:hostalchamu.es,DNS:www.hostalchamu.es'  
[Sun Nov 8 18:50:42 CET 2020] Getting domain auth token for each domain  
[Sun Nov 8 18:50:48 CET 2020] Getting webroot for domain='hostalchamu.es'  
[Sun Nov 8 18:50:48 CET 2020] Getting webroot for domain='www.hostalchamu.es'  
[Sun Nov 8 18:50:48 CET 2020] Verifying: hostalchamu.es  
[Sun Nov 8 18:50:48 CET 2020] Standalone mode server  
[Sun Nov 8 18:50:53 CET 2020] Pending  
[Sun Nov 8 18:50:57 CET 2020] hostalchamu.es:Verify error:Invalid response from [https://hostalchamu.es/.well-known/acme-challenge/PX48t8lMLTzK9m3\_yAmg75pMkZXmC6DVWgPIUSe3dfs](https://hostalchamu.es/.well-known/acme-challenge/PX48t8lMLTzK9m3_yAmg75pMkZXmC6DVWgPIUSe3dfs) [85.56.56.239]:  
[Sun Nov 8 18:50:57 CET 2020] Please check log file for more details: /tmp/acme/HOSTALCHAMU/acme\_issuecert.log

---

<div class="post-metadata">

**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\
**Post date:** [November 8, 2020, 6:03pm UTC](https://community.letsencrypt.org/t/renewing-certificate/137845/2 "2020-11-08T18:03:32Z")

</div>

Hi @pabloperez

> [@pabloperez](#):
>
> /usr/local/pkg/acme/acme.sh --issue -d 'hostalchamu.es' --standalone --listen-v4 --httpport '4002' -d 'www.hostalchamu.es' --standalone --listen-v4 --httpport '4002' --home '/tmp/acme/HOSTALCHAMU/' --accountconf '/tmp/acme/HOSTALCHAMU/accountconf.conf' --force --reloadCmd '/tmp/acme/HOSTALCHAMU/reloadcmd.sh' --log-level 3 --log '/tmp/acme/HOSTALCHAMU/acme\_issuecert.log'

first, I'm not so firm with acme.sh.

You use `--standalone`.

Normally, that starts an own webserver to validate your domain.

But:

> [@pabloperez](#):
>
> [Sun Nov 8 18:50:57 CET 2020] hostalchamu.es:Verify error:Invalid response from [https://hostalchamu.es/.well-known/acme-challenge/PX48t8lMLTzK9m3\_yAmg75pMkZXmC6DVWgPIUSe3dfs](https://hostalchamu.es/.well-known/acme-challenge/PX48t8lMLTzK9m3_yAmg75pMkZXmC6DVWgPIUSe3dfs) [85.56.56.239]:

There is a https answer validating your domain. So a http instance answers, redirects to https, then the "file not found" result (open the url in your browser) of your website is visible.

So it's not the webserver startet via `--standalone`, it's your website that answers.

Result: That can't work.

---

<div class="post-metadata">

**Author:** ![Rip](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rip/32/70863_2.png) [@Rip](https://community.letsencrypt.org/u/Rip)\
**Post date:** [November 8, 2020, 8:18pm UTC](https://community.letsencrypt.org/t/renewing-certificate/137845/3 "2020-11-08T20:18:55Z")

</div>

Hello @pabloperez welcome to the community.

A few questions come to mind.

The latest version of "Acme Certificates" service on pfSense is 0.6.9\_2 ... are you up to date?  
Did you use acme.sh for your previous certificates?  
If so how has your configuration changed since June?

> [@pabloperez](#):
>
> I have an ACME certificate on a pfsense firewall

Are you using the certificate for the pfSense "webConfigurator" itself?  
(Assumptions are not a good thing) for public access on port 4002?

One should **NEVER** expose the web GUI to the internet.

The HTTP listening port for the stand-alone server configuration on pfSense must be 80 or have port 80 on WAN forwarded to this port (4002 in your case). AND your firewall rules must allow traffic to reach this port (port forwarding)

> [@pabloperez](#):
>
> Please check log file for more details: /tmp/acme/HOSTALCHAMU/acme\_issuecert.log

Logs are your friend.

---

<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:** [December 8, 2020, 8:19pm UTC](https://community.letsencrypt.org/t/renewing-certificate/137845/4 "2020-12-08T20:19:06Z")

</div>

Closed on December 8, 2020, 8:19pm UTC

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