Hello everyone,
-
I have an ONLYOFFICE Document Server v.5.5.0 installed on Ubuntu 18.04 TLS
as the following instructions:
https://helpcenter.onlyoffice.com/server/linux/document/linux-installation.aspx -
After that Nginx configured to use Self-Signed SSL/TLS Certificate as the
following instructions:
https://hostadvice.com/how-to/how-to-configure-nginx-to-use-self-signed-ssl-tls-
certificate-on-ubuntu-18-04-vps-or-dedicated-server/ -
Finally Document Server switched to HTTPS protocol as the following intructions:
https://helpcenter.onlyoffice.com/server/linux/document/switch-to-https.aspx -
There is another Nextcloud server v17.0.3.1 installed on Ubuntu 18.04 TLS as the
following instructions:
1- sudo snap install nextcloud
2- sudo ufw allow 443/tcp
3- sudo nextcloud.enable-https self-signed -
I want to integrate the two servers to be able to create Docs, Sheets & Slides
from Nextcloud side. -
ONLYOFFICE connector app has been downloaded and enabled from the
Nextcloud official store. -
Because of using a self signed certificate with ONLYOFFICE Document Server, I
added the bellow section to Nextcloud config.php as the following instructions:
1- cd /var/snap/nextcloud/19299/nextcloud/config/
2- sudo nano /var/snap/nextcloud/19299/nextcloud/config/config.php
3- Adding the bellow section on config.php file before the last );
‘onlyoffice’ => array ( ‘verify_peer_off’ => TRUE, ), -
But while trying to add ONLYOFFICE Document Server ip address with https in
onlyoffice setting this error occured:
GetConvertedUri on check error: Error occurred in the document service: Error
while downloading the document file to be converted. -
After that checked the connection between Document server and Nextcloud
servers from Nextcloud side and the result here:
administrator@ubuntu:~$ wget 192.168.1.8
–2020-03-18 14:37:20-- http://192.168.1.8/
Connecting to 192.168.1.8:80… connected.
HTTP request sent, awaiting response… 301 Moved Permanently
Location: https://192.168.1.8/ [following]
–2020-03-18 14:37:20-- https://192.168.1.8/
Connecting to 192.168.1.8:443… connected.
ERROR: cannot verify 192.168.1.8’s certificate, issued by ‘emailAddress=admin@192.168.1.8,CN=192.168.1.8,OU=Textiles,O=Tadweer,L=Sa
dat City,ST=Monofia,C=EG’:
Self-signed certificate encountered.
To connect to 192.168.1.8 insecurely, use `–no-check-certificate’. -
What should I do for now?