#13619 closed Bug/Something is broken (fixed)

Collabora via NextCloud isn't working

Reported by: Jamila Khan Owned by: Jamie McClelland
Priority: High Component: Tech
Keywords: Cc:
Sensitive: no


I am attempting to open documents on share.mayfirst.org for editing, and I get:

504 Gateway Time-out

The URL I just attempted is: https://share.mayfirst.org/apps/files/?dir=/Palante%20Tech%20Shared/Current%20Clients%20and%20Projects/Borealis%20Philanthropy/TMF/YWU&fileid=3104483

Change History (11)

comment:1 Changed 12 months ago by Jack Aponte

Priority: MediumHigh

Yup, I'm experiencing the same thing when I navigate to a different password-protected shared LibreOffice spreadsheet on share.mayfirst.org; the 504 error appears after I enter the password on the authentication page. We have many clients interacting with spreadsheets via Collabora instead of Google Docs so it feels important to get this resolved soon if possible!

comment:2 Changed 12 months ago by JaimeV

Owner: set to Jamie McClelland
Status: newassigned

Oh no, just saw this. Not sure how to restart collabora separately. Copying jamie here.

comment:3 Changed 12 months ago by Jamie McClelland

The docker instance was running, but had a lot of error messages, including:

wsd-00026-02804 15:34:50.133168 [ docbroker_11f ] WRN  Attempted ping on non-upgraded websocket!| ./net/WebSocketHandler.hpp:280
kit-02784-02793 15:35:01.233516 [ lokit_11e ] ERR  No socket associated with WebSocketHandler 0x0x919be60| ./net/WebSocketHandler.hpp:100
wsd-00026-02791 15:35:01.468349 [ docbroker_11e ] ERR  getJSONValue: Invalid access: Can not convert empty value.| wsd/Storage.cpp:385
wsd-00026-02791 15:35:02.243545 [ docbroker_11e ] WRN  Client session [1b26] not found to forward message: o1793036 invalidatetiles: part=0 x=4140 y=2025 width=32208090 height=255| wsd/Documen

I've restarted docker and it seems to be working now, but not sure what happened. Still investigating.

comment:4 Changed 12 months ago by Jamie McClelland

It looks like this problem is experienced by others. I found an unanswered question on the nextcloud forum as well as an issue posted against both the richdocuments Nextcloud plugin as well as the collabora image.

The good news: It seems the solution is to simply restart the docker image after the first time it is started. The bad news is that there is no follow up to the tickets :(.

comment:5 Changed 12 months ago by Jamie McClelland

Another posts suggests it has to be restarted every 4 to 5 days.

comment:6 Changed 12 months ago by Jack Aponte

Thanks for following up on that, Jamie! At least from the sounds of it this won't happen again now that the Docker has been started more than once? How weird!

comment:7 in reply to:  5 Changed 12 months ago by Jack Aponte

Replying to https://id.mayfirst.org/jamie:

Another posts suggests it has to be restarted every 4 to 5 days.

Oh geez, every 4-5 days, not so cute, but perhaps can be automated? Ugh!

comment:8 Changed 12 months ago by JaimeV

What's the correct way to restart the docker image jamie?

comment:9 Changed 12 months ago by Jamie McClelland

You can restart with:

  • docker stop nextcloud-collabora
  • docker start nextcloud-collabora

You can also see running docker instances with:

docker ps

And, more documentation here.

comment:10 Changed 12 months ago by Jamie McClelland

Resolution: fixed
Status: assignedfeedback

I just completed the Nextcloud 13.1 upgrade (and also rebooted the server).

I tested online editing via collabora and it worked perfectly (with everyting auto starting).

Just to be safe I have once again restarted the docker image.

Still seems to be working... but please let us know if you experience any problems.

comment:11 Changed 12 months ago by automatic

Status: feedbackclosed

No news is good news (we hope)! Given the lack of feedback, we think this ticket can be closed.

Please login to add comments to this ticket.

Note: See TracTickets for help on using tickets.