Nextcloud Office Not Working

ℹ️ Support
, , , , , ,
1
Support intro

Sorry to hear you’re facing problems :slightly_frowning_face:

help.nextcloud.com is for home/non-enterprise users. If you’re running a business, paid support can be accessed via portal.nextcloud.com where we can ensure your business keeps running smoothly.

In order to help you as quickly as possible, before clicking Create Topic please provide as much of the below as you can. Feel free to use a pastebin service for logs, otherwise either indent short log examples with four spaces:

Or for longer, use three backticks above and below the code snippet:

longer
example
here

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can :heart:

Nextcloud version (eg, 29.0.5): 30.0.0
Operating system and version (eg, Ubuntu 24.04): Linux 6.6.44-production+truenas x86_64
Apache or nginx version (eg, Apache 2.4.25): I have no idea where I can find this information for I just clicked "Install" in the TrueNAS Apps.
PHP version (eg, 8.3): I have no idea where I can find this information for I just clicked "Install" in the TrueNAS Apps.

The issue you are facing:

Is this the first time you’ve seen this error? (Y/N): y

Before all I have to mention that I’m running TrueNAS 24.10, a RC version in which docker-compose replaces K3S.

Steps to replicate it:

  1. Install Nextcloud in TrueNAS
  2. Install Collabora in TrueNAS ( I changed two Extra Parameters: --o:ssl.enable=false --o:ssl.enable=false )
  3. Connect them in shell via
docker network create office
docker network connect office ix-nextcloud-1-nextcloud-1
docker network connect office ix-collabora-collabora-1

4.Set up Nextcloud as shown below

image
image1920×1080 364 KB

5.Open up one of the documents and it acts like ↓
image
image1920×1080 211 KB

The output of your Nextcloud log in Admin > Logging:
There is one error message continuously popping up but I don’t know if it is related to my question. I’ll paste the log anyway.

[no app in context] Error: image not found: image:apps/whiteboard.svg webroot: serverroot:/var/www/html
	GET /ocs/v2.php/apps/notifications/api/v2/notifications?format=json
	from 240c:c283:4001:7b9:c4a4:dd08:d462:a89b by zykerman at 2024年10月15日 08:08:24

The output of your config.php file in /path/to/nextcloud (make sure you remove any identifiable information!):

Screenshot_20241015-092530
Screenshot_20241015-0925301600×2560 246 KB

The output of your Apache/nginx/system log in /var/log/____:

There seems to be nothing in these log files.

Output errors in nextcloud.log in /var/www/ or as admin user in top right menu, filtering for errors. Use a pastebin service if necessary.

There are only two folders ( html and www ) in /var/www/.
2

your CODE address is wrong - this must be public FQDN running with TLS (same as Nextcloud)

Please review Collabora integration guide for details

3

According to the warning, you have not configured the WOPI list in the Office settings. Enter permitted hosts there. You may be able to test with 0.0.0.0/0

4

I see, but I won’t be able to get an available domain in the near future.

5

I’ll try to configure that. Are there any documents available?

6

I have a domain but I can only get a public ipv6 address. Therefore I set up a docker network to bind my nextcloud and CODE and entered my CODE server domain as

http://ix-collabora-1-collabora-1:9980

.
However, I see from this page that this may cause communication failure, for example a green check in the administration panel but failing to actully open a document, which is exactly my case. Is there any solutions to this?

7

I have IPv4 so I can’t say for sure IMHO Nextcloud and CODE could operate using IPV6 only.

But the requirement remains the same - CODE must be accessible from the client and cloud. You can have another FQDN like https://code.mydomain.tld or you can host it on a path like 'https://mydomain.tld/code/hosting/…` once you can reach /discovery and /capabilities endpoints from the client and cloud document editing should work.

8

image
image1432×737 47.9 KB

Are there any chance that I can change the link here? It should be

https://ix-nextcloud-1-nextcloud-1/

to establish the connection between the CODE server container and the nextcloud container.

9

the message is clear: “Determined from the browser URL” - if you would access your cloud using this URL it would be shown there but this is definitely not what you you need.

  • technically it could work
  • but you can not acquire public TLS certificates for internal names
  • this address would be accessible within your LAN only - only people from this network could use Office…
10

Do you use a Reverse Proxy? If you do, you don’t need to pay attention to IPv4 or IPv6. For instance, if you run a reverse proxy on your docker host, that has both IP’s (4&6) and someone with just a IPv6 address tries to connect to your Nextcloud, the reverse proxy will serve it, even if your docker network is purely IPv4. The good news is, that you do not take care of the IP-Protocol.

Caddy as a reverse proxy is easy to set up and supports different deployment cases.

11

I am using a reverse proxy, yes, but it only works when I try to access the container from the outside (eg from my school network to nextcloud). If I try to access an ipv6 address from nextcloud, it itself needs the access to ipv6, or an error message CANNOT REACH will appear. :upside_down_face:

12

by default Docker doesn’t enable IPv6 and for this reason containers could not access IPv6-only resources. but you can enable ipv6 it and it works. In my installation I use IPv6 - but only internally as I don’t have external network for test utilizing IPv6 now. I only can confirm both NC and CODE container are capable to access each other using IPv6 (see curl examples below)

check out:

13

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.