Can't renew ssl on Raspberry pi 4 with nextcloud

Help
1

Hi I managed to get a nextcloud up and running and I used let’s encrypt ssl. Everything works but for some reason (i’m absolutely a novice) when I try to renew my certificate I get this:
udo certbot renew
Saving debug log to /var/log/letsencrypt/letsencrypt.log

Processing /etc/letsencrypt/renewal/lexors.duckdns.org.conf

Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator apache, Installer apache
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for lexors.duckdns.org
Waiting for verification…
Cleaning up challenges
Attempting to renew cert (lexors.duckdns.org) from /etc/letsencrypt/renewal/lexors.duckdns.org.conf produced an unexpected error: Failed authorization procedure. lexors.duckdns.org (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://lexors.duckdns.org/.well-known/acme-challenge/EI3Qn7IxVT3y_JJNGksMci6_Uo3Gv54mOflfgq0p9cM: Timeout during connect (likely firewall problem). Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/lexors.duckdns.org/fullchain.pem (failure)

All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/lexors.duckdns.org/fullchain.pem (failure)

1 renew failure(s), 0 parse failure(s)

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: lexors.duckdns.org
    Type: connection
    Detail: Fetching
    http://lexors.duckdns.org/.well-known/acme-challenge/EI3Qn7IxVT3y_JJNGksMci6_Uo3Gv54mOflfgq0p9cM:
    Timeout during connect (likely firewall problem)

    To fix these errors, please make sure that your domain name was
    entered correctly and the DNS A/AAAA record(s) for that domain
    contain(s) the right IP address. Additionally, please check that
    your computer has a publicly routable IP address and that no
    firewalls are preventing the server from communicating with the
    client. If you’re using the webroot plugin, you should also verify
    that you are serving files from the webroot path you provided.

Can anybody guide to a solution?
I don’t know if this has anything to do with the problem, but when I insalled nextcloud, the guide I followed made me reroute all http traffic to https…

Thanks

1 Like
2

Hi @RIchard3

there

is no answer. A working port 80 is required.

2 Likes
3

Thanks, but how do i manager to make it work on a port 80?

4

You had a working port 80.

So you have created bugs. Undo these or use your backup to restore your working configuration.

1 Like
5

Thank you very very much!!! You made me realize that I had deleted port 80 forwarding on the router!! I reapplied the rule and certbot renewed my certificate! Thanks again

2 Likes
6

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