Tuesday, October 03, 2023
support@conference.yunohost.org
October
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:42:27] <orhtej2> this button?
[08:42:30] <ChriChri> Is there a configuration to prohibit email users defining there own aliases?
[08:42:30] <tituspijean> > <@chrichri:librem.one> Is there a configuration to prohibit email users defining there own aliases?

A global one no, and I thought you could play with hooks (https://yunohost.org/en/packaging_apps_hooks#post-user-update), but there is no `pre_user_update` hook... so no. 😕
[08:42:35] <ChriChri> > <@titus:pijean.ovh> A global one no, and I thought you could play with hooks (https://yunohost.org/en/packaging_apps_hooks#post-user-update), but there is no `pre_user_update` hook... so no. 😕

I don't understand completely: why would I use a hook? I'd like to disable the right to define aliases or even better make it its own permission, e.g. `email_alias`.
[08:42:39] <tituspijean> My reasoning was: if no global setting or permission exists, then use a hook, they should be versatile enough (in that case, no).
[11:26:35] <tane> orhtej2: yip. Didn't wprk.
[14:20:48] <amu> Hi! Nothing really important... My domain fails to renew its certificate. I'm still doing the old disable-XMPP workaround, which fortunately keeps working. But, is there any fix for it yet?
[14:25:44] <amu> I'm on version 11.2.3 stable
[15:32:21] <Aleks (he/him/il/lui)> you can try adding the `muc.domain.tld` entry to your /etc/hosts
[18:52:14] <jwgn> hi, I am unable to upgrade synapse. restore also failed. can anyone help me?

https://paste.yunohost.org/raw/ohepogihej
https://paste.yunohost.org/raw/moxiyasenu
https://paste.yunohost.org/raw/unusenepus
[19:01:30] <beelu> Bonjour à tous, suite à une mise à de l'app Hotspot ne fonctionne plus. Voici le log de la mise à jour : https://paste.yunohost.org/raw/iwuyewived
J'ai tenté une restauration sans succès.
Ensuite j'ai donc désinstallé puis re-installé via ssh, pas possible en webadmin, pas de succès non plus (le log: https://paste.yunohost.org/raw/xowucobori)
[19:02:06] <beelu> Je suis sur un rpi400. J'ai testé avec ou sans firmware non-libre
[19:04:50] <Aleks (he/him/il/lui)> mokay, est-ce que tu pourrais partager le log de dnsmasq depuis la partie Outils > Services > dnsmasq > Gros bouton vert "Partager les logs avec Yunopaste"
[19:06:56] <beelu> Ok
[19:07:33] <beelu> https://paste.yunohost.org/tirisabari
[19:10:39] <Aleks (he/him/il/lui)> `interface wlan0 inconnue` hmokay
[19:11:09] <beelu> Au redémarrage du RPi, je dois relancer ce service d'ailleurs (dnsmasq)
[19:12:07] <Aleks (he/him/il/lui)> le soucis avec hotspot a l'air surtout lié à hostapd qui ne monte pas :

```
2023-09-28 20:00:16,705: DEBUG - 152722 sept. 28 19:59:23 ynh-hotspot[464855]: sept. 28 19:58:19 systemd[1]: Starting Access point and authentication server for Wi-Fi and Ethernet...
2023-09-28 20:00:16,705: DEBUG - 152722 sept. 28 19:59:23 ynh-hotspot[464855]: sept. 28 19:58:19 hostapd[464244]: Configuration file: /etc/hostapd/hostapd.conf
2023-09-28 20:00:16,705: DEBUG - 152722 sept. 28 19:59:23 ynh-hotspot[464855]: sept. 28 19:58:19 hostapd[464244]: Could not open configuration file '\''/etc/hostapd/hostapd.conf'\'' for reading.
2023-09-28 20:00:16,706: DEBUG - 152723 sept. 28 19:59:23 ynh-hotspot[464855]: sept. 28 19:58:19 hostapd[464244]: Failed to set up interface with /etc/hostapd/hostapd.conf
2023-09-28 20:00:16,706: DEBUG - 152723 sept. 28 19:59:23 ynh-hotspot[464855]: sept. 28 19:58:19 hostapd[464244]: Failed to initialize interface
```
[19:13:04] <Aleks (he/him/il/lui)> mais ça ne montre pas vraiment quel est le vrai probleme
[19:20:03] <beelu> Un ifconfig me donne ça : sudo ifconfig wlan0
sudo: /etc/sudoers.d/domoticz is owned by uid 992, should be 0
wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether e4:5f:01:27:08:08 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
[19:20:51] <beelu> J'ai installé domoticz après ces problématiques de wifi
[19:29:27] <beelu> Un ifconfig complet t'aiderait à y voir plus clair ?
[19:45:01] <beelu> sudo iwconfig
sudo: /etc/sudoers.d/domoticz is owned by uid 992, should be 0
lo no wireless extensions.

eth0 no wireless extensions.

wlan0 IEEE 802.11 ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=31 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on

tun0 no wireless extensions.
[19:46:30] <jwgn> > <@jwgn:matrix.org> hi, I am unable to upgrade synapse. restore also failed. can anyone help me?
>
> https://paste.yunohost.org/raw/ohepogihej
> https://paste.yunohost.org/raw/moxiyasenu
> https://paste.yunohost.org/raw/unusenepus

any idea on how to get synapse back to a working state?
[19:49:51] <tituspijean> jwgn: I read the error for you:

> The password needs to be at least 12 characters long and contain a digit, upper, lower and special characters
2023-10-03 19:51:40,239: DEBUG - 118599 You are now about to define a new user password. The password should be at least 8 characters long—though it is good practice to use a longer password (i.e. a passphrase) and/or to a variation of characters (uppercase, lowercase, digits and special characters).

Lower your global setting for password strength, restore, put it back up.
[19:50:40] <tituspijean> jwgn: Read it for you:

> The password needs to be at least 12 characters long and contain a digit, upper, lower and special characters
2023-10-03 19:51:40,239: DEBUG - 118599 You are now about to define a new user password. The password should be at least 8 characters long—though it is good practice to use a longer password (i.e. a passphrase) and/or to a variation of characters (uppercase, lowercase, digits and special characters).

Have you tweaked the global setting for password strength?
[19:52:44] <beelu> > <@Alekswag:matrix.org> mais ça ne montre pas vraiment quel est le vrai probleme

Normal que hostapd.conf soit vide ?
[19:55:43] <beelu> D'ailleurs hostapd.accesspoint.conf et hostapd.base.conf vide aussi
[19:55:56] <jwgn> > <@titus:pijean.ovh> jwgn: Read it for you:
>
> > The password needs to be at least 12 characters long and contain a digit, upper, lower and special characters
> 2023-10-03 19:51:40,239: DEBUG - 118599 You are now about to define a new user password. The password should be at least 8 characters long—though it is good practice to use a longer password (i.e. a passphrase) and/or to a variation of characters (uppercase, lowercase, digits and special characters).
>
> Have you tweaked the global setting for password strength?

yes, but I changed it back to "Require at least 8 chars" restore still failing, see latest log
[19:58:39] <jwgn> https://aria.im/_matrix/media/v1/download/matrix.org/uUdJVivrmjjhSVoxKquxPMmi
[19:58:50] <jwgn> what else do I need to change to get it back working? right now my synapse is down and I cannot connect.
[20:04:57] <jorgeluis> >> <jorgeluis> > you'd need to put a reverse proxy there
> ...view rest of paste (36 lines): https://conference.yunohost.org/pastebin/c86080b4-49dc-47eb-a551-60bcdc351f8c
Do you know how can I implement such a reverse proxy? Which files should I edit?
[20:12:38] <tituspijean> jwgn damn we regularly have issues with setuptools and synapse... ☹️
here is an answer adapted from https://forum.yunohost.org/t/solved-synapse-update-failed-restore-not-possible/22888/2:

```
$ cd /home/yunohost.backup/archives/
$ ls -l synapse-pre-upgrade* # This is to double check the name of the backup, adjust the file name accordingly later, and take the latest
$ cp synapse-pre-upgrade1.tar synapse-pre-upgrade1.tar.bak # Make a backup of the existing backup before modifying, just in case
$ sudo tar --delete --file synapse-pre-upgrade1.tar apps/synapse/backup/opt/yunohost/matrix-synapse/lib/python3.9/site-packages/setuptools
$ yunohost backup restore synapse-pre-upgrade1 --apps synapse # start restoring the backup
```
[20:12:38] <beelu> > <@Alekswag:matrix.org> mais ça ne montre pas vraiment quel est le vrai probleme

Les dernières lignes du journal hostapd:

journalctl -u hostapd -n 100 --no-hostname --no-pager

ep 29 22:42:55 systemd[1]: hostapd.service: Scheduled restart job, restart counter is at 7.
Sep 29 22:42:55 systemd[1]: Stopped Access point and authentication server for Wi-Fi and Ethernet.
Sep 29 22:42:55 systemd[1]: Starting Access point and authentication server for Wi-Fi and Ethernet...
Sep 29 22:42:55 hostapd[80223]: Configuration file: /etc/hostapd/hostapd.conf
Sep 29 22:42:55 hostapd[80223]: Interface name not specified in /etc/hostapd/hostapd.conf, nor by '-i' parameter
Sep 29 22:42:55 hostapd[80223]: : interface state UNINITIALIZED->DISABLED
Sep 29 22:42:55 hostapd[80223]: : AP-DISABLED
Sep 29 22:42:55 hostapd[80223]: : CTRL-EVENT-TERMINATING
Sep 29 22:42:55 hostapd[80223]: hostapd_free_hapd_data: Interface wasn't started
Sep 29 22:42:55 hostapd[80223]: Failed to initialize interface
Sep 29 22:42:55 systemd[1]: hostapd.service: Control process exited, code=exited, status=1/FAILURE
Sep 29 22:42:55 systemd[1]: hostapd.service: Failed with result 'exit-code'.
Sep 29 22:42:55 systemd[1]: Stopped Access point and authentication server for Wi-Fi and Ethernet.
[20:14:54] <jwgn> > <@titus:pijean.ovh> jwgn damn we regularly have issues with setuptools and synapse... ☹️
> here is an answer adapted from https://forum.yunohost.org/t/solved-synapse-update-failed-restore-not-possible/22888/2:
>
> ```
> $ cd /home/yunohost.backup/archives/
> $ ls -l synapse-pre-upgrade* # This is to double check the name of the backup, adjust the file name accordingly later, and take the latest
> $ cp synapse-pre-upgrade1.tar synapse-pre-upgrade1.tar.bak # Make a backup of the existing backup before modifying, just in case
> $ sudo tar --delete --file synapse-pre-upgrade1.tar apps/synapse/backup/opt/yunohost/matrix-synapse/lib/python3.9/site-packages/setuptools
> $ yunohost backup restore synapse-pre-upgrade1 --apps synapse # start restoring the backup
> ```

```
sudo tar --delete --file synapse-pre-upgrade1.tar apps/synapse/backup/opt/yunohost/matrix-synapse/lib/python3.9/site-packages/setuptools
tar: Cannot update compressed archives
tar: Error is not recoverable: exiting now
```
[20:22:23] <jwgn> > <@jwgn:matrix.org> ```
> sudo tar --delete --file synapse-pre-upgrade1.tar apps/synapse/backup/opt/yunohost/matrix-synapse/lib/python3.9/site-packages/setuptools
> tar: Cannot update compressed archives
> tar: Error is not recoverable: exiting now
> ```

`synapse-pre-upgrade1.tar: symbolic link to /home/yunohost.backup/archives/synapse-pre-upgrade1.tar.gz` 🤔
[20:45:00] <jwgn> deleted that folder and created a new archive, still failing https://paste.yunohost.org/raw/ameloyijiw
[20:45:45] <jwgn> any more ideas? ☹️
[20:47:44] <jwgn> I thought the backup feature backups the app in case anything goes wrong with the update. how is it possible that both upgrade and restore fails? how to recover from that situation?
[20:48:53] <tituspijean> jwgn erf you need to "ungz" the archive first
[20:50:46] <jwgn> isn't that what `tar xf` does?
[20:51:23] <tituspijean> maybe so, have you run that command?
[20:52:56] <jwgn> what I did:


```
pwd
/home/yunohost.backup/archives/temp
```

```
965 2023-10-03 22:24:33 tar xf synapse-pre-upgrade1.tar.gz
966 2023-10-03 22:26:05 rm apps/synapse/backup/opt/yunohost/matrix-synapse/lib/python3.9/site-packages/setuptools
967 2023-10-03 22:26:21 rm -rf apps/synapse/backup/opt/yunohost/matrix-synapse/lib/python3.9/site-packages/setuptools
968 2023-10-03 22:26:42 rm synapse-pre-upgrade1.tar.gz
969 2023-10-03 22:27:42 tar -czf synapse-pre-upgrade1.tar.gz *
975 2023-10-03 22:36:38 rm ../synapse-pre-upgrade1.tar
976 2023-10-03 22:36:40 cd ..
981 2023-10-03 22:39:24 ln -s /home/yunohost.backup/archives/temp/synapse-pre-upgrade1.tar.gz synapse-pre-upgrade1.tar
```
[20:53:40] <jwgn> still failing
[20:54:40] <tituspijean> with same error, I presume?
[20:54:43] <jwgn> yes
[20:54:47] <jwgn> ```
10:53:56 jwgn@f1sh archives → ls -l synapse-pre-upgrade*
-rw-r--r-- 1 root root 308 Oct 3 19:48 synapse-pre-upgrade1.info.json
lrwxrwxrwx 1 jwgn jwgn 63 Oct 3 22:39 synapse-pre-upgrade1.tar -> /home/yunohost.backup/archives/temp/synapse-pre-upgrade1.tar.gz
-rw-r--r-- 1 jwgn jwgn 2372739649 Oct 3 22:12 synapse-pre-upgrade1.tar.bak
-rw-r--r-- 1 root root 2372739649 Oct 3 19:48 synapse-pre-upgrade1.tar.gz
```
[20:55:42] <jwgn> ```
10:55:10 jwgn@f1sh archives → ls -l temp/
total 2352940
drwxr-xr-x 3 jwgn jwgn 4096 Oct 3 22:24 apps
-rw-r--r-- 1 jwgn jwgn 1482 Oct 3 19:41 backup.csv
-rw-r--r-- 1 jwgn jwgn 308 Oct 3 19:41 info.json
-rw-r--r-- 1 root root 2409392474 Oct 3 22:35 synapse-pre-upgrade1.tar.gz
```
[20:57:59] <jwgn> ```
023-10-03 22:42:09,785: DEBUG - Installing collected packages: setuptools
2023-10-03 22:42:09,786: DEBUG - Attempting uninstall: setuptools
2023-10-03 22:42:09,787: DEBUG - Found existing installation: setuptools 68.2.0
2023-10-03 22:42:09,807: DEBUG - Uninstalling setuptools-68.2.0:
2023-10-03 22:42:09,853: DEBUG - Successfully uninstalled setuptools-68.2.0
2023-10-03 22:42:10,270: WARNING - ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
2023-10-03 22:42:10,271: WARNING - setuptools-rust 1.7.0 requires setuptools>=62.4, but you have setuptools 60.8.2 which is incompatible.
2023-10-03 22:42:10,271: DEBUG - Successfully installed setuptools-60.8.2
2023-10-03 22:42:10,404: DEBUG - + pip3 install --upgrade cffi ndg-httpsclient psycopg2 lxml jinja2
2023-10-03 22:42:10,798: DEBUG - Requirement already satisfied: cffi in /opt/yunohost/matrix-synapse/lib/python3.9/site-packages (1.15.1)
2023-10-03 22:42:11,070: DEBUG - Collecting cffi
2023-10-03 22:42:11,071: DEBUG - Obtaining dependency information for cffi from https://files.pythonhosted.org/packages/ea/ac/e9e77bc385729035143e54cc8c4785bd480eaca9df17565963556b0b7a93/cffi-1.16.0-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata
2023-10-03 22:42:11,082: DEBUG - Using cached cffi-1.16.0-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (1.5 kB)
2023-10-03 22:42:11,083: DEBUG - Requirement already satisfied: ndg-httpsclient in /opt/yunohost/matrix-synapse/lib/python3.9/site-packages (0.5.1)
2023-10-03 22:42:11,098: DEBUG - Requirement already satisfied: psycopg2 in /opt/yunohost/matrix-synapse/lib/python3.9/site-packages (2.9.7)
2023-10-03 22:42:11,200: DEBUG - Collecting psycopg2
2023-10-03 22:42:11,213: DEBUG - Using cached psycopg2-2.9.9.tar.gz (384 kB)
2023-10-03 22:42:11,273: DEBUG - Preparing metadata (setup.py): started
2023-10-03 22:42:11,503: DEBUG - Preparing metadata (setup.py): finished with status 'error'
2023-10-03 22:42:11,509: WARNING - error: subprocess-exited-with-error
```
[20:59:02] <jwgn> why does it uninstall `setuptools-68.2.0`and tries to install `setuptools-60.8.2` `when setuptools>=62.4` is needed?
[21:00:13] <tituspijean> from what I see it went further down the script, now its error is on psycopg2
[21:01:24] <tituspijean> > <@jwgn:matrix.org> why does it uninstall `setuptools-68.2.0`and tries to install `setuptools-60.8.2` `when setuptools>=62.4` is needed?

excellent question, as I wrote earlier it is not the first time it happens and I have no clue why it would behave like that. The YunoHost package does not specifically alter the python requirements
[21:01:50] <tituspijean> > <@titus:pijean.ovh> from what I see it went further down the script, now its error is on psycopg2

you should do the same tweak with `psycopg2`
[21:02:19] <jwgn> but it is the exact same error as on the first attempt
[21:02:40] <jwgn> ```
2023-10-03 22:42:10,270: WARNING - ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
2023-10-03 22:42:10,271: WARNING - setuptools-rust 1.7.0 requires setuptools>=62.4, but you have setuptools 60.8.2 which is incompatible.
```
[21:05:07] <jwgn> https://paste.yunohost.org/raw/ohepogihej this was the first upgrade attempt hours ago

```
023-10-03 19:49:12,259: DEBUG - + pip3 install --upgrade setuptools==60.8.2 wheel pip
2023-10-03 19:49:13,433: DEBUG - Collecting setuptools==60.8.2
2023-10-03 19:49:13,454: DEBUG - Using cached setuptools-60.8.2-py3-none-any.whl (1.1 MB)
2023-10-03 19:49:13,463: DEBUG - Requirement already satisfied: wheel in /opt/yunohost/matrix-synapse/lib/python3.9/site-packages (0.41.2)
2023-10-03 19:49:13,525: DEBUG - Requirement already satisfied: pip in /opt/yunohost/matrix-synapse/lib/python3.9/site-packages (23.2.1)
2023-10-03 19:49:14,188: DEBUG - Installing collected packages: setuptools
2023-10-03 19:49:14,189: DEBUG - Attempting uninstall: setuptools
2023-10-03 19:49:14,190: DEBUG - Found existing installation: setuptools 68.2.0
2023-10-03 19:49:14,210: DEBUG - Uninstalling setuptools-68.2.0:
2023-10-03 19:49:14,261: DEBUG - Successfully uninstalled setuptools-68.2.0
2023-10-03 19:49:14,688: WARNING - ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
2023-10-03 19:49:14,688: WARNING - setuptools-rust 1.7.0 requires setuptools>=62.4, but you have setuptools 60.8.2 which is incompatible.
2023-10-03 19:49:14,688: DEBUG - Successfully installed setuptools-60.8.2
2023-10-03 19:49:14,927: DEBUG - + pip3 install --upgrade cffi ndg-httpsclient psycopg2 lxml jinja2
2023-10-03 19:49:15,312: DEBUG - Requirement already satisfied: cffi in /opt/yunohost/matrix-synapse/lib/python3.9/site-packages (1.15.1)
2023-10-03 19:49:15,700: DEBUG - Collecting cffi
2023-10-03 19:49:15,700: DEBUG - Obtaining dependency information for cffi from https://files.pythonhosted.org/packages/ea/ac/e9e77bc385729035143e54cc8c4785bd480eaca9df17565963556b0b7a93/cffi-1.16.0-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata
2023-10-03 19:49:15,871: DEBUG - Downloading cffi-1.16.0-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (1.5 kB)
2023-10-03 19:49:15,882: DEBUG - Requirement already satisfied: ndg-httpsclient in /opt/yunohost/matrix-synapse/lib/python3.9/site-packages (0.5.1)
2023-10-03 19:49:15,904: DEBUG - Requirement already satisfied: psycopg2 in /opt/yunohost/matrix-synapse/lib/python3.9/site-packages (2.9.7)
2023-10-03 19:49:16,003: DEBUG - Collecting psycopg2
2023-10-03 19:49:16,014: DEBUG - Downloading psycopg2-2.9.9.tar.gz (384 kB)
2023-10-03 19:49:16,050: DEBUG - ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 384.9/384.9 kB 11.7 MB/s eta 0:00:00
2023-10-03 19:49:16,104: DEBUG - Preparing metadata (setup.py): started
2023-10-03 19:49:16,387: DEBUG - Preparing metadata (setup.py): finished with status 'error'
2023-10-03 19:49:16,391: WARNING - error: subprocess-exited-with-error
2023-10-03 19:49:16,391: DEBUG -
2023-10-03 19:49:16,391: WARNING - × python setup.py egg_info did not run successfully.
```
[21:05:19] <jwgn> `68.2.0` and `60.8.2` is there a typo somewhere?
[21:07:14] <tituspijean> OK I am completely misreading your logs. I'll have a good night's rest now, before I write something very wrong.
[21:09:59] <jwgn> https://github.com/YunoHost-Apps/synapse_ynh/blob/6537f170c3bea49c3cba84ac6709c09d311915e6/scripts/_common.sh#L51 what about this?

`pip3 install --upgrade setuptools==60.8.2 wheel pip`
[21:11:03] <jwgn> it seems is does exactly try to install `60.8.2` but it should be `68.2.0`? maybe?
[21:13:46] <jwgn> https://github.com/YunoHost-Apps/synapse_ynh/commit/d7e9813f9b1d494ca1c849247b3336696515e231 I assume this is a typo in the code. I am not a programmer, can anyone verify this?
[21:15:07] <tituspijean> (eh, I was confidently wrong on that part too, gotta go sleep in shame 🔔)
[21:27:12] <jwgn> not sure if I did this correctly, but I have created a pull request with a possible fix (if it's really just a typo) https://github.com/YunoHost-Apps/synapse_ynh/pull/417
[22:41:59] <Thomas> Bonjour, j'ai une question bête, y'a t'il une utilité à chiffrer une conversation entre deux utilisateurs sur son serveur matrix (synapse) en sachant que le tout est héberger chez sois?
[23:08:50] <Aleks (he/him/il/lui)> si on parle de chiffrement bout en bout, l'intérêt est que les correspondants n'ont pas besoin de faire confiance au serveur ou au réseau puisque le message est chiffré avec la clef du destinataire, donc seul le destinaire pourra déchiffrer le message
[23:09:33] <Aleks (he/him/il/lui)> Après la sécurité c'est comme d'hab : le mot sécurité ne veut rien dire sans relation à un modèle de menace définit
[23:11:42] <Thomas> Merci Aleks (he/him/il/lui) pour l’éclaircissement en cette heure tardive