# Infinite loading screen, Collabora Nextcloud

**URL:** <https://forum.collaboraonline.com/t/infinite-loading-screen-collabora-nextcloud/1400>\
**Category:** Uncategorized\
**Created:** [October 6, 2022, 11:23am UTC](https://forum.collaboraonline.com/t/infinite-loading-screen-collabora-nextcloud/1400 "2022-10-06T11:23:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kollala](https://avatars.discourse-cdn.com/v4/letter/k/ce73a5/32.png) [@kollala](https://forum.collaboraonline.com/u/kollala)\
**Post date:** [October 6, 2022, 11:23am UTC](https://forum.collaboraonline.com/t/infinite-loading-screen-collabora-nextcloud/1400/1 "2022-10-06T11:23:45Z")

</div>

PHP 7.4  
Nextcloud 24.0.5  
I tried to switch from OnlyOffice to Collabora, as the community document server of OnlyOffice has sooo many bugs.  
I installed the Nextcloud Office app and the Collabora Online - Built-in CODE Server app. In the nextcloud settings page it shows that the server can be reached. But when trying to open a document, I´m getting an infinite loading screen and no error message.

Any ideas where I could even start looking for the problem?

error\_log\_apache tells this

```auto
[Wed Oct 05 11:29:10 2022] [error] [pid 23427] mod_proxy_fcgi.c(1006): (70007)The timeout specified has expired: [client 87.132.0.0] AH01075: Error dispatching request to : (polling)

```

---

<div class="post-metadata">

**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 9, 2022, 8:10pm UTC](https://forum.collaboraonline.com/t/infinite-loading-screen-collabora-nextcloud/1400/2 "2022-10-09T20:10:42Z")

</div>

take a look at this drawing and related threads:

> **[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.

basically:

> You should have both Nextcloud and Collabora having valid DNS names (which is prerequisite for TLS). All this names should exist in DNS and be resolvable by each component - client Nextcloud server and Collabora **must** resolve all the DNS names to the right ip (your real server ip in this case as 127.0.0.1 might be not the right one especially if you use some virtualization)

> [@Question about required DNS configuration for collabora with nextcloud integration?](https://forum.collaboraonline.com/t/question-about-required-dns-configuration-for-collabora-with-nextcloud-integration/1233/2):
>
> You should have both Nextcloud and Collabora having valid DNS names (which is prerequisite for TLS). All this names should exists in DNS and be resolvable by each component - client Nextcloud server and Collabora must resolve all the DNS names to the right ip (your real server ip in this case as 127.0.0.1 might be not the right one especially if you use some virtualization) You can refer to Nextcloud forum where I posted some drawings and references: