Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Connection Loss" – file download is offered instead opening office editor until reapplying app configuration #3709

Open
4001982248998 opened this issue May 22, 2024 · 3 comments

Comments

@4001982248998
Copy link

4001982248998 commented May 22, 2024

Description
Connection to a Collabora (Nextcloud Office) service running as docker container is setup and working. But after a few hours, when clicking on an odt file, a download dialogue opens instead of Collabora.

It is, however, able to start the office editor by using the three-point-menu and then choosing "edit in Nextcloud Office"!

Access to the Nextcloud Office app is limited to a certain user group. That is configured in Nextcloud's app administration page.

To Reproduce
Steps to reproduce the behavior:

  1. Setup Collabora connector in Nextcloud, confirm it's working
  2. Wait a few hours, maybe logoff from Nextcloud
  3. Click on an office document
  4. A file download dialogue will open. Bad!
  5. Go to Nextcloud's App configuration and reapply the Collabora connection
  6. Click on an office document
  7. Now Collabora opens again

Expected behavior
After clicking on an office document, Collabora office should start always, not only after reapplying the connection.

Server details

  • Operating system: Ubuntu
  • Web server: Apache2
  • Database: MariaDB
  • PHP version: 8.1
  • Nextcloud version: 28.0.5
  • Version of the richdocuments app: 8.3.7
  • Version of Collabora Online: Collabora Online Development Edition 24.04.1.3 89a7742 or Collabora Online Development Edition 24.04.3.1 594b605
  • Configuration of the richdocuments app
{
    "apps": {
        "richdocuments": {
            "disable_certificate_verification": "",
            "edit_groups": "collabora-test",
            "enabled": "yes",
            "external_apps": "",
            "installed_version": "8.3.7",
            "public_wopi_url": "https:\/\/my.host.com",
            "types": "prevent_group_restriction",
            "use_groups": "collabora-test",
            "wopi_allowlist": "my-host-ip\/32",
            "wopi_url": "https:\/\/my.host.com"
        }
    }
}

@Niemand112233
Copy link

Have the same problem on NC 29.0.1 and a dedicated collabora instance (which is working on another NC), but I can't get it back to work.

@joshtrichards
Copy link
Member

Can you check your Nextcloud log during the time window between it working and stopping working? I suspect you'll have some errors there. Possible saying "Failed to fetch [...]" or similar.

@juliushaertl
Copy link
Member

This might be addressed by #3749 which makes the cached response if the Collabora server is setup permanent and no longer expiring if the background fetch fails

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants