Random Delay at startup

[DrGeek]

Is this behaviour normal ? (I'm discovering bitwarden since today... The dock didn't want to launch before, no reason for working right now, I didn't change anything).

Each time I do a ./bitwarden.sh start I have to wait a delay because of the "Non-interactive renewal" of the letsencrypt certificate (don't understand why : it doesn't need to be renewed) ;

./bitwarden.sh start
 _     _ _                         _            
| |__ (_) |___      ____ _ _ __ __| | ___ _ __  
| '_ \| | __\ \ /\ / / _` | '__/ _` |/ _ \ '_ \ 
| |_) | | |_ \ V  V / (_| | | | (_| |  __/ | | |
|_.__/|_|\__| \_/\_/ \__,_|_|  \__,_|\___|_| |_|

Open source password management solutions
Copyright 2015-2018, 8bit Solutions LLC
https://bitwarden.com, https://github.com/bitwarden

===================================================

Docker version 18.09.0, build 4d60db4
docker-compose version 1.23.1, build b02f1306

Removing network docker_default
WARNING: Network docker_default not found.
Pulling mssql         ... done
Pulling web           ... done
Pulling attachments   ... done
Pulling api           ... done
Pulling identity      ... done
Pulling admin         ... done
Pulling icons         ... done
Pulling notifications ... done
Pulling nginx         ... done
Using default tag: latest
latest: Pulling from certbot/certbot
Digest: sha256:xxxx
Status: Image is up to date for certbot/certbot:latest
Saving debug log to /etc/letsencrypt/logs/letsencrypt.log
Non-interactive renewal: random delay of 370 seconds

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Processing /etc/letsencrypt/renewal/xxx.xx.xxx.conf
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Cert not yet due for renewal

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

The following certs are not due for renewal yet:
  /etc/letsencrypt/live/xxx.xxx.xxxx/fullchain.pem expires on 2019-03-16 (skipped)
No renewals were attempted.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Creating network "docker_default" with the default driver
Creating bitwarden-attachments   ... done
Creating bitwarden-admin         ... done
Creating bitwarden-nginx         ... done
Creating bitwarden-api           ... done
Creating bitwarden-mssql         ... done
Creating bitwarden-web           ... done
Creating bitwarden-notifications ... done
Creating bitwarden-icons         ... done
Creating bitwarden-identity      ... done
Total reclaimed space: 0B
1.28.0: Pulling from bitwarden/setup
Digest: sha256:xxx
Status: Image is up to date for bitwarden/setup:1.28.0


Bitwarden is up and running!
===================================================

visit https://xxx.xxx.xxx
to update, run `./bitwarden.sh updateself` and then `./bitwarden.sh update`

[kspearrin]

Looks like something LE does. Source code here:
https://github.com/certbot/certbot/blob/master/certbot/main.py#L1272