airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Christie (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AIRAVATA-2900) Letsencrypt autorenewal fails: fails to bind to port 443
Date Fri, 12 Oct 2018 22:38:00 GMT

     [ https://issues.apache.org/jira/browse/AIRAVATA-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Marcus Christie resolved AIRAVATA-2900.
---------------------------------------
    Resolution: Fixed

Doesn't seem to be a problem anymore.

One theory I have, maybe we originally requested the staging ultrascan cert without the --apache
flag, where certbot spins up a webserver to listen on 443 to get the cert. Now with apache
setup and listening on 443 we need the --apache flag.

> Letsencrypt autorenewal fails: fails to bind to port 443
> --------------------------------------------------------
>
>                 Key: AIRAVATA-2900
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2900
>             Project: Airavata
>          Issue Type: Improvement
>            Reporter: Marcus Christie
>            Assignee: Marcus Christie
>            Priority: Major
>
> This happened on pga.staging.scigap.org:
> {noformat}
> : Attempting to renew cert (staging.ultrascan.scigap.org) from 
> /etc/letsencrypt/renewal/staging.ultrascan.scigap.org.conf produced an unexpected error:
Problem binding to port 44
> Problem binding to port 443: Could not bind to IPv4 or IPv6.. Skipping.
> {noformat}
> I tried updating certbot and the apache plugin to latest, no luck.
> h5. Workaround
> Manually run
> {noformat}
> certbot renew --apache
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message