On 2026-01-10, Vagrant Cascadian wrote: > On 2026-01-10, Ludovic Courtès wrote: >> Vagrant Cascadian <[email protected]> skribis: >> >>> (service guix-publish-service-type >>> (guix-publish-configuration >>> (host "0.0.0.0") >>> (port 8086))) ... >> To listen on IPv6 only, any interface, you need (host "::"). > > Surprisingly, that worked! And then setting it to the IPv6 address of > the yggdrasil interface also worked. I *thought* I had tried both of > those before, but something *else* must have been wrong too that I > eventually resolved... ... >>> If I use a hostname that resolves to the ipv6 address ... it works, >>> under very specific conditions... after reconfiguring the system, and >>> then "herd restart guix-publish" (or sometimes only "herd stop >>> guix-publish && herd start guix-publish" !!!). Similar story for just >>> specifying the ipv6 address. But after rebooting it no longer listens on >>> the yggdrasil ipv6 address, and only works by reconfiguring the system >>> *and* restarting guix-publish... every. single. boot. > > Apparently using a global IPv6 "::" or a specific IPv6 > address... actually does resolve this, yay!
The plot thickens...
Apparently both ("::" or a specific IPv6 address) work fine on my
machine using dhcpcd-service-type, but my machine using
network-manager-service-type, it only seems to work with (host "::") at
boot. Though at least I can restart it with a specified IPv6 address and
then it seems to work fine...
Unless there is a race condition or similar and I just got "lucky"? :)
> Might it work with an IP address range?
Or a list of IP addresses?
>>> I have not yet figured out how to make sure guix-publish only starts
>>> after the yggdrasil service starts (and/or name resolution is
>>> available?), but in theory that *might* resolve the issue...
This might still be helpful, if it is at all possible, if only to debug
the issue further...
So, improvements for sure, but still some curious quirks!
live well,
vagrant
signature.asc
Description: PGP signature
