Could not connect to server using backend url

paramazo commented 2 weeks ago

How to use GitHub

Please use the 👍 reaction to show that you are affected by the same issue.
Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
Subscribe to receive notifications on status change and new comments.

Steps to reproduce

Open a Talk conversation

Expected behaviour

Conversation should open without errors

Actual behaviour

Errors in browser console ("Could not connect to server using backend url") and nextloud notifications with signaling server for 7-10 seconds are shown. Then it works as expected. This issue exists reproducible for every user since some days and we dont know why. We can not see performance issues or issues with network connectivity to the signaling server.

Talk app

Talk app version: 19.0.1

Custom Signaling server configured: yes, version 1.2.4

Custom TURN server configured: yes

Custom STUN server configured: yes

Browser

Microphone available: yes

Camera available: yes

Operating system: Debian 11

Browser name: Firefox

Browser version: 115.14.0esr (64-bit)

Browser log

``` Content-Security-Policy: The page’s settings blocked the loading of a resource at data: (“media-src”). spreed OCA.Sharing.ShareSearch not ready init-collections.js:39:10 OCA.Sharing.ShareSearch not ready init-collections.js:39:10 Content-Security-Policy: The page’s settings blocked the loading of a resource at data: (“media-src”). blank Could not connect to server using backend url https://192.168.11.18/ocs/v2.php/apps/spreed/api/v3/signaling/backend Object { id: "1", type: "error", error: {…} } signaling.js:1081:10 Ignore unknown error Object { id: "1", type: "error", error: {…} } signaling.js:830:12 Could not connect to server using backend url https://192.168.11.18/ocs/v2.php/apps/spreed/api/v3/signaling/backend Object { id: "1", type: "error", error: {…} } signaling.js:1081:10 Ignore unknown error Object { id: "1", type: "error", error: {…} } signaling.js:830:12 Could not connect to server using backend url https://192.168.11.18/ocs/v2.php/apps/spreed/api/v3/signaling/backend Object { id: "1", type: "error", error: {…} } signaling.js:1081:10 Ignore unknown error Object { id: "1", type: "error", error: {…} } signaling.js:830:12 Could not connect to server using backend url https://192.168.11.18/ocs/v2.php/apps/spreed/api/v3/signaling/backend Object { id: "1", type: "error", error: {…} } signaling.js:1081:10 Ignore unknown error Object { id: "1", type: "error", error: {…} } signaling.js:830:12 Could not connect to server using backend url https://192.168.11.18/ocs/v2.php/apps/spreed/api/v3/signaling/backend Object { id: "1", type: "error", error: {…} } signaling.js:1081:10 Ignore unknown error Object { id: "1", type: "error", error: {…} } signaling.js:830:12 Could not connect to server using backend url https://192.168.11.18/ocs/v2.php/apps/spreed/api/v3/signaling/backend Object { id: "1", type: "error", error: {…} } signaling.js:1081:10 Ignore unknown error Object { id: "1", type: "error", error: {…} } signaling.js:830:12 Could not connect to server using backend url https://192.168.11.18/ocs/v2.php/apps/spreed/api/v3/signaling/backend Object { id: "1", type: "error", error: {…} } signaling.js:1081:10 Ignore unknown error Object { id: "1", type: "error", error: {…} } signaling.js:830:12 Could not connect to server using backend url https://192.168.11.18/ocs/v2.php/apps/spreed/api/v3/signaling/backend Object { id: "1", type: "error", error: {…} } signaling.js:1081:10 Ignore unknown error Object { id: "1", type: "error", error: {…} } signaling.js:830:12 ```

Server configuration

Operating system: Debian 11

Web server: Apache

Database: Maria

PHP version: 8.2

Nextcloud Version: 29.0.5

List of activated apps:

``` Enabled: - activity: 2.21.1 - bruteforcesettings: 2.9.0 - calendar: 4.7.16 - circles: 29.0.0-dev - cloud_federation_api: 1.12.0 - comments: 1.19.0 - contacts: 6.0.0 - contactsinteraction: 1.10.0 - dashboard: 7.9.0 - dav: 1.30.1 - deck: 1.13.1 - drawio: 3.0.2 - federatedfilesharing: 1.19.0 - federation: 1.19.0 - files: 2.1.1 - files_downloadlimit: 2.0.0 - files_external: 1.21.0 - files_lock: 29.0.1 - files_pdfviewer: 2.10.0 - files_reminders: 1.2.0 - files_sharing: 1.21.0 - files_trashbin: 1.19.0 - files_versions: 1.22.0 - flow_notifications: 1.9.0 - forms: 4.2.4 - groupfolders: 17.0.2 - logreader: 2.14.0 - lookup_server_connector: 1.17.0 - mail: 3.7.7 - nextcloud_announcements: 1.18.0 - notes: 4.10.1 - notifications: 2.17.0 - oauth2: 1.17.0 - onlyoffice: 9.3.0 - password_policy: 1.19.0 - photos: 2.5.0 - privacy: 1.13.0 - provisioning_api: 1.19.0 - recommendations: 2.1.0 - related_resources: 1.4.0 - serverinfo: 1.19.0 - settings: 1.12.0 - spreed: 19.0.8 - systemtags: 1.19.0 - tables: 0.7.5 - text: 3.10.1 - theming: 2.4.0 - twofactor_backupcodes: 1.18.0 - twofactor_totp: 11.0.0-dev - updatenotification: 1.19.1 - user_ldap: 1.20.0 - user_status: 1.9.0 - viewer: 2.3.0 - weather_status: 1.9.0 - workflowengine: 2.11.0 ```

