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

[ENHANCEMENTS] - Enable the ability to specify a certificate manually per service. #266

Closed
freedbygrace opened this issue Jul 24, 2024 · 1 comment
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@freedbygrace
Copy link

Right now, I have no idea how to make a wildcard certificate be the certificate used for a proxy entry.

The ACME integration should be smoother and more concise. Also, it should be configurable after the proxy entry has been created.

I really like this software! I am actually in process of migrating away from my current reverse proxy.

@freedbygrace freedbygrace added the enhancement New feature or request label Jul 24, 2024
@tobychui
Copy link
Owner

Hi @freedbygrace

Seems you are coming from nginx proxy manager. In Zoraxy, we do that automatically. You do not need to specify / assign a certificate manually to a hostname. As soon as you have a wildcard certificate in the certificate storage, Zoraxy will pick the suitable one for you based on the host name your downstream clients are requesting.

Just go to the ACME snippet, generate a wildcard certificate using DNS challenge and after it is done and show up in the list, it is ready to use (will automatically assign to proxy rules that matches the wildcard)

@tobychui tobychui added the good first issue Good for newcomers label Jul 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants