and both are gray cant edit …
Document Editing Service address for internal requests from the server
is emty
Server address for internal requests from the Document Editing Service https://sub.domain.de/nextcloud/
Than i try do install it with dynamic internet adress (like DYNDNS service) the route renew the DNS with the new IP4
Second try was ADSL need 10 trys to intall it. At the first day war running next day (fresh IP) no Onlyoffice.
Yesterday i ty my Home server with a VDSL dynamic IP and DYNDNS service. First try was sucessfull and it is running. New day no Onlyoffice from external (SOGo and Nextcloud running no certificate Errros with the Browser)
I get this error
Fehler beim Anschließen (cURL error 51: Unable to communicate securely with peer: requested domain name does not match the server’s certificate. (see http://curl.haxx.se/libcurl/c/libcurl-errors.html))
Now from my homenetwork Onlyoffice is running but external is a errormassage …
I will send a hallo from new MaskLand … Burkas for everybody ;-)… I klie to change my toiletpapper bay to human rigths
I do the same work with all servers …
Building a letsencrypt setificate for the subdomain sub.domain.de and let it be default.
HTTPS is fine with with all server Web, SOGo, nextcloud. All kind of browsers are “green”
From the Routes (three times AVM Fritzboxes 7490/7590) the ports 443, 80 a routed to the Nethserver.
so it looks like certificate is okay…
one server is behind a VSDL with fix IP… need a littel bit of time than this server is running with the combination of Nextcloud and Onlyoffice.
one server is behind a ADSL with Dynamic IP. DNS for subdomain is a DYNDNS servive like selfhost…
my Server is sitting behind VDSL with dynamic IP, and a Strato DYNDNS service.
On th the installation day my server is running well, next day with a new IP Onlyoffice is not working from external, but internal. So i am take a view for setting in the Onlyoffice in Nextcloud there was a IP not the SubDomain. Than i try to change Internal IP Nethserver to the subdomain and this is the error
Fehler beim Anschließen (cURL error 51: Unable to communicate securely with peer: requested domain name does not match the server’s certificate. (see libcurl - Error Codes))
But i will try it step by step again …
Did you think the letsencrypt is okay ?
I still didn’t find time to the test the internal onlyoffice but I’ll do it asap.
You may check config files or Nextcloud onlyoffice settings for ip addresses and change them to FQDN to make it work but it’s just a guess.
thx for you help and it show the rigth direction. My homeserver is now fixt…
The solution is very easy and crasy to.
Frist → setur the route to redirct the ports 80, 443 to my netserver (internal IP)
second-> letsencrypt certificate must installd and be default!!! (but it was)
third-> I am installing Nextcloud (without onlyoffice) and including the TrustedDomains
with
We can use Nextcloud form external and internal. (looks like perfect)
Than i am folowing the instruction to Instlla Onlyoffice (its the connector) and the comuninty documentserver.
Try it internal !! it is running…
try it external fine
Brake → one beer → and a lill bit of sleep
Nextday try it again oh not nice not working …
Login as admin (Nextcloud) [not aktivate the Neth admin user] moving to setup → Onlyoffice
and try to change IP with FQDN (sub.domain.de)
try to change internal too cant change it …
save it wir the error …
but it will be saved …