Tcp 127.0.0.1:2019: bind: address already in use

Thanks. So it seems that your system won’t let you bind two sockets to 0.0.0.0:2019 and 127.0.0.1:2019 – it’s possible that internally it reads 0.0.0.0 as the loopback interface for IPv4, which is 127.0.0.1, which is probably configurable on the system, but to be honest I would not know without some searching. I’d look into that first; but the good news is it’s not a Caddy problem so it’s something that you can fix on your end!

2 Likes