Just experimenting with ipv6 network stack. While core web seems fine, it does seem to break a lot of things.
Surprisingly, seems like duplicati web interface is one of those. Any particular reason (other than no real users) for this? It serves up as a regular webpage right? Should be fairly underlying ip4/6 agnostic?
Looks like Duplicati only binds to IPv4 addresses:
I tried doing something really quick and dirty:
if (interfacestring.Trim() == "*" || interfacestring.Trim().Equals("any", StringComparison.OrdinalIgnoreCase) || interfacestring.Trim().Equals("all", StringComparison.OrdinalIgnoreCase))
listenInterface = System.Net.IPAddress.IPv6Any;
else if (interfacestring.Trim() == "loopback")
listenInterface = System.Net.IPAddress.IPv6Loopback;
Supposedly specifying IPv6 here will support both IPv4 and IPv6 stacks simultaneously. But it didn’t work. Will need to do more testing…
No real users? I’d like to object. 
I’m a first-time Duplicati user. Just installed it (as a service) on a Windows server (2012 R2). The server’s management interface is IPv6-only. Remote access to the Duplicati Web interface doesn’t work at all. (I’ve enabled remote access and added the hostname in the settings.) Local access only works when using localhost or 127.0.0.1, but not when using the server’s FQDN (resolves to an IPv6 address) or any of its IPv6 addresses (::1, link-local, GUA, ULA).
Searching for a solution brought me here. What’s the next step? Open an issue on GitHub?
Cheers
Maurice
Yes… If you have time please do so. Thanks!
Done.