Build problems

[janpekar]

Hi,
when I'm building with debian buster go, build fails.

build go.txtdirect.org/txtdirect/cmd/txtdirect: cannot find module for path crypto/ed25519
make: *** [Makefile:16: build] Error 1
go version
go version go1.11.6 linux/amd64

I tried building with debian bullseye (because crypto/ed25519 was added in newer go versions), I can build it but executing binary fails with

./txtdirect
panic: qtls.ClientSessionState not compatible with tls.ClientSessionState

goroutine 1 [running]:
github.com/lucas-clemente/quic-go/internal/handshake.init.2()
        /root/go/pkg/mod/github.com/lucas-clemente/quic-go@v0.17.1/internal/handshake/unsafe.go:26 +0x205

Maybe update dependency to quic-go@v0.18 can fix problem? libp2p/go-libp2p-quic-transport#171

[janpekar]

I tried to build master with make docker-build
It creates txtdirect binary, but when I try to run it, it behaves differently, than downloaded txtdirect binary from releases.
It looks like that caddy server changed a lot.
When I use Caddyfile and place into it previously working txtdirect configuration, I get

run: adapting config using caddyfile: directive 'txtdirect' is not ordered, so it cannot be used here

So it don't knows txtdirect directives?

I can switch to tag v0.5.1 and it builds as expected, but I think, that caddy is old, and don't implements on_demand_tls, which I want to use, am I right?

Or is there anybody, that is using on_demand_tls with txtdirect now and can help me with that?

[erbesharat]

Hi there,

Currently master branch is in a non-production status because of the migration to Caddy v2 and changes to TXTDirect's spec. But I would definitely take a look at your reported issue this week and will update master so you can use TXTDirect alongside new caddy features.

Just note that because of some edge case issues with the path type which you can also read more about in its related issues, we have decided to take a different approach in implementing it in the new version so if you're planning to use any of the older features and they're not available on master, just let us know about it and we'll discuss that how it can be added in the next version or maybe reverting the old code might be a better option in some cases.

Thanks a lot for your help and time in making TXTDirect better.

[janpekar]

Thank you. I solved it for now running Caddy v2 with on_demand_ssl as reverse-proxy on 443 port (https) and txtdirect 0.5.1 on 80 (http) and that is what I needed.

[stp-ip]

Glad it worked out and thanks @erbesharat for jumping in.
Thank you for reporting and happy for any contributions in the long run, we are eager to get back into developing as well.