[01:20:16]
<wivodaim> 😀 boujour
[06:59:28]
<doesnm> i know only two words (well maybe three in french) 👀
[06:59:30]
<doesnm> bonjour, merci and comment
[06:59:32]
<tituspijean> Welcome! Do not mind the french frenching, this room is bilingual :)
[08:49:09]
<selfhoster1312> hello is it expected that yunohost rotates the DKIM key without a special warning to update the DNS TXT records? i just found out about it reading the `Issues found by automatic diagnosis` daily mail, but i usually don't read them because it's so full of "false-positives" (intended changes)
[09:39:58]
<selfhoster1312> and i've just lost SSH access, joke's on me for force-regen ssh config to remove that pesky warning of custom modified file :D
(yes my user has SSH/SFTP groups and has a public key setup in ~/.ssh/authorized_keys)
[09:43:12]
<selfhoster1312> and both wetty/httpsh prevent me from logging in because apparently they're doing ssh auth? (looks like it but they clear the error message almost instantly so it's hard to say)
[09:49:00]
<selfhoster1312> (apparently according to my emails DKIM update is from september 16th)
[09:52:06]
<fabulousfabs> I had it recently, I think it was from a migration step, did you run some migrations ? it was a change in size of DKIM keys, in many years with YNH it is the first time it happened to me, so I guess it won’t happen often.
[11:52:03]
<miro5001> > <selfhoster1312> (apparently according to my emails DKIM update is from september 16th)
This is related to dkim migration. Apparently you didn't read the notice of the migration.
Check migrations logs
[12:42:04]
<selfhoster1312> maybe some other admin did that indeed :-)
unfortunately i can't check the migration logs now because in the webui in migrations it appears but it's not a link to the logs, and in the logs only the last 20 or so entries are displayed (i know the CLI can do it, but until i get back close to the machine i don't have SSH so this will wait :D)
[12:43:41]
<selfhoster1312> my two cents: this is a highly modifying/destructive operation so next time we may want a separate email that's more easily spotted by the admins, and maybe having *wrong* DKIM keys (not having *no* keys) could use a higher level of reporting than being lost in the sea of diagnosis
[15:36:13]
<fabulousfabs> I wonder why you’re working on `coolwsd.xml` (collaboraonline config) if your original problem was with nextcloud-signalling ^^ but glad you got to a point you’re satisfied with
[15:36:14]
<mrjive> ahah you are right! I solved the troubles with signalling and had some more with collabora online... the stress led to the confusion!
[15:37:47]
<mrjive> hello everyone! I'm happily using unohost and I have installed nextcloud, coturn, nextcloud-signalling (plus aother software for testing). The only trouble I have is with <del>nextcloud-signaling</del>collabora online (coolwsd).
Inserting more than one website leads to errors e I have to reinstall everything to make it work again... any experince with this issue?
[15:57:03]
<selfhoster1312> vu sur liberachat #yunohost : https://demo.yunohost.org/ le certificat a expiré :-)
[20:00:54]
<fabulousfabs> as long as everything works as expected, it really doesn’t matter ^^
[20:00:59]
<tituspijean> fixed!
[20:05:59]
<selfhoster1312> ❤️
[21:49:30]
<Moté> selfhoster1312: there is a warning *before* launching the migration, and it's so rare I don't see why an admin wouldn't read them. Also, if you have a lot of warnings from your diagnosis, you should mark the unrelevant warnings as ignored so that you can still follow what happens. Or you could also use custome hooks so that yunohost generates your conf as you want it, but it's obviously more work.
[21:50:49]
<khrys_> Je sors d'une présentation de Reticulum et maintenant je rêve d'avoir une app NomadNet sur Yunohost ;-P