Unable to enable OnlyOffice connector in fresh Nextcloud AIO install (endless loop)

ℹ️ Support 📦 Appliances (Docker, Snappy, VM, NCP, AIO)
, , , ,
1

Hi everyone,

I’m facing a critical issue with the OnlyOffice connector in a fresh installation of Nextcloud AIO (Docker), without restoring any data or previous apps.

:compass: Environment

  • Platform: Synology NAS DS920+ (DSM 7.2)
  • Setup:
    • Clean install of Nextcloud AIO
    • Standalone container of onlyoffice/documentserver:latest via Portainer
    • Reverse proxy configured via DSM with a valid Let’s Encrypt certificate
    • Public domain: https://office.lann.es
  • Connection: via public HTTPS only
  • JWT Secret: identical on both sides (env var + UI input)

:white_check_mark: What works

  • Access to https://office.lann.es works from any browser
  • /healthcheck returns true
  • TLS certificate is valid and trusted
  • The DocumentServer container runs fine
  • This exact setup used to work flawlessly before reinstall

:cross_mark: The problem

  • In the Nextcloud UI > OnlyOffice settings:
    • The form hangs on “Saving settings…” endlessly
    • No network request is made (checked via dev tools)
    • The connector never activates

:test_tube: Already tested (and ruled out)

Test Result
Reinstalling Docker + AIO + DocumentServer :white_check_mark:
Changing JWT format (with/without quotes) :white_check_mark:
Internal Docker network linking (e.g. documentserver:80) :cross_mark: Already tested — not working
HTTP instead of HTTPS :cross_mark: Rejected by the connector
Self-signed certs :cross_mark: Rejected
Disabling EditorsCheck cron job :cross_mark: Not the issue (happens at initial setup)

:paperclip: Related GitHub issue

:right_arrow: ❗ Bug: Unable to enable OnlyOffice connector in fresh Nextcloud AIO install (endless loading loop) · Issue #1104 · ONLYOFFICE/onlyoffice-nextcloud · GitHub

Looking for anyone who:

  • Has faced the same issue with a clean AIO setup
  • Successfully uses OnlyOffice in AIO via external public HTTPS
  • Can confirm or deny whether this is a recent regression

Thanks in advance for your help!

— Pierre
GitHub: @PierreLga456

2

Issue resolved.

The problem was caused by a misconfigured local DNS redirection in my UniFi (UCG-Ultra) router, which pointed nuage.lann.es to the internal server IP (192.168.1.38).

This redirection caused a hairpin NAT loop, which prevented services like Nextcloud Talk (high-performance backend) or ONLYOFFICE from working properly.

After removing this redirection, everything works as expected.

Thanks for your support, I’m closing this ticket.

1 Like
3

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.