# Background blur: Could not check for WASM loading support **URL:** \ **Category:** ℹ️ Support\ **Tags:** nc32, aio, dns, nc31\ **Created:** [November 20, 2025, 4:58pm UTC](https://help.nextcloud.com/t/background-blur-could-not-check-for-wasm-loading-support/236175 "2025-11-20T16:58:31Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![BaschtelOpi](https://help.nextcloud.com/user_avatar/help.nextcloud.com/baschtelopi/32/75603_2.png) [@BaschtelOpi](https://help.nextcloud.com/u/BaschtelOpi)\ **Post date:** [November 20, 2025, 4:58pm UTC](https://help.nextcloud.com/t/background-blur-could-not-check-for-wasm-loading-support/236175/1 "2025-11-20T16:58:31Z")
> **Support intro** > > ## Sorry to hear you’re facing problems. 🙁 > > _The community help forum ([help.nextcloud.com](http://help.nextcloud.com)) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are **volunteering their time to help you.** _ > > **If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via [portal.nextcloud.com](http://portal.nextcloud.com) where Nextcloud engineers can help ensure your business keeps running smoothly.** > > ## Getting help > > In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can. > > **Before clicking submit** : Please check if your query is already addressed via the following resources: > > - [Official documentation](https://docs.nextcloud.com) (searchable and regularly updated) > - [How to topics and FAQs](https://help.nextcloud.com/c/how-to-faqs/9) > - [Forum search](https://help.nextcloud.com/search) > > (Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly). Since migration to 32.0.x I’m getting follow in error message: Background blur: Could not check for WASM loading support. Please check manually if your web server serves `.wasm` files. To allow this check to run you have to make sure that your Web server can connect to itself. Therefore it must be able to resolve and connect to at least one of its `trusted_domains` or the `overwrite.cli.url`. This failure may be the result of a server-side DNS mismatch or outbound firewall rule. ## The Basics - Nextcloud Server version _(e.g., 29.x.x)_: - docker \> nextcloud:32.0.1-apache - Operating system and version _(e.g., Ubuntu 24.04)_: - `Ubuntu 24.04` - Web server and version _(e.g, Apache 2.4.25)_: - `n/a` - Reverse proxy and version \_(e.g. nginx 1.27.2) - nginx -V nginx version: nginx/1.28.0 built by gcc 13.3.0 (Ubuntu 13.3.0-6ubuntu2~24.04) built with OpenSSL 3.0.13 30 Jan 2024 TLS SNI support enabled configure arguments: --prefix=/etc/nginx --sbin-path=/usr/sbin/nginx --modules-path=/usr/lib/nginx/modules --conf-path=/etc/nginx/nginx.conf --error-log-path=/var/log/nginx/error.log --http -log-path=/var/log/nginx/access.log --pid-path=/run/nginx.pid --lock-path=/run/nginx.lock --http-client-body-temp-path=/var/cache/nginx/client\_temp --http-proxy-temp-path=/var/cache/nginx/p roxy\_temp --http-fastcgi-temp-path=/var/cache/nginx/fastcgi\_temp --http-uwsgi-temp-path=/var/cache/nginx/uwsgi\_temp --http-scgi-temp-path=/var/cache/nginx/scgi\_temp --user=nginx --group=ngi nx --with-compat --with-file-aio --with-threads --with-http\_addition\_module --with-http\_auth\_request\_module --with-http\_dav\_module --with-http\_flv\_module --with-http\_gunzip\_module --with-ht tp\_gzip\_static\_module --with-http\_mp4\_module --with-http\_random\_index\_module --with-http\_realip\_module --with-http\_secure\_link\_module --with-http\_slice\_module --with-http\_ssl\_module --with- http\_stub\_status\_module --with-http\_sub\_module --with-http\_v2\_module --with-http\_v3\_module --with-mail --with-mail\_ssl\_module --with-stream --with-stream\_realip\_module --with-stream\_ssl\_mod ule --with-stream\_ssl\_preread\_module --with-cc-opt=‘-g -O2 -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -ffile-prefix-map=/home/builder/debuild/nginx-1.28.0/debian/debuild-base/ngin x-1.28.0=. -flto=auto -ffat-lto-objects -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -fdebug-prefix-map=/home/builder/debuild/nginx-1.2 8.0/debian/debuild-base/nginx-1.28.0=/usr/src/nginx-1.28.0-1~noble -fPIC’ --with-ld-opt=‘-Wl,-Bsymbolic-functions -flto=auto -ffat-lto-objects -Wl,-z,relro -Wl,-z,now -Wl,–as-needed -pie’ - PHP version _(e.g, 8.3)_: - `n/a` - Is this the first time you’ve seen this error? (Yes / No): - `Yes` - When did this problem seem to first start? - `When upgrading from 31.0.10 to 32.0.0` - Installation method _(e.g. AlO, NCP, Bare Metal/Archive, etc.)_ - `docker` - Are you using CloudfIare, mod\_security, or similar? _(Yes / No)_ - `No` ### Summary of the issue you are facing: Checked trusted\_domains and overwrite.cli.url. I’m running a nextcloud:32.0.1-apache behind an nginx proxy. In the error log of the nginx proxy I found : “/usr/share/nginx/html/spreed/js/tflite.wasm” failed (2: No such file or directory), client: 172.18.0.12 172.18.0.12 is the IP of the nc docker app. tflite.wasm is not part of docker image ### Steps to replicate it (hint: details matter!): 1. Administration \> Overview 2. 3. ### Log entries #### Nextcloud Please provide the log entries from your Nextcloud log that are generated during the time of problem (via the _Copy raw_ option from _Administration settings-\>Logging_ screen or from your `nextcloud.log` located in your data directory). Feel free to use a pastebin/gist service if necessary. ```auto No related log entry ``` #### Web Browser If the problem is related to the Web interface, open your browser inspector _Console_ and _Network_ tabs while refreshing (reloading) and reproducing the problem. Provide any relevant output/errors here that appear. ```auto N/A ``` #### Web server / Reverse Proxy The output of your Apache/nginx/system log in `/var/log/ ____ `: ```auto error.log: 2025/11/20 17:33:18 [error] 3896827#3896827: *791 open() "/usr/share/nginx/html/spreed/js/tflite.wasm" failed (2: No such file or directory), client: 172.18.0.12, server: my-domain, request: "HEAD /spreed/js/tflite.wasm HTTP/1.1", host: "192.168.1.24" ``` ### Configuration #### Nextcloud The output of `occ config:list system` or similar is best, but, if not possible, the contents of your `config.php` file from `/path/to/nextcloud` is fine (make sure to remove any identifiable information!): ```auto PASTE HERE ``` #### Apps The output of `occ app:list` (if possible). ### Tips for increasing the likelihood of a response - Use the `preformatted text` formatting option in the editor for all log entries and configuration output. - If screenshots are useful, feel free to include them. - If possible, also include key error output in text form so it can be searched for. - Try to edit log output only minimally (if at all) so that it can be ran through analyzers / formatters by those trying to help you. ---
**Author:** ![squid-f](https://help.nextcloud.com/user_avatar/help.nextcloud.com/squid-f/32/75608_2.png) [@squid-f](https://help.nextcloud.com/u/squid-f)\ **Post date:** [November 20, 2025, 6:21pm UTC](https://help.nextcloud.com/t/background-blur-could-not-check-for-wasm-loading-support/236175/2 "2025-11-20T18:21:46Z")
Hi. Getting the same error since NC32 update, with php 8.4 and nginx server, no docker. ---
**Author:** ![Cisco30](https://help.nextcloud.com/user_avatar/help.nextcloud.com/cisco30/32/54605_2.png) [@Cisco30](https://help.nextcloud.com/u/Cisco30)\ **Post date:** [November 20, 2025, 8:22pm UTC](https://help.nextcloud.com/t/background-blur-could-not-check-for-wasm-loading-support/236175/3 "2025-11-20T20:22:45Z")
I’ve had the same problem since the 32.0.2 update, Debian 13, Apache 2, PHP 8.3. Before the update, I had no errors. ---
**Author:** ![SysKeeper](https://help.nextcloud.com/letter_avatar/syskeeper/32/5_5575768a8748004e209b776fc1b2916d.png) [@SysKeeper](https://help.nextcloud.com/u/SysKeeper)\ **Post date:** [November 20, 2025, 8:27pm UTC](https://help.nextcloud.com/t/background-blur-could-not-check-for-wasm-loading-support/236175/4 "2025-11-20T20:27:10Z")
Hey, thanks for the reports, 22.0.4 should be available shortly. ---
**Author:** ![SysKeeper](https://help.nextcloud.com/letter_avatar/syskeeper/32/5_5575768a8748004e209b776fc1b2916d.png) [@SysKeeper](https://help.nextcloud.com/u/SysKeeper)\ **Post date:** [November 20, 2025, 8:32pm UTC](https://help.nextcloud.com/t/background-blur-could-not-check-for-wasm-loading-support/236175/5 "2025-11-20T20:32:00Z")
It’s in the AppStore: [Talk - Apps - App Store - Nextcloud](https://apps.nextcloud.com/apps/spreed). Due to caching it might take a bit until it shows up on your instances. ---
**Author:** ![Ok\_Know](https://help.nextcloud.com/user_avatar/help.nextcloud.com/ok_know/32/69839_2.png) [@Ok\_Know](https://help.nextcloud.com/u/Ok_Know)\ **Post date:** [November 21, 2025, 2:53am UTC](https://help.nextcloud.com/t/background-blur-could-not-check-for-wasm-loading-support/236175/6 "2025-11-21T02:53:23Z")
It doesn’t seem to be working. The error isn’t from the 32.0.2 upgrade; the warning appeared when Talk was upgraded from 22.0.2 to 22.0.4. ---
**Author:** ![Rolando\_Nispiros](https://help.nextcloud.com/user_avatar/help.nextcloud.com/rolando_nispiros/32/68919_2.png) [@Rolando\_Nispiros](https://help.nextcloud.com/u/Rolando_Nispiros)\ **Post date:** [November 21, 2025, 3:57am UTC](https://help.nextcloud.com/t/background-blur-could-not-check-for-wasm-loading-support/236175/7 "2025-11-21T03:57:10Z")
Received the same error after upgrading to Talk and Nextcloud 32.02. But then I uninstalled Talk and issue went away. ---
**Author:** ![bb77](https://help.nextcloud.com/letter_avatar/bb77/32/5_5575768a8748004e209b776fc1b2916d.png) [@bb77](https://help.nextcloud.com/u/bb77)\ **Post date:** [November 21, 2025, 11:29am UTC](https://help.nextcloud.com/t/background-blur-could-not-check-for-wasm-loading-support/236175/8 "2025-11-21T11:29:05Z")
Yeah, unfortunately, it seems that the fix did not make it into Talk 22.0.4: [Wrong wasm check results in Overview and Talk andministration pages · Issue #16380 · nextcloud/spreed · GitHub](https://github.com/nextcloud/spreed/issues/16380#issuecomment-3560117292) So, I’d say we need to wait for the next update and ignore the message for now. ---
**Author:** ![pra](https://help.nextcloud.com/user_avatar/help.nextcloud.com/pra/32/34432_2.png) [@pra](https://help.nextcloud.com/u/pra)\ **Post date:** [November 21, 2025, 12:01pm UTC](https://help.nextcloud.com/t/background-blur-could-not-check-for-wasm-loading-support/236175/9 "2025-11-21T12:01:50Z")
thank you @bb77 going to close [https://help.nextcloud.com/t/background-blur-could-not-check-for-wasm-loading-support/236175](https://help.nextcloud.com/t/resolved-nextcloud32-talk-22-0-4/236203/5) no problem will wait the next upgrade good luck ---
**Author:** ![system](https://help.nextcloud.com/user_avatar/help.nextcloud.com/system/32/29333_2.png) [@system](https://help.nextcloud.com/u/system)\ **Post date:** [November 29, 2025, 12:01pm UTC](https://help.nextcloud.com/t/background-blur-could-not-check-for-wasm-loading-support/236175/10 "2025-11-29T12:01:57Z")
This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.