The current release of boringproxy uses an old version of the protocol for talking to TakingNames and it’s not compatible.
I probably won’t update it since I think very few people use this feature. I’m close to releasing the beta for my successor project to boringproxy, and that project will have full support for TakingNames.
For now you’ll need to set up your domain manually.
Built on a simple, open API. Other developers should be able to make their own tools to integrate. Look at how many tools work with SSH. I’m trying to do a similar but with some new features below
Works natively in web browsers since it’s based on WebTransport (with WebSocket fallback). This is impossible with boringproxy because it uses SSH.
Much better auth. OIDC and OAuth2 from the ground up, which results in much better UX than copying keys.
Better performance. Using WebTransport enables low-overhead UDP tunneling. Any UDP tunneling over TCP isn’t going to be great.