Can anyone confirm that Boundary v0.4.x or 0.5.x actually work on OpenBSD-6.9 amd64, using the binaries from releases.hashicorp.com, e.g.
for ex. /boundary/0.5.1/boundary_0.5.1_openbsd_amd64.zip?
I have a reference installation of Boundary v0.4.0 that works perfectly well on FreeBSD 12.1 amd64 (actually OPNsense/HardenedBSD) which uses PostgreSQL 12.
After moving and adapting the Boundary configurations from that FreeBSD setup to OpenBSD-6.9, and dumping its PostgreSQL 12 database and restoring it to PostgreSQL 13 on OpenBSD, the Boundary Controller appears to startup fine, without showing any errors in the event logs.
Also, it answers TCP connects from Web browsers to its WebUI at port 9200 with Syn/Ack, but never serves Boundary’s login page. Unfortunately, I can not get any logs from Boundary yet in order to figure out whats wrong.
Of course, CORS is a prime suspect, but I have checked various settings, among them the tried and tested one from the working FreeBSD setup.
Further, I have rendered the new PostgreSQL 13 database on OpenBSD accessible to the working Boundary Controller on FreeBSD 12, and that works fine too. So this indicates that Boundary on FreeBSD works well using the new PostgreSQL 13 database on OpenBSD.
Vice-versa, I have also tested Boundary Controller on OpenBSD giving it access to the known-good Postgres 12 database on FreeBSD. From looking at tcpdump on port 5432/tcp, Boundary appears to access Postgresql fine, but produces still no HMTL output on its WebUI at port 9200/tcp.
Migrating from Boundary 0.4.0 to 0.5.0 and now 0.5.1, as well as re-initialisation of Postgresql & Boundary databases did not help on OpenBSD either.
Comparing the file sizes of the binaries for FreeBSD and OpenBSD of Boundary, it looks as if the code necessary for the WebUI is indeed included in the OpenBSD binary as well.
Also, I have not found any indication that the WebUI must be enabled, unlike in Consul or Vault for example.
Thank you for any hints and clue sticks!