• Support

  • Nextcloud - stalls on document creation/open

I've tried running this down on the Nextcloud forums as well. I have installed Collabora and Nextcloud Office on my Nextcloud instance, and while I can create, open and edit documents on the Nextcloud test site, when I try it on my own Opalstack install, documents "stall out" upon creation / open.

The creation dialogue takes me through the create/name/choose a template dialogue, but then it's a "forever circle" where the opening of the document never completes. The same "forever circle" when I try to open an existing document (including but not limited to the documents created through the above process).

Wondering if this is something I need to deal with on this hosting end instead of an issue with Nextcloud itself. I'm very low-level in tech expertise, but when I try to look at the console it seems to return tons of "sync" and "notification" commands... screenshot at https://imgur.com/a/lbG8Dub.

  • sean replied to this.

    MattShepherd I was able to reproduce this on my own install but I'm not sure of the cause. I'll reply here if I'm able to find anything out.

    We can't increase the web server timeout at the moment so if this is urgent then you might try a manual Nextcloud install which runs on its own Nginx server where you'd be able to tweak timeouts in the web server config.

      Not urgent -- just trying to ease into Nextcloud from Google over a long holiday weekend here in Canada. Let me know if you find anything out.

      • sean replied to this.

        MattShepherd Looks like there are a couple of problems:

        • The script proxy.php mentioned in the error message is trying to modify a file in the system /tmp directory in a manner that's not allowed. The solution would be to set upload_tmp_dir in your .user.ini but in my tests that setting was ignored. I worked around it by editing proxy.php to set the tmp path to a location in my home directory.
        • That let Collabra move on a bit further, but the binary app image that it uses doesn't seem to be compatible with CentOS 7 so it couldn't run.

        The first issue needs bit more troubleshooting to figure out why upload_tmp_dirisn't working, for the second issue we're looking into building a local install of Collabra so that the app image won't be necessary.

            sean Thanks, Sean. This is all a bit out of my depth, so if there's something I should do that would help, please let me know, but for now I'm just seeing what comes of the exploration (and I appreciate this!).

            • sean replied to this.

                MattShepherd You're very welcome! We want you guys to be able to use Nextcloud's office features with as little friction as possible so we're working to make that happen 🙂

                I'll follow up here when I've got some progress to report. Thanks for your patience!

                  sean The first issue needs bit more troubleshooting to figure out why upload_tmp_dir isn't working

                  This part is by design - PHP only allows upload_tmp_dir to be set via the main system php.ini, so we're not able to set that per-user (I forgot that I already knew this 🤣). I don't think it will be an issue once we've got a standalone Collabra server running.

                    a month later

                    Still not a high-pressure issue, but just wondering if you'd gotten a chance to poke at the standalone Collabra server yet -- I could also try the manual install you link to above, but it's about 20% beyond my comfort zone so I was kind of being lazy and hoping that the Opalstack team might be able to whack away at this.

                    • sean replied to this.
                      5 months later
                      a year later

                      sean sorry the poke, just to say the Collabora server would be amazing for us. 🙂 pls don't give up. 😃

                      • sean replied to this.
                          Mastodon