You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Could this be modified (or it's already available) to mirror traffic to multiple servers?
The use case I would like to implement is in an scenario where I've got only one public IP but multiple servers not at default 80/443 port (of course) but want to get them to request and renew letsencrypt certificates. Letsencrypt default certbot renewal method only allows for default ports and executes a get to /.well-know... path to validate dns ownership.
So, if this mirror spoa could mirror this letsencrypt path to all the backend servers I will be able to request and renew them all, as only one of them will reply to the request when doing validation (it's then when the /.well-known.. server path will be available.
Just guessing if possible.
The text was updated successfully, but these errors were encountered:
of course, it is possible to mirror to several different URLs. In order for it to work, it is necessary to add as many SPOE mirror filters in the HAProxy configuration as we want different URLs for the mirror. Of course, this means that each mirror filter communicates with its spoa-mirror program (in the example below, there are two of them).
For example, something like this should be written in haproxy.cfg:
Could this be modified (or it's already available) to mirror traffic to multiple servers?
The use case I would like to implement is in an scenario where I've got only one public IP but multiple servers not at default 80/443 port (of course) but want to get them to request and renew letsencrypt certificates. Letsencrypt default certbot renewal method only allows for default ports and executes a get to /.well-know... path to validate dns ownership.
So, if this mirror spoa could mirror this letsencrypt path to all the backend servers I will be able to request and renew them all, as only one of them will reply to the request when doing validation (it's then when the /.well-known.. server path will be available.
Just guessing if possible.
The text was updated successfully, but these errors were encountered: