github avandeputte/haproxy-manager v2.4.0-beta.5
2.4.0-beta.5: fixes from a review of the beta

pre-release49 minutes ago

2.4.0-beta.5: ten fixes from a review of the 2.4 beta

A beta of 2.4.0 with no new features: the fixes from a code review of everything the earlier betas added. If you are trying the Cloudflare or gRPC features, update to this one.

Getting the beta

  • Updates page: tick Also offer beta versions, then update.
  • Docker: ghcr.io/avandeputte/haproxy-manager:2.4.0-beta.5
  • install.sh: the usual command with --ref beta.

Cloudflare Tunnel

  • A tunnel that is already in use is no longer taken over. Giving the name of an existing tunnel used to join it, and the next Apply replaced its routes and removed its DNS records. A tunnel of that name is now used only while it has no routes and no connector; otherwise it is refused, by name.
  • Routes added to the tunnel by hand are kept, and so are their DNS records.
  • Publishing one path of a host no longer publishes the rest of the host. The tunnel routes by host name, so an unpublished service on another path of the same host was reachable through it, with no sign-in. A service that is not published now refuses whatever comes down the tunnel.
  • An Access application for a service on a path is removed again when the service is unticked. It used to be left in the account.
  • "Delete it in Cloudflare, then Apply again" now works. After such a warning the next Apply asked nothing of Cloudflare; it now asks again until the matter is settled.
  • Clusters: what Cloudflare was last told is kept in the shared configuration, not in a file on one node. A node that takes over no longer skips a change, and passive nodes no longer show Cloudflare is behind for good.
  • Disconnect switches Cloudflare off and applies first, so the connectors on every node stop before the tunnel is deleted. It copes with a tunnel that was already deleted in the dashboard, and when Cloudflare will not answer it offers to forget the tunnel on this installation.

gRPC and long-lived streams

  • The AppSec exemption follows the service that takes the request. With a second service on a path of a gRPC service's host, a request for that path could skip body inspection by claiming to be gRPC. It no longer can.
  • The per-service client timeout follows it too, and a listener's default pool is covered.
  • HTTP/2 to the servers belongs to the service. It was kept on the servers, and two services with the same target share a server, so ticking it on one changed the other. It is now kept on the service's pool. A tick made in an earlier beta still holds, and the form moves it over when the service is next saved.
  • A health check on a separate check port of a plain-HTTP gRPC server is spoken HTTP/1.1 to. It was spoken HTTP/2 to, and the server was marked down.

Tested

Against a real Cloudflare account on the container image: an in-use tunnel refused; an unpublished path answering 403 through the tunnel while a published one answered; a path with a sign-in redirecting to Access and its application removed when unticked; a route added by hand kept; Disconnect removing everything it made. With a real AppSec and a real gRPC server: a body attack on a path of the gRPC host refused even when it claimed to be gRPC, and the streams still open. The check-port fix on HAProxy 3.0.

Not tried: a real cluster with a virtual IP, RPM systems, wildcard host names, NetBird itself.

Don't miss a new haproxy-manager release

NewReleases is sending notifications on new releases.