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.

Sign up for GitHub

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

Jump to bottom

net/haproxy + acme/letsencrypt: Issue with more than one reverse proxy destinations #1124

Closed
4lexk opened this issue Jan 9, 2019 · 4 comments
Closed

net/haproxy + acme/letsencrypt: Issue with more than one reverse proxy destinations #1124

4lexk opened this issue Jan 9, 2019 · 4 comments
Assignees
@fraenki
Labels
support Community support

Comments

@4lexk
Copy link

4lexk commented Jan 9, 2019

I have configured two servers, services, pools and rules and provided Let's Encrypt certs to them.
Now it looks like the last provisioned service is working and the one before is getting assigned the certificate from the last provisioned one... (the configuration still showing correct cert assignments)

Right now I'm on 18.7.10 but tested the same behavior with 18.7.9
@4lexk 4lexk changed the title net/harproxy + acme/letsencrypt: Issue with more than one reverse proxy destinations net/haproxy + acme/letsencrypt: Issue with more than one reverse proxy destinations Jan 9, 2019
@fraenki
Copy link
Member

fraenki commented Jan 10, 2019

@4lexk Could you possibly paste your /usr/local/etc/haproxy.conf? :)

@4lexk
Copy link
Author

4lexk commented Jan 10, 2019

sure, please find attached
haproxy.conf.txt

@4lexk
Copy link
Author

4lexk commented Jan 11, 2019

@fraenki any news on this?

@4lexk
Copy link
Author

4lexk commented Jan 19, 2019

I think the issue was to have more than one frontend for the same IP:PORT - I had to use one frontend/service with multiple backends on the same IP:PORT

@4lexk 4lexk closed this as completed Jan 19, 2019
@fichtner fichtner added the support Community support label Jan 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@fraenki fraenki

Labels
support Community support
Milestone
No milestone
Development

No branches or pull requests
3 participants
@fraenki @fichtner @4lexk