[03:06:17]
<saebaryo.xyz> Hi tituspijean eric_G So, even after using an older version seems to be only working on Firefox based browsers not Chromium based 🤔
[03:56:11]
<saebaryo.xyz> Hi Everyone, getting the following error when opening any document in Nextcloud:
**Failed to load Next Office. Please try later.**
_**The Install:**_
I installed Collabora in Yunohost and set it to my subdomain office.yorili.com
And made sure to select the next cloud path in the app before installation.
After that I installed the Nextcloud Office App inside from the NC apps and then added the URL of my Collabora instance which is office.yorili.com (Didn’t add any port) and also made sure to add collabora and nextcloud as permissions inside the admin user, all users and visitors groups in Yunohost setting.
[05:37:29]
<lapineige> Did you configure a whitelist ?
[05:41:11]
<saebaryo.xyz> No and if I need to from where please?
[06:02:44]
<saebaryo.xyz> This is a portion of the XML file where it mentions the WOPI:
<storage desc="Backend storage">
<filesystem allow="false" />
<wopi desc="Allow/deny wopi storage." allow="true">
<host desc="Regex pattern of hostname to allow or deny." allow="true">yorili.com/mycloud</host>
<host desc="Regex pattern of hostname to allow or deny." allow="true">10\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}</host>
<host desc="Regex pattern of hostname to allow or deny." allow="true">172\.1[6789]\.[0-9]{1,3}\.[0-9]{1,3}</host>
<host desc="Regex pattern of hostname to allow or deny." allow="true">172\.2[0-9]\.[0-9]{1,3}\.[0-9]{1,3}</host>
<host desc="Regex pattern of hostname to allow or deny." allow="true">172\.3[01]\.[0-9]{1,3}\.[0-9]{1,3}</host>
<host desc="Regex pattern of hostname to allow or deny." allow="true">192\.168\.[0-9]{1,3}\.[0-9]{1,3}</host>
<host desc="Regex pattern of hostname to allow or deny." allow="false">192\.168\.1\.1</host>
<max_file_size desc="Maximum document size in bytes to load. 0 for unlimited." type="uint">0</max_file_size>
<locking desc="Locking settings">
<refresh desc="How frequently we should re-acquire a lock with the storage server, in seconds (default 15 mins) or 0 for no refresh" type="int" default="900">900</refresh>
</locking>
</wopi>
<ssl desc="SSL settings">
<as_scheme type="bool" default="true" desc="When set we exclusively use the WOPI URI's scheme to enable SSL for storage">true</as_scheme>
<enable type="bool" desc="If as_scheme is false or not set, this can be set to force SSL encryption between storage and coolwsd. When empty this defaults to following the ssl.enable setting"></enable>
<cert_file_path desc="Path to the cert file" relative="false"></cert_file_path>
<key_file_path desc="Path to the key file" relative="false"></key_file_path>
<ca_file_path desc="Path to the ca file. If this is not empty, then SSL verification will be strict, otherwise cert of storage (WOPI-like host) will not be verified." relative="false"></ca_file_path>
<cipher_list desc="List of OpenSSL ciphers to accept. If empty the defaults are used. These can be overridden only if absolutely needed."></cipher_list>
</ssl>
</storage>
[06:07:28]
<saebaryo.xyz> In Nextcloud, this is the error I see in the logs:
Error: simplexml_load_string(): Entity: line 60: parser error : Opening and ending tag mismatch: form line 47 and div at /var/www/nextcloud/apps/richdocuments/lib/WOPI/Parser.php#47
[08:45:42]
<orhtej2> > <@saebaryo.xyz:matrix.org> This is a portion of the XML file where it mentions the WOPI:
>
>
>
> <storage desc="Backend storage">
> <filesystem allow="false" />
> <wopi desc="Allow/deny wopi storage." allow="true">
> <host desc="Regex pattern of hostname to allow or deny." allow="true">yorili.com/mycloud</host>
> <host desc="Regex pattern of hostname to allow or deny." allow="true">10\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}</host>
> <host desc="Regex pattern of hostname to allow or deny." allow="true">172\.1[6789]\.[0-9]{1,3}\.[0-9]{1,3}</host>
> <host desc="Regex pattern of hostname to allow or deny." allow="true">172\.2[0-9]\.[0-9]{1,3}\.[0-9]{1,3}</host>
> <host desc="Regex pattern of hostname to allow or deny." allow="true">172\.3[01]\.[0-9]{1,3}\.[0-9]{1,3}</host>
> <host desc="Regex pattern of hostname to allow or deny." allow="true">192\.168\.[0-9]{1,3}\.[0-9]{1,3}</host>
> <host desc="Regex pattern of hostname to allow or deny." allow="false">192\.168\.1\.1</host>
>
>
> <max_file_size desc="Maximum document size in bytes to load. 0 for unlimited." type="uint">0</max_file_size>
>
> <locking desc="Locking settings">
> <refresh desc="How frequently we should re-acquire a lock with the storage server, in seconds (default 15 mins) or 0 for no refresh" type="int" default="900">900</refresh>
> </locking>
> </wopi>
>
> <ssl desc="SSL settings">
> <as_scheme type="bool" default="true" desc="When set we exclusively use the WOPI URI's scheme to enable SSL for storage">true</as_scheme>
> <enable type="bool" desc="If as_scheme is false or not set, this can be set to force SSL encryption between storage and coolwsd. When empty this defaults to following the ssl.enable setting"></enable>
> <cert_file_path desc="Path to the cert file" relative="false"></cert_file_path>
> <key_file_path desc="Path to the key file" relative="false"></key_file_path>
> <ca_file_path desc="Path to the ca file. If this is not empty, then SSL verification will be strict, otherwise cert of storage (WOPI-like host) will not be verified." relative="false"></ca_file_path>
> <cipher_list desc="List of OpenSSL ciphers to accept. If empty the defaults are used. These can be overridden only if absolutely needed."></cipher_list>
> </ssl>
> </storage>
did you format this message partially or does your file contain random ```'s ?
[08:56:04]
<saebaryo.xyz> I just copied and pasted it as it was.
[09:45:06]
<John88888> 6.64 wfB:/ 复制打开抖音，看看【老利探索的作品】请理性观看不喜勿喷！@老利说 # 探索发现 # 真... https://v.douyin.com/DWkj6kM/
[10:02:57]
<orhtej2> > <@saebaryo.xyz:matrix.org> In Nextcloud, this is the error I see in the logs:
>
> Error: simplexml_load_string(): Entity: line 60: parser error : Opening and ending tag mismatch: form line 47 and div at /var/www/nextcloud/apps/richdocuments/lib/WOPI/Parser.php#47
This is super cryptic to me.
What's supposed to happen is [DiscoveryManager](https://github.com/nextcloud/richdocuments/blob/main/lib/WOPI/DiscoveryManager.php#L75) is supposed to download mydomain.tld/hosting/discovery and parse it as XML. It clearly works for me (TM) on your site: https://office.yorili.com/hosting/discovery. But based on error message it gets SSO login page instead (line 47 is indeed a <form> tag there).
No clue why is that
[10:20:13]
<saebaryo.xyz> Thx for checking!
Someone wrote to check whitelists, how do to that?
[10:20:19]
<lapineige> > <@saebaryo.xyz:matrix.org> No and if I need to from where please?
don't, it doesn't work (there is an open issue on github about that)
[10:23:00]
<saebaryo.xyz> Ah so Collabora won't work with nextcloud for now right?
What would be the alernative app for that?
[11:18:53]
<eric_G> saebaryo.xyz: I am also able to access fullscreen with Chome...
[11:19:28]
<saebaryo.xyz> For me only on FF
[11:19:36]
<saebaryo.xyz> And other people as well strangely
[11:20:18]
<saebaryo.xyz> Can you try on my instance please? mytube.yorili.com
[11:23:42]
<eric_G> no problem with fullscreen for mytube.yorili.com
[11:28:48]
<saebaryo.xyz> Strange I still see it on Brave but not on FF 😕
[12:28:37]
<Chatpitaine Caverne> Chat lu,
Pour information, j'ai énormément galéré pour installer Collabora Onlne version ARM64 dans un Nextcloud sur Raspberry Pi.
Je me prenais des codes 50x dès l'activation de l'appli nextcloud Office.
Après moultes recherches, j'ai finalement trouvé où était le souci grâce à ce lien :
https://github.com/CollaboraOnline/richdocumentscode/issues/204#issuecomment-1517211152
Il suffit d'éditer le fichier : /etc/nginx/conf.d/MYCLOUD.MYDOMAIN.TLD.d/nextcloud.conf.
comme indiqué dans le lien.
[12:30:36]
<Aleks (he/him/il/lui)> wtf, why would they name differently their URL depending on architecture -_-
[12:38:30]
<Chatpitaine Caverne> > <@Alekswag:matrix.org> wtf, why would they name differently their URL depending on architecture -_-
En tout cas ça risque d'être accueilli comme une bonne nouvelle sur le forum de Yunohost.
[14:08:15]
<Chatpitaine Caverne> Non, c'est moi qui est recassé en faisant un essai.
[14:08:17]
<Chatpitaine Caverne> ça remarche.
[14:10:21]
<Chatpitaine Caverne> Désolé mauvaise conv'
[16:56:52]
<saebaryo.xyz> Salut a tous, si ya des francophones sur ce groupe qui ont deja installé/configuré Yunohost avec Invidious et Nextcloud avec Collabora ou Onlyoffice, j'aurais vrm besoin de votre expertise pour redsoudre qlq soucis, merci !
[17:05:59]
<saebaryo.xyz> Salut! Merci de ton retour d'experience!
Sur mon instance de Invidious, je n'arrive pas a avoir le plein ecran quand je clique dessus (seulement sur les nivagateurs a base Chromium), et sur Nextcloud je n'arrive pas a ouvir les fichiers alors que j'ai configure pratiquement tout ce qui etait configurable 😄
[17:06:55]
<saebaryo.xyz> Est ce qu'on peux se loguer sur Peertube et importer ses abonnements invidious ou YT par hasard? (Comment alternative a Invidious au cas ou).
[17:13:36]
<Chatpitaine Caverne> Bah pour invidious, je ne sais pas trop. Peut-être voir ta console de navigateur pour chercher les erreurs.
Sur Peertube, on importe nos vidéos soit depuis fichiers, soit depuis URL externe. Mais je n'ai pas vu de transferts d'abonnements.
Pour les fichiers Nextcloud, sont-ce des fichiers Collabora Online ?
Pendant longtemps, étant sur archi ARM64, je n'étais pas parvenu à installer Collabora avec mon nextcloud.
Quand installé, j'ai règlé mon "Allow list for WOPI requests" à ::1,127.0.0.1 c'est à dire localhost en IPv6 et IPv4.
[17:17:11]
<saebaryo.xyz> Merci de ton retour!
Je peux essayer de faire une nouvelle reinstallation de Invidious deja et apres je partage les logs de console.
Pour Peertube (dommage) :)
Concernant NC et Collabora, justement qlq m'avais aussi dit de voir du cote Allowlist mais je n'ai pas su cette info que tu m'a donne la au sujet de mettre le localhost. Je vais essaayer mnt.
[17:36:07]
<saebaryo.xyz> J'ai essaye pour Nexcloud et meme apres redemarrage du serveur meme chose.
Voici les logs de la console quand j'essaie d'ouvrir un docx par example:
The resource from “https://yorili.com/yunohost/sso/” was blocked due to MIME type (“text/html”) mismatch (X-Content-Type-Options: nosniff)
Et aussi:
Content Security Policy: The page’s settings blocked the loading of a resource at wss://office.yorili.com/cool/https%3A%2F%2Fyorili.com%2Fmycloud%2Findex.php%2Fapps%2Frichdocuments%2Fwopi%2Ffiles%2F77_och7d4n6fn8x%3Faccess_token%3DHAbo3prhKmtX5h9A22l0XvnzeUvDslzY%26access_token_ttl%3D1683344027000/ws?WOPISrc=https%3A%2F%2Fyorili.com%2Fmycloud%2Findex.php%2Fapps%2Frichdocuments%2Fwopi%2Ffiles%2F77_och7d4n6fn8x&compat=/ws (“default-src”).
[17:36:41]
<saebaryo.xyz> Ca a l'air vraiment un souci de whitelist a ce que je vois apparemment
[18:18:03]
<Chatpitaine Caverne> Pour partager les logs, le mieux est d'utiliser les fonctions yunopaste car elles enlèvent les données sensibles tels que nom de domaine, pwd, ...
[18:20:49]
<Chatpitaine Caverne> Que disent les journaux dans nextcloud ?
[18:24:35]
<saebaryo.xyz> Un moment
[18:31:40]
<saebaryo.xyz> Ya pas de logs pour cette erreur sur les logs de Nextcloud
[18:34:11]
<Chatpitaine Caverne> ```
sudo -u nextcloud /bin/php8.1 --define apc.enable_cli=1 /var/www/nextcloud/occ config:system:set loglevel --value=1
```
Bah je ne sais pas trop, désolé. Peut-être passer le log level à 1 et tenter des connections Collabora. Mais là je ne vois pas.
[18:35:15]
<saebaryo.xyz> Bonne idee, je vais essayer sinon je vais aussi installer Onlyoffice pour voir
[18:38:18]
<saebaryo.xyz> Voici l'erreur principale que je recoit maintenant:
The resource from “https://yorili.com/yunohost/sso/” was blocked due to MIME type (“text/html”) mismatch (X-Content-Type-Options: nosniff).
[18:38:39]
<saebaryo.xyz> Est ce une config MIME que je dois changer qlq part par hasard?
[18:41:40]
<Chatpitaine Caverne> Oui, mais je ne vois pas. N'ai jamais rencontré cela. Désolé.
[18:42:24]
<saebaryo.xyz> merci quand meme
[18:47:16]
<pti-jean> saebaryo.xyz, Tu t'adresses à qui ??? Je ne vois pas les messages... Pour moi tu fais un monologue !
[18:48:27]
<Chatpitaine Caverne> > <pti-jean> saebaryo.xyz, Tu t'adresses à qui ??? Je ne vois pas les messages... Pour moi tu fais un monologue !
à moi, tu ne me vois pas ?
[18:48:57]
<pti-jean> Si, mais que toi !
[18:49:09]
<Chatpitaine Caverne> Vu qu'on était en réponse, s'est passé en conversation dans mon client Matrix. Peut-être qqc à voir.
[18:50:03]
<pti-jean> Donc, y a un truc qui buggue
[19:04:25]
<jak73887> hi
[19:06:59]
<jak73887> pti-jean: hi
[19:07:40]
<saebaryo.xyz> surement alors
[19:10:49]
<jak73887> Hello, is there a wechat account for free?