Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is it possible to point 2 instances of openresty to the same redis instance and share certs? #257

Open
MemoryLeak55 opened this issue May 19, 2021 · 3 comments

Comments

@MemoryLeak55
Copy link

Hi

I would like to know if it is possible to share certs using the redis adapter by pointing 2 instances of openresty to the same redis.

My current situation is that I have 2 points of ingress both with openresty, and all the domains have double A records to both these instances. Using the file based certs do not work when you have double A records as often lets encrypt will select the wrong A record to do the challenge with, and go to the wrong openresty which of course is not expecting a challenge and fail, and this quickly hits rate limits.

Is there a reason that two instances cannot share certs via redis?

@gjongenelen
Copy link
Contributor

Yes. You can host multiple openresty instances on one redis instance/cluster. That’s kinda the whole purpose of the redis backend.

@luishscosta
Copy link

Hi! @gjongenelen

Can I configure different accounts in these instances?

@gjongenelen
Copy link
Contributor

You don’t configure an account on your instance. I think you mean the email-address being used while requesting certificates. In that case: no, AFAIK you can only set 1 mail-address per instance. You could set different emails on different instances (don’t know why you would want this) but the certificates will be registered with the email configured on the requesting instance.
https://github.com/auto-ssl/lua-resty-auto-ssl#advanced-lets-encrypt-configuration

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants