[07:13:05]
<eric_G> ynhuser: this as been fixed yesterday and should be available to download soon
[07:14:55]
<Guillaume Bouzige> when i have installed an app, can I access it via ip + port instead of a domain ?
[07:15:28]
<Guillaume Bouzige> if yes how can I find those infos for each app ?
[08:18:17]
<tituspijean> you could, but not with a public-facing access, and only with apps shipping their own web server
[08:18:42]
<tituspijean> `yunohost app setting <app> -f | grep port`
[08:19:30]
<tituspijean> and access with `curl http://127.0.0.1:<;port>`, with port opened in the firewall (hence why it should not be public-facing)
[08:22:51]
<Guillaume Bouzige> yes I see
[08:23:15]
<Guillaume Bouzige> I was getting at `sudo ss -tulpn`
[08:28:09]
<Guillaume Bouzige> that would not work for a static website with my_web_app thingy no?
[08:46:32]
<tituspijean> nope, then NGINX would be responsible for routing the user to the page, but it is only based on the server name and path, no IP.
[08:54:23]
<Guillaume Bouzige> yes I thought soao
[09:32:16]
<mushy> so i kinda broke my server with no way. The only thing I remember modifying is ssl certs.
[09:38:44]
<tituspijean> We'll need more details to properly help you. :)
[09:54:58]
<Lucas[m]> Je n'utilise pas l'app Synapse Admin parce que je rencontre cette erreur lorsque j'essaie de l'installer:
https://paste.yunohost.org/raw/awotapegep
[09:58:28]
<mushy> fixed it. i had tried to expose the port :443 from a service, hours ago and didn't realize the catastrophic consequences until i restarted.
[09:59:14]
<Lucas[m]> Sur une autre note, où se trouve le fichier synapse.conf ? 😅
[10:02:08]
<tituspijean> > <@lucas:synapse.tolula.fr> Je n'utilise pas l'app Synapse Admin parce que je rencontre cette erreur lorsque j'essaie de l'installer:
>
> https://paste.yunohost.org/raw/awotapegep
Cela se produit systématiquement ?
[10:02:45]
<tituspijean> > <@lucas:synapse.tolula.fr> Sur une autre note, où se trouve le fichier synapse.conf ? 😅
`/etc/nginx/conf.d/DOMAINE.tld/synapse.conf`
[10:05:15]
<ingolf9[m]> Hello,
which bridge do you use to Jabber/XMPP?
It seems to work very well.
Thanks for the answer.
[10:56:55]
<moko> broke something again
[10:59:52]
<moko> unable to upload the file
[11:00:33]
<moko> Traceback (most recent call last):
[11:00:34]
<moko> File "/usr/lib/python3/dist-packages/moulinette/interfaces/api.py", line 457, in process
[11:00:35]
<moko> ret = self.actionsmap.process(arguments, timeout=30, route=_route)
[11:00:36]
<moko> File "/usr/lib/python3/dist-packages/moulinette/actionsmap.py", line 584, in process
[11:00:36]
<moko> return func(**arguments)
[11:00:37]
<moko> result = func(*args, **kwargs)
[11:00:37]
<moko> File "/usr/lib/python3/dist-packages/yunohost/log.py", line 410, in func_wrapper
[11:00:38]
<moko> File "/usr/lib/python3/dist-packages/yunohost/domain.py", line 270, in domain_add
[11:00:38]
<moko> _certificate_install_selfsigned([domain], True)
[11:00:40]
<moko> with open(ca_file, "r") as ca_pem, open(crt_file, "a") as crt_pem:
[11:00:40]
<moko> File "/usr/lib/python3/dist-packages/yunohost/certificate.py", line 194, in _certificate_install_selfsigned
[11:00:41]
<moko> FileNotFoundError: [Errno 2] No such file or directory: '/etc/yunohost/certs//manage.*redacted*.xyz-history/20230407.103834-selfsigned/ca.pem'
[11:05:12]
<moko> I've checked and the directory+files definitely exists
[11:06:35]
<tituspijean> > <@moko:libera.chat> unable to upload the file
you have a "Share with YunoPaste" button for that. What did you do to your server?
[11:08:15]
<moko> but i was already in the chat so i pasted here but the paste.txt file won't upload.
[11:08:46]
<Aleks (he/him/il/lui)> you don't need to upload the file, just share the generated link ...
[11:08:56]
<moko> ok
[11:09:27]
<moko> https://paste.yunohost.org/raw/sumaqiqeco
[11:09:29]
<moko> here
[11:11:42]
<moko> i think i somehow messed up the symlinks in the /etc/yunohust/certs dir
[11:12:51]
<moko> replaced certificates with the wildcard ones in "pikko.xyz". but I've since restored them to no avail. still unable to add subdomains.
[11:28:32]
<moko> tituspijean ok, i think i had emptied out the ca.pem located in yunohost.org somehow. what do i do about it now?
[11:28:54]
<moko> seems like that's where self-signed certs come from
[11:42:02]
<moko> so much for getting help man.
[11:43:10]
<Lucas[m]> > <@titus:pijean.ovh> Cela se produit systématiquement ?
Oui sur les 3-4 essais, à chaque fois la même erreur
[11:43:57]
<tituspijean> > <@moko:libera.chat> so much for getting help man.
so much for your patience, dude. I'm reading YunoHost's code to see if you can regenerate the self-signed cert.
[11:44:02]
<Lucas[m]> > <@titus:pijean.ovh> `/etc/nginx/conf.d/DOMAINE.tld/synapse.conf`
Merci!
J'ai donc ajouté ces lignes dans le fichier:
```
if ($http_origin ~* "^https?://(github.io)$") {
add_header Access-Control-Allow-Origin "$http_origin";
}
```
j'ai toujours les mêmes erreurs, après restart du nginx et du serveur synapse
[11:44:14]
<tituspijean> > <@lucas:synapse.tolula.fr> Oui sur les 3-4 essais, à chaque fois la même erreur
mmmh très étrange 😕
[11:46:09]
<tituspijean> Un simple `more_set_headers "Access-Control-Allow-Origin: https://awesome-technologies.github.io";` sans `if` devrait suffire
[11:50:14]
<tituspijean> moko so I dunno how to manually regen the CA and a self-signed cert. Don't hesitate to post your request on the forum. (reminder: wildcard certificates are not supported yet, so do backups when you play with certificates...)
[12:58:18]
<Lucas[m]> > <@titus:pijean.ovh> Un simple `more_set_headers "Access-Control-Allow-Origin: https://awesome-technologies.github.io";` sans `if` devrait suffire
en ajoutant cette ligne, après redémarrage de nginx, le serveur synapse devient injoignable 🤔
[13:17:32]
<tituspijean> J'ai dû faire une coquille, vérifie avec `nginx -t`
[13:19:03]
<Lucas[m]> Non ça semble bien normal:
```
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
```
[13:27:22]
<mistral> Bonjour, j'essaie de réinstaller Yunohost, mais le domaine "erca.nohost.me" est indisponible. Merci
[13:28:27]
<tituspijean> Lucas ah oups, le serveur s'ignore lui-même maintenant... essaie avec `more_set_headers "Access-Control-Allow-Origin: https://awesome-technologies.github.io https://TON_DOMAINE";`
[13:28:38]
<Aleks (he/him/il/lui)> mistral: je viens de le réinitialiser mais normalement il faut demander sur https://forum.yunohost.org/t/nohost-domain-recovery-suppression-de-domaine-en-nohost-me-noho-st-et-ynh-fr/442
[13:29:24]
<tituspijean> Lucas mais sinon je me note d'investiguer le timeout quand tu installes l'app
[13:29:47]
<mistral> Merci pour ta réponse, mais je ne savais trop comment faire ...
[13:30:05]
<Aleks (he/him/il/lui)> unjour™ les gens pourront réinitialiser leur domaine en autonomie ...
[13:39:18]
<Lucas[m]> > <@titus:pijean.ovh> Lucas ah oups, le serveur s'ignore lui-même maintenant... essaie avec `more_set_headers "Access-Control-Allow-Origin: https://awesome-technologies.github.io https://TON_DOMAINE";`
même constat, synapse injoignable. J'ai essayé avec le domaine du serveur synapse, et le domaine général
[13:39:52]
<Lucas[m]> est-ce que le module permettant d'utiliser "more_set_headers" est installé de base avec nginx sur yunohost ?
[13:41:41]
<tituspijean> Normalement oui. Je pourrai tenter de déboguer ça ce soir ou demain ;)
[13:43:07]
<Lucas[m]> c'est gentil merci! mais c'est vraiment pas urgent, j'essaie de comprendre ce que je fais sur yunohost et synapse, mais j'ai pas de contraintes d'utilisation/ d'utilisateurs derrière, donc pas de pression pour checker tout ça 🙂