[Bug]: Nextcloud too slow on WAN, but it turns fine when switching Collabora off...

[astrometrics]

⚠️ This issue respects the following points: ⚠️

• This is a bug, not a question or a configuration/webserver/proxy issue.
• This issue is not already reported on Github (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• Nextcloud Server is running on 64bit capable CPU, PHP and OS.
• I agree to follow Nextcloud's Code of Conduct.

Bug description

as described in https://help.nextcloud.com/t/nextcloud-slow-in-public-ip-and-work-perfectly-in-lan/105734/19
NC on LAN is working well, but becomes very slow via WAN. As per the link above, disabled Office then working fine... What could possibly Collabora influence to result in NC delaying 3 to 5 minutes to log on when on WAN?

Thanks for Nextcloud.

Steps to reproduce

1. Publish NC (with office installed) to WAN
2. Test and verify log on takes for ever to show up...
3. Disable office
4. NC works normally.

Expected behavior

Collabora should have zero effect on overall performance of unrelated functionality.

Installation method

Community Manual installation with Archive

Nextcloud Server version

26

Operating system

Debian/Ubuntu

PHP engine version

PHP 8.2

Web server

Apache (supported)

Database engine version

PostgreSQL

Is this bug present after an update or on a fresh install?

None

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

No response

List of activated Apps

Enabled:
  - activity: 2.18.0
  - admin_audit: 1.16.0
  - announcementcenter: 6.6.1
  - bookmarks: 13.0.1
  - bruteforcesettings: 2.6.0
  - calendar: 4.3.4
  - calendar_resource_management: 0.5.0
  - carnet: 0.24.6
  - checksum: 1.2.1
  - cloud_federation_api: 1.9.0
  - comments: 1.16.0
  - contacts: 5.2.0
  - contactsinteraction: 1.7.0
  - cookbook: 0.10.2
  - cospend: 1.5.10
  - dashboard: 7.6.0
  - dav: 1.25.0
  - deck: 1.9.2
  - drawio: 2.1.1
  - federatedfilesharing: 1.16.0
  - federation: 1.16.0
  - files: 1.21.1
  - files_accesscontrol: 1.16.0
  - files_automatedtagging: 1.16.1
  - files_markdown: 2.4.0
  - files_mindmap: 0.0.27
  - files_pdfviewer: 2.7.0
  - files_rightclick: 1.5.0
  - files_sharing: 1.18.0
  - files_trashbin: 1.16.0
  - files_versions: 1.19.1
  - firstrunwizard: 2.15.0
  - forms: 3.3.0
  - groupfolders: 14.0.2
  - health: 1.6.2
  - holiday_calendars: 0.3.0
  - impersonate: 1.13.1
  - logreader: 2.11.0
  - lookup_server_connector: 1.14.0
  - maps: 1.0.2
  - nextcloud_announcements: 1.15.0
  - notes: 4.7.2
  - notifications: 2.14.0
  - oauth2: 1.14.0
  - password_policy: 1.16.0
  - photos: 2.2.0
  - privacy: 1.10.0
  - provisioning_api: 1.16.0
  - recommendations: 1.5.0
  - related_resources: 1.1.0-alpha1
  - serverinfo: 1.16.0
  - settings: 1.8.0
  - sharebymail: 1.16.0
  - spreed: 16.0.3
  - systemtags: 1.16.0
  - tables: 0.5.0
  - tasks: 0.15.0
  - text: 3.7.2
  - theming: 2.1.1
  - twofactor_backupcodes: 1.15.0
  - twofactor_totp: 8.0.0-alpha.0
  - updatenotification: 1.16.0
  - user_status: 1.6.0
  - viewer: 1.10.0
  - weather_status: 1.6.0
  - workflowengine: 2.8.0

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response

[astrometrics]

hi... my last comment was censored needlessly...
anyway what's going on with this issue?

[astrometrics]

Hi... I tested Collabora on x64 too and the problem is the same... NC unusable on WAN

[joshtrichards]

Can you look at your browser console under the *Network" tab while this is behaving slowly and compare it against going it when it's more performant? That will give numbers to go with different transactions and might provide some insight.

[astrometrics]

Can you look at your browser console under the *Network" tab while this is behaving slowly and compare it against going it when it's more performant? That will give numbers to go with different transactions and might provide some insight.

Hi Josh, I did that and the the dashboard page just took minutes to respond... Anyway it is no secret that this is happening, dozens of people are having the same problem... just search... So the main page may be calling some Office function multiple times, that's my hypothesis. Disabled Collabora again and WAN worked fine. So yeah it is time for the NC team to take this specific issue more seriouslly. Did my bit reporting it 6 months ago.

Cheers

[joshtrichards]

I did that and the the dashboard page just took minutes to respond...

There were numerous transactions though, no?

This isn't an issue I can personally replicate so there is clearly nuance to the replication steps or the environments this occurs in.

The details from the Network section of the browser console from someone experiencing this issue might help get to the root cause.