Nextcloud Office - Fails with different documents

User Support
1

Hello,

First I wanna tell you what kind of environment I have so you have a better feeling for what I did wrong.

I am using a Cloudron Instance to host the Nextcloud App and the Collabora Office Suite. (Both connected.)

The first problem is with an older .odt - File. When I opened it with Nextcloud Office, it gets into the Collabora Interface. But it won’t finish loading and gets into a loop. In the top left corner appears the message admin (in that case me) disconnected. But it tries to connect again which ends in another disconnect. This problem was “fixed” by changing smth with our added fonts. DroidSans, DroidSerif, NunitoSans and OpenSans. When we removed all of them. It seemed to work fine. When I just added DroidSerif, the header wasn’t loading. This problem didn’t change and it didn’t matter if I put NunitoSans and OpenSans in the fonts directory. BUT. The DroidSans. When I added this, with the other or alone. It caused the Session_closed…connect…Session_closed loop. So any ideas on why this font caused a bug like this? Or even more interesting why it works totally fine without all the fonts, but when I add DroidSerif part of it can’t get loaded. It is all so confusing to me.

Second file that causes problems is a .docx - File. Usually it worked fine. But yesterday there was a file that tries to connect two times and then just stops. In the console it repeats the same warning. But the most important is the error that comes in the console when you try to open the file.

Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”).
Source: event.preventDefault()

I tried to configure the CSP for the Nextcloud. But it didn’t change something. I don’t know how to configure it for the Collabora Suite (Cloudron App). + it doesn’t even work with the Collabora Built-In (CODE) Server. So I am kinda lost. And as a trainee and some hours of trying to fix it. I really just wish that there is a solution or something I just wasn’t thinking about.

If there is anything that you experienced and fixed, let me know so I can try it.
:slight_smile: Let me know if you can help!

2

Hey @lassgutsein,

Welcome to the forum + thanks for the post! :slight_smile:

I am using a Cloudron Instance to host the Nextcloud App and the Collabora Office Suite. (Both connected.)

Great, great. This helps, but could we get a little more info?

Like:

  • Which OS are you using?
  • What versions of Nextcloud/Collabora are you using?

I don’t know how to configure it for the Collabora Suite (Cloudron App). + it doesn’t even work with the Collabora Built-In (CODE) Server.

Hmmm… So, if I’m understanding correctly:

  • Cloudron + Collabora Suite (= Nextcloud + Collabora) = your initial troubles.

Did you install it following the instructions here?

Looks like Cloudron may have their own little subforum also:

where people are discussing a few Cloudron-specific setup/questions.

The first problem is with an older .odt - File. When I opened it with Nextcloud Office, […] But it won’t finish loading and gets into a loop. […] This problem was “fixed” by changing smth with our added fonts.

Hmmmm. So where/how are you “adding/removing the fonts”?

And if I’m understanding you correctly:

  • Default Nextcloud+Collabora installation, a specific ODT document doesn’t load.
  • You remove ALL fonts.
  • ODT loads fine.

Now, as you’re introducing the fonts back, one-by-one:

  • DroidSerif

causes weird connect/disconnect issues?

(And other ODT documents work okay? No disconnect problems?)

Second file that causes problems is a .docx - File. […] But the most important is the error that comes in the console when you try to open the file.

Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”).

Hmmmm… Doing a search for that error, I’m running across a few things from a few years ago.

Back in 2021, this user’s was solved by doing an upgrade:

And this user had some:

and eventually got it working with some technical (HTTPS request header) stuff.

Unsure if those would be your solution though. (Making sure you’re on latest Collabora wouldn’t hurt though!)

So I am kinda lost. And as a trainee and some hours of trying to fix it. I really just wish that there is a solution or something I just wasn’t thinking about.

Heh, hopefully it was just some silly setting you forgot to flip or some setup instruction you skipped. :slight_smile: