<!--
Thank you for doing recipe maintenance work!
Please mark all checklist items which are relevant for your changes.
Please remove the checklist items which are not relevant for your changes.
Feel free to remove this comment.
-->
* [x] I have deployed and tested my changes
* [x] I have [updated relevant versions in `abra.sh`](https://docs.coopcloud.tech/maintainers/upgrade/#updating-versions-in-the-abrash)
* [x] I have made my environment variable changes [backwards compatible](https://docs.coopcloud.tech/maintainers/upgrade/#backwards-compatible-environment-variable-changes)
* [x] I have added a [release note entry](https://docs.coopcloud.tech/maintainers/upgrade/#creating-new-release-notes)
Thanks a lot @moritz !
The change looks solid to me, before approving and merging though, can you explain the problem we are solving here? was VW using an ipv6 address for smtp submission and your system/network didn't support that or am I misunderstanding?
Thanks a lot @moritz !
The change looks solid to me, before approving and merging though, can you explain the problem we are solving here? was VW using an ipv6 address for smtp submission and your system/network didn't support that or am I misunderstanding?
Yes that was the issue. Because of a change in 1.36.0, vaultwarden uses ipv6 for smtp connections per default. And as docker don't support ipv6 per default, it broke our smtp configuration. Is it still working for you? Do you have some special configuration so docker supports IPv6?
Yes that was the issue. Because of a change in 1.36.0, vaultwarden uses ipv6 for smtp connections per default. And as docker don't support ipv6 per default, it broke our smtp configuration. Is it still working for you? Do you have some special configuration so docker supports IPv6?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
abra.sh@@ -8,2 +8,4 @@- proxy- internalsysctls:- net.ipv6.conf.all.disable_ipv6=${DISABLE_IPV6:-1}does this mean ipv6 is disabled by default?
ah yes it does https://docs.kernel.org/networking/ip-sysctl.html
Thanks a lot @moritz !
The change looks solid to me, before approving and merging though, can you explain the problem we are solving here? was VW using an ipv6 address for smtp submission and your system/network didn't support that or am I misunderstanding?
3d6539c45ato1309c81d32Yes that was the issue. Because of a change in 1.36.0, vaultwarden uses ipv6 for smtp connections per default. And as docker don't support ipv6 per default, it broke our smtp configuration. Is it still working for you? Do you have some special configuration so docker supports IPv6?
it is still working for me but that's probably because my email server doesn't have an ipv6 address (it's a mailu recipe hosted on the same swarm box)