Nextcloud Office and Built-in CODE Server

Hello

After a little break I started an other atempt to install Office and Built-in Code Server on my Nitrokey NextBox.

Operating System: Linux 5.10.103-v8+ aarch64
CPU: Raspberry Pi 4 Model B Rev 1.5 (4 threads)
Nextcloud: Nextcloud Hub 8 (29.0.11)

I still get the same error message: Failed to connect to the remote server: cURL error 28: Operation timed out after 5001 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://ck-waldm19c.dedyn.io:61028/custom_apps/richdocumentscode_arm64/proxy.php?req=/hosting/discovery


curl -v https://ck-waldm19c.dedyn.io:61028/custom_apps/richdocumentscode_arm64/proxy.php?req=/hosting/discovery

* Trying 2001:1680:5872:1400:91e2:1f23:aae7:42ad:61028...

* connect to 2001:1680:5872:1400:91e2:1f23:aae7:42ad port 61028 failed: Connection refused

* Trying 82.220.113.200:61028...

* Connected to ck-waldm19c.dedyn.io (82.220.113.200) port 61028 (#0)

* ALPN, offering h2

* ALPN, offering http/1.1

* successfully set certificate verify locations:

* CAfile: /etc/ssl/certs/ca-certificates.crt

* CApath: /etc/ssl/certs

* TLSv1.3 (OUT), TLS handshake, Client hello (1):

* TLSv1.3 (IN), TLS handshake, Server hello (2):

* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):

* TLSv1.3 (IN), TLS handshake, Certificate (11):

* TLSv1.3 (IN), TLS handshake, CERT verify (15):

* TLSv1.3 (IN), TLS handshake, Finished (20):

* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):

* TLSv1.3 (OUT), TLS handshake, Finished (20):

* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384

* ALPN, server accepted to use http/1.1

* Server certificate:

* subject: CN=ck-waldm19c.dedyn.io

* start date: Mar 7 03:27:20 2025 GMT

* expire date: Jun 5 03:27:19 2025 GMT

* subjectAltName: host "ck-waldm19c.dedyn.io" matched cert's "ck-waldm19c.dedyn.io"

* issuer: C=US; O=Let's Encrypt; CN=R11

* SSL certificate verify ok.

> GET /custom_apps/richdocumentscode_arm64/proxy.php?req=/hosting/discovery HTTP/1.1

> Host: ck-waldm19c.dedyn.io:61028

> User-Agent: curl/7.74.0

> Accept: */*

>

* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):

* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):

* old SSL session ID is stale, removing

* Mark bundle as not supporting multiuse

< HTTP/1.1 200 OK

< Date: Wed, 16 Apr 2025 12:34:50 GMT

< Server: Apache/2.4.62 (Debian)

< Strict-Transport-Security: max-age=63072000

< Referrer-Policy: no-referrer

< X-Content-Type-Options: nosniff

< X-Frame-Options: SAMEORIGIN

< X-Permitted-Cross-Domain-Policies: none

< X-Robots-Tag: noindex, nofollow

< X-XSS-Protection: 1; mode=block

< Upgrade: h2

< Connection: Upgrade

< X-Powered-By: PHP/8.2.27

< Content-Length: 17

< Content-Type: text/html; charset=UTF-8

<

ERROR ! No error

* Connection #0 to host ck-waldm19c.dedyn.io left intact

What I do understand, is that the connection is refused, but why and how to solve the problem is unclear to me. Any help would be appreciated.

@kr1979 can you be clearer about your coolswd configuration. there are two options here:

  1. collabora handles termination
ssl.enable=true or false         # enable/disable collabora/coolswd ssl termination
  1. reverse proxy handles termination:
ssl.termination=true or false     # enable/disable reverse proxy ssl termination

why are there two handshakes? this is probably your issue…

assuming you’re not using a reverse proxy but rather letting collabora do the SSL thing: coolswd should be configured like ssl.enable=true and ssl.termination=false that’s because there can only be one SSL terminator.

alternatively, assuming you have a reverse proxy handling the termination, coolswd termination would be disabled like ssl.enable=false and ssl.termination=true

see How to install & configure Collabora CODE with Docker

I’m afraid I don’t know there are two handshakes. Is there something I can do against that?

/etc/coolwsd/coolwsd.xml does not exist.

oh boy… I jumped the gun and over read those specs, sorry :grimacing:

I have no idea how Nitrokey NextBox handles their instances

their FAQ’s say they don’t support Office see Nextcloud FAQ - Nitrokey Documentation

consider the snap, works on ARM too How to install Nextcloud snap