[RESOLVED] Nextcloud32 - talk 22.0.4

â„č Support 💬 Talk (spreed)
, , , ,
1
Support intro

Sorry to hear you’re facing problems :slightly_frowning_face:

help.nextcloud.com is for home/non-enterprise users. If you’re running a business, paid support can be accessed via portal.nextcloud.com where we can ensure your business keeps running smoothly.

In order to help you as quickly as possible, before clicking Create Topic please provide as much of the below as you can. Feel free to use a pastebin service for logs, otherwise either indent short log examples with four spaces:

example

Or for longer, use three backticks above and below the code snippet:

longer
example
here

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can :heart:

Some useful links to gather information about your Nextcloud Talk installation:
Information about Signaling server: /index.php/index.php/settings/admin/talk#signaling_server
Information about TURN server: /index.php/settings/admin/talk#turn_server
Information about STUN server: /index.php/settings/admin/talk#stun_server

Nextcloud version (eg, 24.0.1): 32.0.2
Talk Server version (eg, 14.0.2): 22.0.4
Custom Signaling server configured: no
Custom TURN server configured: yes
Custom STUN server configured: yes

In case the web version of Nextcloud Talk is involved:
Operating system (eg, Windows/Ubuntu/
): debian 13 / mac os 26.1
Browser name and version (eg, Chrome v101): firefox 140.5.0esr (aarch64)/ chrome142.0.7444.162 (Build officiel) (arm64)

In case mobile Nextcloud Talk apps are involved:
Talk iOS version (eg, 14.0.2): na
Talk Android version (eg, 14.0.2): na

The issue you are facing:

takl working but sinc e the upgrade 22.0.2 to 22.0.4 in nextcloud in admin after the check i have this warning / info :

Flou d’arriùre-plan

Impossible de vĂ©rifier la prise en charge du chargement WASM. Veuillez vĂ©rifier manuellement si votre serveur Web sert des fichiers `.wasm`. Pour autoriser cette vĂ©rification, pour devez vous assurer que votre serveur web peut se connecter Ă  lui-mĂȘme. Il doit donc ĂȘtre capable de rĂ©soudre et de se connecter Ă  au moins un de ses `trusted_domains` ou Ă  l’URL `overwrite.cli.url`. Cet Ă©chec peut ĂȘtre le rĂ©sultat d’une erreur de DNS cĂŽtĂ© serveur ou d’une rĂšgle de pare-feu sortante.

Is this the first time you’ve seen this error? (Y/N):

Steps to replicate it:

  1. na

  2. na

  3. na

The output of your Nextcloud log in Admin > Logging or errors in nextcloud.log in /var/www/:

Erreur
no app in context
ConnectException
cURL error 28: Operation timed out after 120000 milliseconds with 48835 out of 9647074 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://garm3.nextcloud.com/api/v1/apps.json

The output of your Apache/nginx/system log in /var/log/____:

no error

Your browser log if relevant (javascript console log, network log, etc.):

no error

my conf :

‘trusted_domains’ =>
array (
0 => ‘nxt.pra.rip’,
),
‘overwrite.cli.url’ => ‘https://nxt.pra.rip’,

network check :

DNS using bind with views, nothing in /etc/hosts

all test done from nextcloud server

internal :
< [07:17:24] - root@webblog:/bck_upgrade/nextcloud/engine >
=>dig nxt.pra.rip aaaa +short
webblog.tech.pra.rip.
2a01:e0a:1ef:7591::17
< [07:17:32] - root@webblog:/bck_upgrade/nextcloud/engine >
=>dig nxt.pra.rip +short
webblog.tech.pra.rip.
192.168.123.17

external :
< [07:16:01] - root@webblog:/bck_upgrade/nextcloud/engine >
=>dig nxt.pra.rip @1.1.1.1 +short
web.pra.rip.
82.64.130.10
< [07:17:13] - root@webblog:/bck_upgrade/nextcloud/engine >
=>dig nxt.pra.rip aaaa @1.1.1.1 +short
web.pra.rip.
2a01:e0a:1ef:7591::203

nextcloud access from external :

internet ===> reverse proxy (nginix) ===> nextcloud server

curl -I https://nxt.pra.rip
HTTP/1.1 302 Found
Date: Fri, 21 Nov 2025 07:15:11 GMT
Server: Apache/2.4.65 (Debian)
Content-Security-Policy: default-src ‘self’; script-src ‘self’ ‘nonce-FpEfDwxwhvVepo+BoSyz/I4t5qJLjSvZU/Zq1Vhm4hI=’; style-src ‘self’ ‘unsafe-inline’; frame-src *; img-src * data: blob:; font-src ‘self’ data:; media-src *; connect-src *
; object-src ‘none’; base-uri ‘self’;
Set-Cookie: oc_sessionPassphrase=vHM3emy5P5%2BCrOpHfEwtpouvRTR%2BT%2FE8GLJKnaSwbRIXTzkU8py1c%2BxMyLhnc8PyiNr7RYDjpOYMeD32dQFfPhgd%2F3CYRIYCWgzPRyXkTSTcctqqSjGbgwyrdzSSPGNY; path=/; secure; HttpOnly; SameSite=Lax
Set-Cookie: __Host-nc_sameSiteCookielax=true; path=/; httponly;secure; expires=Fri, 31-Dec-2100 23:59:59 GMT; SameSite=lax
Set-Cookie: __Host-nc_sameSiteCookiestrict=true; path=/; httponly;secure; expires=Fri, 31-Dec-2100 23:59:59 GMT; SameSite=strict
Set-Cookie: oc22s5j6m931=t5m6evosv33rqscckcg6si26kr; path=/; secure; HttpOnly; SameSite=Lax
Strict-Transport-Security: max-age=15552000; includeSubDomains; preload
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-Permitted-Cross-Domain-Policies: none
X-Robots-Tag: noindex, nofollow
Referrer-Policy: no-referrer
Upgrade: h2
Connection: Upgrade
Location: S’identifier – Nextcloud
Content-Type: text/html; charset=UTF-8

thank you for your help

2

I suppose it is the same issue as here - Background blur: Could not check for WASM loading support

3

hello @vawaver
yes, i already see it , but the thread is closed , that why i created a new i didn t see a button or other thing for reopen the issue

for me this issue is linked to the talk upgrade

thank you for your help

1 Like
4

No, the other thread is not closed, and yes, it appears to be a bug, and unfortunately, the fix does not seem to have made it into Talk 22.0.4: Wrong wasm check results in Overview and Talk andministration pages · Issue #16380 · nextcloud/spreed · GitHub

So if everything is working as expected, just wait for the next update and ignore the message for now.

3 Likes
5

thank you @bb77 closing continue in Background blur: Could not check for WASM loading support

1 Like
6

Just a quick note.

If a post is marked as “reolved” in a thread that does not mean that the thread is actually closed. You can still post replies if there is new information, or ask questions if the post marked as the solution is unclear.

You can also un-mark a post if it was not the solution after all, and then mark a new post with the actual solution.

7

ok thank you @bb77

have a great week end

1 Like