Wednesday, July 31, 2024
support@conference.yunohost.org
July
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
       
             

[08:08:28] <Salamandar> hi, you can manually edit the nginx configuration files
[08:08:41] <Salamandar> this is not (yet) possible, although that's a feature some users want
[08:30:45] <phinero> https://aria.im/_matrix/media/v1/download/matrix.org/BysAcZtliNxRlxODmQQlByEa
[08:31:12] <phinero> This error is still present.
how to fix it?
[08:32:06] <phinero> This error is still present.
how to fix it?
The server is in Cloudflare zone
[08:32:38] <phinero> https://aria.im/_matrix/media/v1/download/matrix.org/IGTDCHwfZJUqDnECgaNKLmOZ
[08:33:49] <phinero> This error is still present.
how to fix it?
The server is in Cloudflare zone
The only working commands is:
`apt dist-upgrade`
[08:34:03] <phinero> This error is still present.
how to fix it?
The server is in Cloudflare zone
The only working command is:
`apt dist-upgrade`
[10:24:08] <tufek> > <@phinero:matrix.org> sent an image.

I can't tell if it's a good idea since I don't really know what packages.sury.org are about, but technically you should be able to bypass this allert with `--allow-unauthenticated` option to apt (e.g., `sudo apt --allow-unauthenticated update`) to definitively get rid of it you can create a file in your /etc/apt/apt.conf.d/ directory containing `APT::Get::AllowUnauthenticated "true";`
[10:25:26] <tufek> at your own risks because these operations deactivate signature verifications so one would rather know why this repo is no longer signed?
[11:01:06] <phinero> > <@tufek:matrix.fdn.fr> I can't tell if it's a good idea since I don't really know what packages.sury.org are about, but technically you should be able to bypass this allert with `--allow-unauthenticated` option to apt (e.g., `sudo apt --allow-unauthenticated update`) to definitively get rid of it you can create a file in your /etc/apt/apt.conf.d/ directory containing `APT::Get::AllowUnauthenticated "true";`

