I am able to curl from the nextcloud server to the documentserver without any errors and without turning off validation with -k or similar flags. I have solved this problem by created a new self signed certificate for documentserver with SAN and CN properly present and adding this certificate on the nextcloud server to the openssl trusted certificates which solved the problem. Both use ssl and have self signed certificates of their own.įirst problem was that Nextcloud could not use curl on the documentserver due to a self signed certificate missing a Common Name field. (please let me know if you would like to see any apache config files or similar).ĭocument server is running inside its own VM, on stock debian 10 stable, the welcome page displays correctly, all the installation steps (from the onlyoffice help center instructions for linux installation) completed successfully - all the relevant packages are managed by apt and documenserver itself was installed using apt after dependencies where already installed (postgre etc.).īoth servers have their local domain names resolved inside the lan, can ping each other, can ssh into each other. Nextcloud is running inside its own VM, on stock Debian 10 stable, everything seems to be nominal including https. No other things are displayed on the nextcloud page, the connector is never enabled due to this error. This issue is similar to another one currently opened however I thought it would be better to open a new one given the other has stalled. When attempting to save settings to connect onlyoffice document server with nextcloud using the connector app I get the following error:
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |