Zilonis

Yes, sorry.

No issues after 24 hours of heavy network traffic using the most recent update on the "latest" tag. 127.1.1.1#5153, 127.2.2.2#5253, and cache are all working as expected. Thank you for all of your work on this.

I assume they haven't updated the servers config UI since initially adding Valheim support to AMP. There's a lot of game-specific settings missing that you can find in the config files. What's odd is other .kvp files aren't overwritten. I changed "SFTP.SFTPEnabled" in "FileManagerPlugin.kvp" to "False" to disable SFTP and that sticks after an instance update. I haven't seen a UI option for that either.

I just updated and 127.1.1.1#5153 looks like it's working on "latest" with no errors. I'll keep an eye on it though. https://1.1.1.1/help is also showing I'm using DoH.

This may be specific to AMP, and not the docker, but is there a way to prevent an instance from overwriting its .kvp files on update? Specifically the "GenericModule.kvp" file is overwritten with a generic version. For context I changed the "WakeupMode" value to "OnUDPPacket" so the Steam query port doesn't prevent my Valheim server from sleeping. If I stop the server, update this value, then start the server it sticks. If the instance is updated e.g., when the game updates, it wipes it out.

@ZappyZap both "latest" and "beta". I provided more information in my reply just before you replied.

Sorry, to clarify on the "latest" docker release if the Pihole tries to use "127.1.1.1#5135" as its DNS server for DoH it will endless throw this error. I assume it's because Cloudflare removed the "proxy-dns" command which would explain why it works on the docker "beta" release that uses "dnscrypt-proxy" instead. For the same error with "127.2.2.2#5335" that looks like user error. The docker overview when editing it or installing says this: Following those instructions I set the second DNS server to "127.2.2.2#5335", but it looks like it should actually be "127.2.2.2#5235" if I take the value from "stubby.yml". I don't know if the overview needs to be updated to show the correct port for the DoT DNS server.

I see what I did wrong for the errors being returned by "127.2.2.2#5335". The overview/description when editing the docker says "you must set FTLCONF_dns_upstreams variables to 127.1.1.1#5153 (DoH) and/or 127.2.2.2#5335 (DoT)", but looking at "stubby.yml" it should be "127.2.2.2#5253" for DoT. The issue still stands with "127.1.1.1"5153".

Thank you for your continued work on this ZappyZap. I noticed with the "latest" release both "127.1.1.1#5153" and "127.2.2.2#5335" are returning the following error: WARNING Connection error (127.2.2.2#5335): TCP connection failed (Connection refused) The issue seems to be specific to these unbound addresses, and only on the "latest" release. If I switch to a different DNS server like "1.1.1.1" or "8.8.8.8" on "latest" it works as expected. The same is true if I stay on "127.1.1.1#5153" or "127.2.2.2#5335" on the "beta" release. I assume "127.1.1.1#5153" fails on "latest" because Cloudflare removed the "proxy-dns" command, but I'm not sure about "127.2.2.2#5335".