# Document upload failed - Collabora-office in Nextcloud **URL:** \ **Category:** Installation & Configuration\ **Created:** [September 15, 2022, 10:08am UTC](https://forum.collaboraonline.com/t/document-upload-failed-collabora-office-in-nextcloud/1348 "2022-09-15T10:08:09Z")\ **Posts on this page:** 15\ **Page:** 1
**Author:** ![fgm](https://avatars.discourse-cdn.com/v4/letter/f/22d042/32.png) [@fgm](https://forum.collaboraonline.com/u/fgm)\ **Post date:** [September 15, 2022, 10:08am UTC](https://forum.collaboraonline.com/t/document-upload-failed-collabora-office-in-nextcloud/1348/1 "2022-09-15T10:08:09Z")
Hello. A few months ago I used an old laptop that was forgotten at home, and I installed a servidfor on debian 11. Web server and DNS server Then install nextcloud to make a private cloud and share photos, videos and documents with my family. We are only 7 users and my cloud works very well. Over time I decided to install an office tool and be able to edit documents online. I have installed Collabora-office and everything seems to be fine, yet I get errors when opening or creating documents. I have followed this installation guide, because I don’t want to use docker [Install Nextcloud 23 with Collabora and HPB on Debian 11 natively](https://fscene8.me/nextcloud-collabora-hpd-installation-guide/) When I do a certbot --apache I get this ```auto Requesting a certificate for collabora-office.miva.sytes.net Performing the following challenges: http-01 challenge for collabora-office.miva.sytes.net Waiting for verification... Challenge failed for domain collabora-office.miva.sytes.net http-01 challenge for collabora-office.miva.sytes.net Cleaning up challenges Some challenges have failed. IMPORTANT NOTES: - The following errors were reported by the server: Domain: collabora-office.miva.sytes.net Type: dns Detail: DNS problem: NXDOMAIN looking up A for collabora-office.miva.sytes.net - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for collabora-office.miva.sytes.net - check that a DNS record exists for this domain ``` It seems that I have problems with SSL certificates and what I have configured with cerbot is not correct. ---
**Author:** ![fgm](https://avatars.discourse-cdn.com/v4/letter/f/22d042/32.png) [@fgm](https://forum.collaboraonline.com/u/fgm)\ **Post date:** [September 15, 2022, 5:23pm UTC](https://forum.collaboraonline.com/t/document-upload-failed-collabora-office-in-nextcloud/1348/2 "2022-09-15T17:23:50Z")
Hello. At the moment that is already resolved and the SSL certificates have already been generated Change the name to a shorter one to [collabora-miva.sytes.net](http://collabora-miva.sytes.net) Now it won’t let me put the address [https://collabora-miva.sytes.net](https://collabora-miva.sytes.net) Yes, I can put [https://miva.sytes.net](https://miva.sytes.net) (which is the domain) It does not address and when I open an office file it tells me again “the document load has failed” i’m stuck ---
**Author:** ![wwe](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.collaboraonline.com/wwe/32/534_2.png) [@wwe](https://forum.collaboraonline.com/u/wwe)\ **Post date:** [September 16, 2022, 12:22pm UTC](https://forum.collaboraonline.com/t/document-upload-failed-collabora-office-in-nextcloud/1348/3 "2022-09-16T12:22:14Z")
> [@fgm](#): > > At the moment that is already resolved and the SSL certificates have already been generated > Change the name to a shorter one to [collabora-miva.sytes.net](http://collabora-miva.sytes.net) at his point you have to start from the beginning and generate fresh certificates, as TLS certificates always bind to a domain name, once you change the domain previous certificates become invalid. ---
**Author:** ![fgm](https://avatars.discourse-cdn.com/v4/letter/f/22d042/32.png) [@fgm](https://forum.collaboraonline.com/u/fgm)\ **Post date:** [September 16, 2022, 12:54pm UTC](https://forum.collaboraonline.com/t/document-upload-failed-collabora-office-in-nextcloud/1348/4 "2022-09-16T12:54:56Z")
I have already updated the certificates to the address [collabora-miva.sytes.net](http://collabora-miva.sytes.net) But the message “the document load has failed” continues. My server manages the domain through NOIP, because the IP is dynamic. And I also installed a DNS server; is it possible that you should add this subdomain? ---
**Author:** ![wwe](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.collaboraonline.com/wwe/32/534_2.png) [@wwe](https://forum.collaboraonline.com/u/wwe)\ **Post date:** [September 19, 2022, 7:21pm UTC](https://forum.collaboraonline.com/t/document-upload-failed-collabora-office-in-nextcloud/1348/5 "2022-09-19T19:21:51Z")
the integration of Nextcloud with Collabora is little demanding until you get the point how they belong together. Please review following post and work through referred material as well - this will provide good understanding of both integration and useful troubleshooting techniques. > **[Collabora/CODE not working with NC 24.0.3 in Docker](https://help.nextcloud.com/t/collabora-code-not-working-with-nc-24-0-3-in-docker/143324/2)** > > You find detailed example here: the referenced “green mark” in Nextcloud Office settings only shows the connection form Nextcloud to Collabora works, it doesn’t show reverse connection neither client to Collabora… see this post As I see you point... basically speaking the client must reach both servers using fqdn and both servers much reach each other using the **same** hostname as the client. very detailed drawing how to achieve this using local “split-brain” or “split-horizon” DNS server is here: > **[Yet another problem with Nextcloud Office/Collabora](https://help.nextcloud.com/t/yet-another-problem-with-nextcloud-office-collabora/134179/11?u=wwe)** > > I agree, given the fact item within “srv” are containers sharing the same docker network expose is good choice. In this sample you only need to include ports on reverse proxy and hide both applications within docker. ---
**Author:** ![fgm](https://avatars.discourse-cdn.com/v4/letter/f/22d042/32.png) [@fgm](https://forum.collaboraonline.com/u/fgm)\ **Post date:** [September 20, 2022, 8:46am UTC](https://forum.collaboraonline.com/t/document-upload-failed-collabora-office-in-nextcloud/1348/6 "2022-09-20T08:46:18Z")
The truth is that I am lost. The vhost is created and the diagnosis seems correct dig [collabora-miva.sytes.net](http://collabora-miva.sytes.net) ; \<\<\>\> DiG 9.16.27-Debian \<\<\>\> [collabora-miva.sytes.net](http://collabora-miva.sytes.net) ;; global options: +cmd ;; Got answer: ;; -\>\>HEADER\<\<- opcode: QUERY, status: NOERROR, id: 17753 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ; COOKIE: 5a8da3a1ba48f0cb01000000632970cd876e4c990d085858 (good) ;; QUESTION SECTION: ;[collabora-miva.sytes.net](http://collabora-miva.sytes.net). IN A ;; AUTHORITY SECTION: [sytes.net](http://sytes.net). 6 IN SOA [nf1.no-ip.com](http://nf1.no-ip.com). [hostmaster.no-ip.com](http://hostmaster.no-ip.com). 2095365172 600 300 604800 600 ;; Query time: 0 msec ;; SERVER: 192.168.1.100#53(192.168.1.100) ;; WHEN: Tue Sep 20 09:50:37 CEST 2022 ;; MSG SIZE rcvd: 141 But when I type the URL in the box, it tells me that it can’t connect to the Collabora Online server. my installation is not done with docker. It is a native debian 11 installation. I have used this guide > **[Install Nextcloud 23 with Collabora and HPB on Debian 11 natively](https://fscene8.me/nextcloud-collabora-hpd-installation-guide/)** > > This post will guide you on how to install Nextcloud with Collabora and the High-Performance backend for pushing Nextcloud notifications on Debian 11 server natively. No Docker, AppImages or Snap! Dashboard, Cloud Storage, Photos/Videos, Calendar,... ---
**Author:** ![fgm](https://avatars.discourse-cdn.com/v4/letter/f/22d042/32.png) [@fgm](https://forum.collaboraonline.com/u/fgm)\ **Post date:** [September 20, 2022, 2:39pm UTC](https://forum.collaboraonline.com/t/document-upload-failed-collabora-office-in-nextcloud/1348/7 "2022-09-20T14:39:58Z")
In principle the diagnosis of [collabora-miva.sytes.net](http://collabora-miva.sytes.net) is correct, and if I ping the result is positive. 64 bytes from [miva.sytes.net](http://miva.sytes.net) (192.168.1.100): icmp\_seq=1 ttl=64 time=0.208 ms 64 bytes from [miva.sytes.net](http://miva.sytes.net) (192.168.1.100): icmp\_seq=2 ttl=64 time=0.204 ms 64 bytes from [miva.sytes.net](http://miva.sytes.net) (192.168.1.100): icmp\_seq=3 ttl=64 time=0.193 ms 64 bytes from [miva.sytes.net](http://miva.sytes.net) (192.168.1.100): icmp\_seq=4 ttl=64 time=0.194 ms 64 bytes from [miva.sytes.net](http://miva.sytes.net) (192.168.1.100): icmp\_seq=5 ttl=64 time=0.198 ms 64 bytes from [miva.sytes.net](http://miva.sytes.net) (192.168.1.100): icmp\_seq=6 ttl=64 time=0.227 ms 64 bytes from [miva.sytes.net](http://miva.sytes.net) (192.168.1.100): icmp\_seq=7 ttl=64 time=0.203 ms ^C — [collabora-miva.sytes.net](http://collabora-miva.sytes.net) ping statistics — 7 packets transmitted, 7 received, 0% packet loss, time 6150ms rtt min/avg/max/mdev = 0.193/0.203/0.227/0.010 ms I think I’m close to the solution, but I can’t figure out what’s going on. ---
**Author:** ![fgm](https://avatars.discourse-cdn.com/v4/letter/f/22d042/32.png) [@fgm](https://forum.collaboraonline.com/u/fgm)\ **Post date:** [September 20, 2022, 4:25pm UTC](https://forum.collaboraonline.com/t/document-upload-failed-collabora-office-in-nextcloud/1348/8 "2022-09-20T16:25:25Z")
I have noticed that this warning appears in the nextcloud log Trusted domain error. “127.0.0.1” tried to access using “[collabora-miva.sytes.net](http://collabora-miva.sytes.net)” as host. Both the IP and the subdomain are mine, so I don’t understand why my cloud rejects the connection from collaboraoffice ---
**Author:** ![fgm](https://avatars.discourse-cdn.com/v4/letter/f/22d042/32.png) [@fgm](https://forum.collaboraonline.com/u/fgm)\ **Post date:** [September 20, 2022, 4:46pm UTC](https://forum.collaboraonline.com/t/document-upload-failed-collabora-office-in-nextcloud/1348/9 "2022-09-20T16:46:33Z")
I have added [collabora-miva.sytes.net](http://collabora-miva.sytes.net) in /var/www/nextcloud/config: ‘trusted\_domains’ =\> array ( 0 =\> ‘[miva.sytes.net](http://miva.sytes.net)’, 1 =\> ‘[collabora-miva.sytes.net](http://collabora-miva.sytes.net)’, ), ---
**Author:** ![wwe](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.collaboraonline.com/wwe/32/534_2.png) [@wwe](https://forum.collaboraonline.com/u/wwe)\ **Post date:** [September 25, 2022, 8:08pm UTC](https://forum.collaboraonline.com/t/document-upload-failed-collabora-office-in-nextcloud/1348/10 "2022-09-25T20:08:54Z")
> [@fgm](#): > > my installation is not done with docker it doesn’t matte how you install the systems - the mechanics behind the scenes are the same - client needs access to both system, each system requires access to the other. troubleshooting techniques described in referenced threads apply everywhere… > [@fgm](#): > > Trusted domain error. “127.0.0.1” tried to access using “[collabora-miva.sytes.net](http://collabora-miva.sytes.net)” as host. something is wrong when requests to `collabora-miva` arrive on your Nextcloud. > [@fgm](#): > > I have added [collabora-miva.sytes.net](http://collabora-miva.sytes.net) in /var/www/nextcloud/config: did this solved the issue? ---
**Author:** ![fgm](https://avatars.discourse-cdn.com/v4/letter/f/22d042/32.png) [@fgm](https://forum.collaboraonline.com/u/fgm)\ **Post date:** [September 27, 2022, 5:51am UTC](https://forum.collaboraonline.com/t/document-upload-failed-collabora-office-in-nextcloud/1348/11 "2022-09-27T05:51:29Z")
No. I’m still investigating what could happen. ---
**Author:** ![fgm](https://avatars.discourse-cdn.com/v4/letter/f/22d042/32.png) [@fgm](https://forum.collaboraonline.com/u/fgm)\ **Post date:** [September 28, 2022, 6:42am UTC](https://forum.collaboraonline.com/t/document-upload-failed-collabora-office-in-nextcloud/1348/12 "2022-09-28T06:42:13Z")
I wonder if the /etc/apache2/sites-available/collabora.conf file is correct? ![image](https://europe1.discourse-cdn.com/flex013/uploads/collaboraonline/original/1X/7b8076c0345a5a33375026bf41f1fc36fb296325.png) ---
**Author:** ![wwe](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.collaboraonline.com/wwe/32/534_2.png) [@wwe](https://forum.collaboraonline.com/u/wwe)\ **Post date:** [October 2, 2022, 7:42pm UTC](https://forum.collaboraonline.com/t/document-upload-failed-collabora-office-in-nextcloud/1348/13 "2022-10-02T19:42:09Z")
I’m not Apache expert but looks you are missing lot of required directives. take a look at this guide, it includes detailed Apache configs… > **[HowTo: Ubuntu + Docker + Nextcloud + Talk + Collabora](https://help.nextcloud.com/t/howto-ubuntu-docker-nextcloud-talk-collabora/76430)** > > 1.Overview This is a general guide to setting up a functional Nextcloud instance using Ubuntu Server 18.04.3, Docker CE, Docker-Compose, Collabora CODE, and an Apache reverse proxy. By the end (and as of writing), this setup will have an A+ rating on... or even better use official docs: > **[Proxy settings — SDK https://sdk.collaboraonline.com/ documentation](https://sdk.collaboraonline.com/docs/installation/Proxy_settings.html)** > > Collabora Online Proxy settings: reverse proxy (Apache or Nginx), load balancing (HAProxy or Nginx) ---
**Author:** ![fgm](https://avatars.discourse-cdn.com/v4/letter/f/22d042/32.png) [@fgm](https://forum.collaboraonline.com/u/fgm)\ **Post date:** [October 11, 2022, 9:46am UTC](https://forum.collaboraonline.com/t/document-upload-failed-collabora-office-in-nextcloud/1348/14 "2022-10-11T09:46:41Z")
I have checked the vhost files in apache, and they seem correct. SSL certificates are fine. I have added my collabora server in the collabora office box and it has been accepted. However when I try to open any file, I continue to have the same problem “document upload failed” Any new idea? Is it necessary to add a DNS record in my nameserver? ---
**Author:** ![fgm](https://avatars.discourse-cdn.com/v4/letter/f/22d042/32.png) [@fgm](https://forum.collaboraonline.com/u/fgm)\ **Post date:** [October 14, 2022, 8:52am UTC](https://forum.collaboraonline.com/t/document-upload-failed-collabora-office-in-nextcloud/1348/15 "2022-10-14T08:52:27Z")
Fixed adding CNAME record to DNS server