Beta. Only nodes with Also offer beta versions ticked (Settings → Updates) are offered this.
One service on several ports
A service's public URLs can now use different ports. Enter
https://service.mydomain.com
https://service.mydomain.com:3456
and the service gets a listener on 443 and one on 3456. The two listeners share one rule, one pool and one certificate. It is listed once on the Services page and the Overview, with both URLs, and you edit, pause or remove it as one thing (#14).
- Every name on a service answers on every one of its ports. If the URLs leave a combination out, the form says so, and the Services page lists everything that is served.
- Editing a service and removing one port's URLs takes the service off that port.
- A port already used by a different kind of listener (raw TCP, or the other of http and https) is refused instead of being bound twice.
- Fixed: a service attached to two listeners used to appear twice on the Services page, and pausing or deleting either entry acted on both.
A host name matches on any port
On a port other than 80 or 443, browsers send the port as part of the host name (service.mydomain.com:3456). The "host matches" condition compared that exactly, so a service published on any other port answered 503 to everyone. Host matches and host ends with now ignore the port. Host starts with was not affected. If you switched a condition to host starts with to work around this, you can switch it back.
After upgrading
Press Apply once. The corrected rule reaches haproxy.cfg only on an Apply, and an Apply on the active node also updates the other nodes.
Image: ghcr.io/avandeputte/haproxy-manager:1.100.0-beta.1