[11:13:57]
<ramfreeman> Hey guys, I'm trying to integrate Onlyoffice with next cloud, both are installed at YunoHost 11.0.11 (stable)
I installed them on the same domain as it's recommended, and when i try to change the setting for onlyoffice server settings Inside nextcloud
at the "ONLYOFFICE Docs address" I put my onlyoffice server location example https://Mydomain.ynh.fr/onlyoffice/
I got this error:
Error when trying to connect (cURL error 60: SSL certificate problem: self signed certificate in certificate chain (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://Mydomain.ynh.fr/onlyoffice/healthcheck)
When i open https://Mydomain.ynh.fr/onlyoffice/healthcheck
the page only shows "true"
I also tried disabling the certificate verfication and i got an error saying
Error when trying to connect (Error occurred in the document service: Invalid token)
I wonder if I'm doing something wrong or there is a bug there
[11:40:19]
<ramfreeman> Any suggestion is very welcome and highly appreciated <3
[11:40:19]
<ramfreeman> I'm also not able to install alternative to ONLYOFFICE like Collabora Online - Built-in CODE Server
i got:
An error occurred during the request. Unable to proceed.
and then it shows me:
This installation does not have a built in server. Install it from the App Store.
If the installation from the App Store fails, you can still do that manually using this command: php -d memory_limit=512M occ app:install richdocumentscode
I'm not able to do that cuz i installed Next cloud using yunohost.
[13:37:18]
<IoMe> Good afternoon
[13:37:25]
<IoMe> I need some help with IPv6
[13:38:23]
<IoMe> My smtp is on spamhaus CSS list on the IPv6 address but I don't understand how I could remove it
[13:39:08]
<IoMe> I passed the helo trial of spamhaus but it was not sufficient
[15:31:05]
<pti-jean> Bonjour,
J'ai reçu par courriel un message d'erreur concernant mon Yunohost, dont l'objet est:
Issues found by automatic diagnosis on MonNomDeDomaine.fr
Et le message est ici:
https://paste.yunohost.org/cufoviqese.sql
L'utilitaire de diagnostic, confirme l'erreur de DNS...
Chose forte, j'ai rien touché à la config, et avant-hier y avais pas d'erreur...
Chose pas mal aussi... excepté ce message d'erreur, je n'ai constaté aucun dysfonctionnement...
Je me demande donc si j'ignore le message d'erreur... si c'est-un simple défaut de diagnostic, et que cela va rentré dans l'ordre... Si l'erreur vient de mon fournisseur de nom de domaine (à savoir www.bookmyname.com ), et que le problème est ponctuel...
[15:32:00]
<pti-jean> Bref... vu que je ne constate pas de défaut... Je ne sais pas trop ce que je doit faire ???
[15:34:30]
<pti-jean> Une idée ?
[15:35:41]
<mbjdsh> > Bref... vu que je ne constate pas de défaut... Je ne sais pas trop ce que je doit faire ???
[15:41:53]
<MayeulC> > <IoMe> My smtp is on spamhaus CSS list on the IPv6 address but I don't understand how I could remove it
First, do you have at least a /64?
[15:42:49]
<IoMe> MayeulC, > First, do you have at least a /64?
I think yes 🙂
[15:44:47]
<IoMe> MayeulC, so ip a is saying
[15:58:21]
<MayeulC> @IoMe, if you host at home it's likely the case.
[16:06:17]
<IoMe> MayeulC, no, it's a gandi vps
[16:45:40]
<ths> Auriez vous une idée ?
[16:47:45]
<pti-jean> ths, Tu avais 2 NextCloud dans un seul YunoHost ?? Comment tu fais ?
[16:47:47]
<ths> Je ne sais pas comment réinstaller pour que tous les utilisateurs puissent retrouver leur fichiers..
[16:48:08]
<ths> sous domaine
[16:48:19]
<ths> ça fonctionnait très bien
[16:48:55]
<ths> mais depuis la dernière mise à jour, pof, disparu
[16:50:25]
<pti-jean> Mais cela ne me semble pas possible, d'avoir 2 NextCloud dans un seul YunoHost ???
[16:50:44]
<pti-jean> Comment tu fais ?
[16:51:06]
<ths> comme dit, simplement plusieurs sous domaine, il est prévu pour
[16:51:50]
<ths> "Allow multiple instances of this application"
[16:51:59]
<ths> https://github.com/YunoHost-Apps/nextcloud_ynh
[16:54:58]
<pti-jean> Alors là... je vais me coucher, je suis incompétent !
[18:13:54]
<DerpFox> Hello, is it possible with why you no host to generate let's encrypt certificate for subdomain not pointing toward the ip where yunohost is hosted
[23:36:08]
<gredin67> > <@ramfreeman:matrix.org> Hey guys, I'm trying to integrate Onlyoffice with next cloud, both are installed at YunoHost 11.0.11 (stable)
> I installed them on the same domain as it's recommended, and when i try to change the setting for onlyoffice server settings Inside nextcloud
>
> at the "ONLYOFFICE Docs address" I put my onlyoffice server location example https://Mydomain.ynh.fr/onlyoffice/
>
> I got this error:
> Error when trying to connect (cURL error 60: SSL certificate problem: self signed certificate in certificate chain (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://Mydomain.ynh.fr/onlyoffice/healthcheck)
>
> When i open https://Mydomain.ynh.fr/onlyoffice/healthcheck
> the page only shows "true"
>
> I also tried disabling the certificate verfication and i got an error saying
> Error when trying to connect (Error occurred in the document service: Invalid token)
>
>
> I wonder if I'm doing something wrong or there is a bug there
lol you should NOT install on the same domain ;)
https://github.com/YunoHost-Apps/onlyoffice_ynh/tree/master#prerequisite
[23:36:10]
<gredin67> here is a sample domain setup:
- install only office on `office.yourdomain.tld`
- install nextcloud on `file.yourdomain.tld` or `yourdomain.tld/file`
[23:36:10]
<gredin67> finally you may have to give a token below the onlyoffice url in the nextcloud ONLYOFFICE settings panel. You can get it by running `sudo documentserver-jwt-status.sh` on your server
https://github.com/YunoHost-Apps/onlyoffice_ynh/issues/84