Rebuild without replacing existing certificates hangs

Kobo On Your Own Server
1

I’m testing different smtp settings. Each time I want to try different settings I do

python3 run.py --setup

However since letsencrypt has a maximum number of certs it will hand out in a given time period I don’t want to choose y when I get to

Existing data found for kf.my.domain.com ....
Continue and replace existing certificate? (y/N)

This causes letsencrypt to hit the maximum number of certs and refuse to issue more

Error creating new order :: too many certificates (5) already issued for this exact set of domains in the last 168 hours

However if I choose N I get

Waiting for environment to be ready. It can take a few minutes.
.....................

Followed by

Wait for another 600 seconds?
	1) Yes
	2) No
[1]: 1

This loops and never completes even if I’m using the exact settings that I know have worked before, pressing return at each build question. If I choose y and letsencrypt issues me new certs then the rebuild completes in next to no time.

2 
Wait for another 600 seconds?
	1) Yes
	2) No
[1]: 2

I’ve found that if I choose No then I can get to the next prompt

Sometimes front-end containers cannot communicate with back-end containers.
Restarting the front-end containers usually fixes it.

Would you like to try?
	1) Yes
	2) No
[1]: 1

This then starts kobo. However this means I’m sat waiting every time I want to make a change, which is quite ridiculous.

It would be good if this process could be improved

1 Like
3

@dyq, :clap: :heart: :partying_face:

1 Like
4

How to solve this issue ??