Thank you. I think it's because of Cloudflare. Two other servers (not in the Cloudflare zone) don't have this issue
[11:42:24] <tituspijean> I see error 451, for "Unavailable For Legal Reasons" in your first screenshot... which seems very weird. :/
[11:52:02] <chrichri ⚡> Hey everybody, I'm trying to change an alias entry in slapd using phpldapadmin and it returns me an error saying that I'd do not have sufficient rights to do that (logged in as member of the admin group). Found a [forum post](https://forum.yunohost.org/t/problems-connecting-to-yunohosts-ldap-database-the-user-cn-admin-no-longer-exists-in-the-new-version-of-yunohost/24697/11) that describes the problem, but doesn't suggest a solution.
Can someone help me?
[12:02:52] <Mateusz Szymański> phinero: are you from Russia by any chance? cc https://mastodon.rfc1925.org/@deb/112721129407180511
[12:03:29] <Mateusz Szymański> (which would explain [HTTP 451](https://http.cat/451))
[12:22:07] <chrichri ⚡> > <@chrichri:ween.de> Hey everybody, I'm trying to change an alias entry in slapd using phpldapadmin and it returns me an error saying that I'd do not have sufficient rights to do that (logged in as member of the admin group). Found a [forum post](https://forum.yunohost.org/t/problems-connecting-to-yunohosts-ldap-database-the-user-cn-admin-no-longer-exists-in-the-new-version-of-yunohost/24697/11) that describes the problem, but doesn't suggest a solution.
> Can someone help me?

```
/usr/share/yunohost/conf/slapd# diff -u config.ldif-2024-07-31.orig config.ldif
--- config.ldif-2024-07-31.orig 2024-07-31 14:02:15.749987211 +0200
+++ config.ldif 2024-07-31 14:10:37.802705955 +0200
@@ -140,6 +140,7 @@
# Others should be able to see it.
olcAccess: {1}to attrs=cn,gecos,givenName,mail,maildrop,displayName,sn
by dn.base="gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth" write
+ by group/groupOfNamesYnh/member.exact="cn=admins,ou=groups,dc=yunohost,dc=org" write
by self write
by * read
#
```
This did the trick. I could write the attributes.
[12:48:19] <T> Hey all. How can I change the default mail port 25 to another one, say 587?
[12:49:00] <rodinux> hello, my nextcloud version 29.0.2 have stay with php8.2... Is it possible to migrate it to php8.3 before upgrade it ???
[12:50:28] <rodinux> > <@tsh:envs.net> Hey all. How can I change the default mail port 25 to another one, say 587?

the port 587 is the STARTTLS smtp port
[12:50:44] <rodinux> and 993 is the IMAP port...
[12:57:52] <Aleks (he/him/il/lui)> > <@tsh:envs.net> Hey all. How can I change the default mail port 25 to another one, say 587?

you don't : port 25 refers to the "incoming" traffic, i.e. other servers willing to deliver mail to your server. Depending on which exact mail protocol they use, they will use port 25. And there's no way to "tell" them to use a different port. That's similar to willing to change port 80 or 443 (for web) : people willing to visit your website won't be able to magically guess that the website is in fact on a different port
[12:58:47] <Aleks (he/him/il/lui)> ah or actually the issue with port 25 is also that it's sometimes blocked for outgoing traffic but that's the same story here : the other server expects to be contacted on port 25, you can't tell it to use a different port
[13:16:34] <T> > <@Alekswag:matrix.org> ah or actually the issue with port 25 is also that it's sometimes blocked for outgoing traffic but that's the same story here : the other server expects to be contacted on port 25, you can't tell it to use a different port

Yup that one. So I guess either I use a vps with open port 25 or only send emails from the server to a server email address?
[14:42:04] <phinero> Thank you, but it seems very weird. This server is located in SWE. Two others are in Holland and SWE and haven't this issue. (
[14:44:43] <phinero> Thank you, but it seems very weird. This server is located in SWE. Two others are in Holland and SWE and haven't this issue. ( The only difference is CloudFlare.
[14:51:38] <cdnpupper> omg not Cloudflare, behind the scenes, Cloudflare is the opposite of self hosting.
[15:19:09] <cdnpupper> any and all cloud services are your data on there physical servers
[17:55:00] <hook> Is the `robots.txt` file for XMPP uploads by default set up, so it’s not indexed?
[18:14:29] <Aleks (he/him/il/lui)> I doubt you can index XMPP uploads without knowing their exact URIs otherwise it's a much bigger security issue that just robot indexing
[18:28:57] *hook was probably overthinking
[19:28:07] <@err404:matrix.numericore.com> robots.txt <-- does not mean security
[20:58:22] <tufek> > <@orhtej2:matrix.org> phinero: are you from Russia by any chance? cc https://mastodon.rfc1925.org/@deb/112721129407180511

good to know, not cool for russian users though :/
[21:05:53] <rodinux> I have a problem, try upgrade a my_web_app and it failed, I try found from borg daily repository but something seems wrong... AArgh
[21:16:28] <rodinux> Is it normal the backups with borg seems all been in paths like `home/yunohost.backup/tmp/`
[21:24:11] <rodinux> Error: Could not load info for archive '/home/yunohost.backup/archives/auto_my_webapp-2024-07-31T04:29:52.tar.gz'… The info.json file cannot be retrieved (or is not a valid json)
[21:34:34] <orhtej2> > <@rodinux:matrix.org> I have a problem, try upgrade a my_web_app and it failed, I try found from borg daily repository but something seems wrong... AArgh

Borg backups are on remote server oO
[21:35:56] <rodinux> I have two BorgBackup, one local another on remote server (home server)
[21:38:34] <orhtej2> Still you should interact with it via borg, not filesystemm directly
[21:40:44] <rodinux> What do you mean ?
[21:41:21] <rodinux> restore the app with borg for example ?
[21:44:15] <rodinux> first I do a borg export-tar `app=borg; BORG_PASSPHRASE="$(yunohost app setting $app passphrase)" BORG_RSH="ssh -p xxxx -i /root/.ssh/id_borg_ed25519 -oStrictHostKeyChecking=yes " /var/www/${app}/venv/bin/borg export-tar "$(yunohost app setting $app repository)::auto_my_webapp-2024-07-31T04:29:52" /home/yunohost.backup/archives/auto_my_webapp-2024-07-31T04:29:52.tar
[21:45:17] <rodinux> now I can't use this tar file because first I need extract the info.json, isn't it ?
[21:45:38] <orhtej2> you don't need to export the tar, you can restore directly
[21:46:20] <rodinux> \o/ how ?
[21:49:35] <rodinux> something like borg extract ?
[21:54:28] <orhtej2> hmmm I was wrong apparently? I misremembered the docs (now gone)
[21:55:04] <rodinux> yes I also failed to see the link from the forum...
[21:55:05] <orhtej2> 'Then restore the archive in the usual way.' 🤷
[21:55:22] <orhtej2> https://github.com/YunoHost/doc/blob/4f828219e30ff61e2e4f492df8a65cf9addad59c/pages/02.administer/20.backups/10.backup_methods/01.borgbackup/borgbackup.md#restore (old now gone docs)
[21:58:41] <rodinux> well... what mean restore by the usual way ?
[22:14:19] <rodinux> I am afraid that that something is wrong...
[22:14:23] <Aleks (he/him/il/lui)> "the usual way" being via "yunohost backup restore" or from the webadmin in the Backup section using the Restore button etc
[22:22:19] <rodinux> To do so if there is no info.json yunohost can't see the backup, isn't it ??
[22:54:02] <hook> > robots.txt <-- does not mean security
Oh, yeah, I know. And some also ignore robots.txt too. But for those who follow it, it would at least tell them not to try to figure out what files are there.
[22:58:24] <hook> Again, probably overthinking it. I guess OMEMO also encrypts the file, so that's useful.