Saturday, January 21, 2023
support@conference.yunohost.org
January
Mon Tue Wed Thu Fri Sat Sun
            1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
         

[00:56:26] <ast3risk> > <@DerpFox:libera.chat> Hello

hello
[07:11:21] <gymn> hi anyone?
[07:11:36] <gymn> What's a good XMPP client for mac guys? All the ones I've tried seem a bit unstable
[09:15:15] <anubis> hi gymn, I think Beagle is the best one : https://beagle.im/
[09:25:15] <naos> Hi, upgrade gitea from 1.17.2~ynh2 to 1.17.4~ynh1 : https://paste.yunohost.org/raw/iwihenoreb
[09:25:32] <naos> may have sth to do with using a non-standard port for ssh...
[09:49:00] <naos> nevermind, found a solution: having "Port 22739\n#Port 22" in /etc/ssh/sshd_config caused the issue. Removing the (commented) "#Port 22" solved it
[15:37:49] <daniel> I also used another port for SSH, to prevent all those bots trying to log in. It worked for some time, but then they found the new port.
[15:39:06] <daniel> I did something else now: I use port 22 again, but blocked it on ipv4, so it can only be reached via ipv6. No more bot login attempts since then.
[17:48:44] <davide.mainardi> Hello
[17:51:07] <davide.mainardi> I tried to upgrade Redmine from 4.2.7~ynh1 to 5.0.4~ynh1 but something went wrong: https://paste.yunohost.org/raw/emeyefadir
[17:56:52] <Aleks (he/him/il/lui)> hmyeah

```
2023-01-21 18:33:28,869: DEBUG - + bundle exec rake db:migrate RAILS_ENV=production
2023-01-21 18:33:33,233: DEBUG - rake aborted!
2023-01-21 18:33:33,238: DEBUG - LoadError: cannot load such file -- open_id_authentication
```
[17:56:59] <Aleks (he/him/il/lui)> not clear what the issue is, i'm not familiar enough with ruby
[17:58:12] <davide.mainardi> Thanks Aleks
[17:58:37] <davide.mainardi> I am writing the same message into the forum
[17:58:46] <davide.mainardi> I am not familiar with ruby too...
[17:58:54] <davide.mainardi> Do you use Redmine?
[18:41:06] <dustinwidmann> 1) I can't seem to get nginx http basic authentication to work anymore, it used to, but stopped working recently... 2) There seems to be a distributed effort to get into my server going on at the momentk never really had to deal with something like this before, and while I don't think they'll succeed, does anybody have any advice?
[18:44:10] <Aleks (he/him/il/lui)> 1) check the anouncement on the forum ; 2) can you be more specific
[18:51:56] <dustinwidmann> I'll take a look at the forum, one second... As per being more specific, here's a snippet of my log https://pastebin.com/08DnMJWN has been going on for a while
[18:53:55] <Aleks (he/him/il/lui)> yeah this is "excepted", if you want to reduce those you can try changing the ssh port
[18:56:19] <Aleks (he/him/il/lui)> naively i'd say "let's increase the number of workers to 5" (because we really have a lot of margin on the RAM available), this is a quickwin
[18:57:20] <Aleks (he/him/il/lui)> and disabling the probably-useless-in-99%-of-cases services such as rspamd, dovecot, maybe nginx workers, (in the CI context) shouldnt be too hard
[18:57:48] <Aleks (he/him/il/lui)> uh wrong channel
[19:04:53] <Karl (AT)> Has anybody found a workaround for sogo/activesync not working when setup on Yunohost?
[19:11:03] <dustinwidmann> Hmm, I assume the forum announcement you're talking about is this one? https://forum.yunohost.org/t/authentication-issues-with-yunohost-11-1-0-with-new-ssowat-version-please-upgrade-to-yunohost-11-1-2-to-fix/23059/30 Unfortunately, I tried that and it didn't help. Auth is still broken.
[19:12:21] <Karl (AT)> I run into this one https://github.com/YunoHost-Apps/sogo_ynh/issues/7
[23:26:55] <samyuno> ola