[10:52:40]
<Charles P.> > <@Alekswag:matrix.org> i can't see exactly what you are talking about if you don't share the exact diagnosis message you are reffering to
diagnosis outputs an error if wildcard is not set, even if all domains served by yunohost have a A or a CNAME record
[10:55:18]
<Charles P.> i think <a href="https://matrix.to/#/@chrichri:librem.one">ChriChri @chrichri:librem.one</a> meant that it would be better to check if DNS resolving for every domain is correct instead of testing every recommended record (because one may not use the recomended setup, for exemple using CNAME instead of A, it still works but outputs an error in diagnosis because that's not the recommended way of doing it according to Ynh)
[10:55:34]
<Charles P.> i think @chrichri:librem.one meant that it would be better to check if DNS resolving for every domain is correct instead of testing every recommended record (because one may not use the recomended setup, for exemple using CNAME instead of A, it still works but outputs an error in diagnosis because that's not the recommended way of doing it according to Ynh)
[10:55:50]
<Charles P.> i think ChriChri @chrichri:librem.one: meant that it would be better to check if DNS resolving for every domain is correct instead of testing every recommended record (because one may not use the recomended setup, for exemple using CNAME instead of A, it still works but outputs an error in diagnosis because that's not the recommended way of doing it according to Ynh)
[10:56:07]
<Charles P.> i think ChriChri @chrihri:librem.one that it would be better to check if DNS resolving for every domain is correct instead of testing every recommended record (because one may not use the recomended setup, for exemple using CNAME instead of A, it still works but outputs an error in diagnosis because that's not the recommended way of doing it according to Ynh)
[10:56:48]
<Charles P.> i think ChriChri @chrichri:librem.one meant that it would be better to check if DNS resolving for every domain is correct instead of testing every recommended record (because one may not use the recomended setup, for exemple using CNAME instead of A, it still works but outputs an error in diagnosis because that's not the recommended way of doing it according to Ynh)
[11:17:35]
<bibanez> Hi! This is weird, I flashed the latest 64bit image for yunohost using balenaEtcher (also tried dd) and it isn't recognized as a boot option
[11:17:55]
<bibanez> I've installed OSes many times. How can I debug this?
[11:29:52]
<Aleks (he/him/il/lui)> > <@charlesp:stratus.family> i think ChriChri @chrichri:librem.one meant that it would be better to check if DNS resolving for every domain is correct instead of testing every recommended record (because one may not use the recomended setup, for exemple using CNAME instead of A, it still works but outputs an error in diagnosis because that's not the recommended way of doing it according to Ynh)
Im pretty sure the case 'using a CNAME instead of A' is handled, hence asking for the exact message.. There are two overlapping topics here, but im pretty sure using CNAME or A record is irrelevant
[12:21:32]
<ChriChri[m]> > <@Alekswag:matrix.org> Im pretty sure the case 'using a CNAME instead of A' is handled, hence asking for the exact message.. There are two overlapping topics here, but im pretty sure using CNAME or A record is irrelevant
I'm still looking at it - sorry, didn't find time before.
[12:51:05]
<Charles P.> > <@bibanez:matrix.org> Hi! This is weird, I flashed the latest 64bit image for yunohost using balenaEtcher (also tried dd) and it isn't recognized as a boot option
You can also install Debian (Raspberry Pi OS on Raspberry Pi) and manually run `curl https://install.yunohost.org/ | bash` then follow instructions
[12:51:33]
<Charles P.> I can't help debugging images but if Debian works, then you're good
[12:59:24]
<ChriChri[m]> > <@Alekswag:matrix.org> Im pretty sure the case 'using a CNAME instead of A' is handled, hence asking for the exact message.. There are two overlapping topics here, but im pretty sure using CNAME or A record is irrelevant
Got that one. Really has been a DNS error 😁 .
The only one I can only ignore is
```
Type: MX
Name: @
Current value: ['10 link-goe.de.', '20 arcanum.ween.de.']
Expected value: 10 link-goe.de.
```
I have a second MX for sending out from an official, not burned IP and that needs to be in the MX to be fully accepted by some hosts.
[14:21:13]
<miraille> https://aria.im/_matrix/media/v1/download/matrix.org/krQxvFdpNwwSwStKMygwdgpz
[14:21:17]
<miraille> Bonjour, impossible d'utiliser l'application Headphones que yunohost propose, car impossible de modifier le fichier `/etc/headphones/headphones.ini` d'après les logs Headphones
[14:25:21]
<@err404:matrix.org> I dont know what was the first message, but the second was in french and was not offending (from miraille), can some admin check and eventually unban miraille please?
[20:37:58]
<Paprika> Hello, upgrading Synapse from 1.94.0 to 1.96.1 on Yunohost 11.2.6 seems to fail with the following error:
```
/usr/share/yunohost/helpers.d/fail2ban: line 106: logpath: unbound variable
```
Anyone faced the issue before?
[20:39:17]
<Paprika> Hello, upgrading Synapse from 1.94.0 to 1.96.1 on Yunohost 11.2.6 seems to fail with the following error:
```
/usr/share/yunohost/helpers.d/fail2ban: line 106: logpath: unbound variable
```
Anyone faced the issue before?
Seems to crash fail2ban in the process as well.
[20:52:00]
<Tag> > <@botagiuks:tiesiog.lt> Hello, upgrading Synapse from 1.94.0 to 1.96.1 on Yunohost 11.2.6 seems to fail with the following warning and errors:
>
> ```
> /usr/share/yunohost/helpers.d/fail2ban: line 106: logpath: unbound variable
> Could not upgrade synapse: An error occurred inside the app upgrade script
> Could not upgrade synapse: This action seems to have broken these important services: fail2ban (failed)
> ```
>
> Anyone faced the issue before?
> Seems to crash fail2ban in the process as well.
I think there's work in progress on a fix for this bug https://github.com/YunoHost/yunohost/pull/1743
[21:12:28]
<ben> And then the restore failed because of password length/complexity. Had to reduce Yunohost setting to 8 characters for password.
[21:14:32]
<ben> And after fail2ban failed to start. Paprika did it start again in your case?
In my case the homeserver.log was missing in /var/log/matrix-synapse/ as it was required by fail2ban.
[22:14:24]
<@err404:matrix.numericore.com> I had the same issue, it is required to restart fail2ban after triying to upgrade synapse