Nextcloud configuration:

``` If you have access to your command line run e.g.: sudo -u www-data php occ config:list system from within your Nextcloud installation folder ```

Server log (data/nextcloud.log)

``` empty ```

SystemKeeper commented 2 weeks ago

Besides the fact that I would highly recommend updating to the latest version of talk:

Could not connect to server using backend url https://192.168.11.18/ocs/v2.php/apps/spreed/api/v3/signaling/backend Object { id: "1", type: "error", error: {…} }

Can you please post the expanded error here? Also please check the signaling servers log.

paramazo commented 2 weeks ago

Thanks for your response @SystemKeeper

Here are the expanded errors from browsers console:

Could not connect to server using backend url https://192.168.11.18/ocs/v2.php/apps/spreed/api/v3/signaling/backend 
Object { id: "1", type: "error", error: {…} }
[signaling.js:1081:10](webpack:///talk/src/utils/signaling.js)
    helloResponseReceived signaling.js:1081
    onmessage signaling.js:777
Ignore unknown error 
Object { id: "1", type: "error", error: {…} }
[signaling.js:830:12](webpack:///talk/src/utils/signaling.js)
    onmessage signaling.js:830

Signaling log when this error occurs on page reload:

Aug 30 16:57:47 talk01 signaling[445]: client.go:283: Client from 192.168.10.231 has RTT of 29 ms (29.9
5765ms)
Aug 30 16:57:49 talk01 signaling[445]: client.go:283: Client from 192.168.10.231 has RTT of 20 ms (20.7
44113ms)
Aug 30 16:57:50 talk01 signaling[445]: client.go:283: Client from 192.168.10.231 has RTT of 5 ms (5.458
374ms)
Aug 30 16:57:51 talk01 signaling[445]: client.go:283: Client from 192.168.10.231 has RTT of 6 ms (6.700
626ms)
Aug 30 16:57:52 talk01 signaling[445]: client.go:283: Client from 192.168.10.231 has RTT of 9 ms (9.781
341ms)
Aug 30 16:57:53 talk01 signaling[445]: client.go:283: Client from 192.168.10.231 has RTT of 2 ms (2.386
309ms)
Aug 30 16:57:54 talk01 signaling[445]: client.go:283: Client from 192.168.10.231 has RTT of 8 ms (8.777
714ms)
Aug 30 16:57:55 talk01 signaling[445]: client.go:283: Client from 192.168.10.231 has RTT of 13 ms (13.0
51447ms)
Aug 30 16:57:56 talk01 signaling[445]: client.go:283: Client from 192.168.10.231 has RTT of 3 ms (3.827
291ms)
Aug 30 16:57:58 talk01 signaling[445]: client.go:283: Client from 192.168.10.231 has RTT of 9 ms (9.582
093ms)

SystemKeeper commented 2 weeks ago

Object { id: "1", type: "error", error: {…} }

Sorry, this is what I meant, the "error" key should be expanded.

paramazo commented 2 weeks ago

Ah ok, here is the expanded error @SystemKeeper

Ignore unknown error 
Object { id: "1", type: "error", error: {…} }

error: Object { code: "token_not_valid_yet", message: "The token is not valid yet." }

code: "token_not_valid_yet"

message: "The token is not valid yet."

<prototype>: Object { … }

id: "1"

type: "error"

<prototype>: Object { … }

In the meantime i updated the nextcloud to 29.0.5 and talk app to 19.0.8. The behaviour is the same.

SystemKeeper commented 2 weeks ago

code: "token_not_valid_yet"

This indicates that the time on the server is not set correctly, it is probably some seconds ahead - can you please check that?

paramazo commented 2 weeks ago

the server time is indeed some seconds ahead. I will check this, thank you.

// Fixing my NTP TImeserver was the solution for this

SystemKeeper commented 2 weeks ago

Thanks for the info. I’ll close this issue now, as it is related to server time.

nextcloud / spreed