Support intro
Sorry to hear you’re facing problems 
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 : 31.0.7
Talk Server version (eg, 14.0.2): Unsure? Is this different than the signaling server version?
Custom Signaling server configured: no - using built in 2.0.3
Custom TURN server configured: no - built in
Custom STUN server configured: no - built in
Web version of nextcloud talk works just fine.
In case mobile Nextcloud Talk apps are involved:
Talk iOS version: Most current version
Talk Android version: Most current version
Talk Windows Version: Most current version
The issue you are facing:
When logging in to windows talk client, I receive “Login was successful but something went wrong” and if I try to log in again, I get “nextcloud server not found.” Restarting the client lets me connect and attempt to login again but always gives the same error.
On both iPhone and android, I can login but cannot send messages, view messages, do anything really except search users.
Is this the first time you’ve seen this error? : Yes, and since I installed nextcloud AIO. Previously I had just the regular nextcloud instance working just fine but decided to move to nextcloud-aio from scratch for all the built in features and greater ease of use.
Steps to replicate it:
- Setup nextcloud-aio docker
- Forward 443 and 80 to Caddy container(Caddy forwards literally everything to apache it is NOT the issue at this point, websockets connect and everything and all else works)
- Caddy is forwarding everything to apache container inside of nextcloud-aio docker network. As I said all else works and websockets connect when tested separately. Hello message is received.
The output of your Nextcloud log in Admin > Logging or errors in nextcloud.log in /var/www/:
There are no errors
The output of your Apache/nginx/system log in /var/log/____:
Non-existent?
Your browser log if relevant (javascript console log, network log, etc.):
Its not.
What I have tried in this insanity:
I have tried using nginx, caddy, having 443 and 80 go directly to both apache and AIO docker containers. Nothing.
I have tried the most basic of Caddy setups and had to use this to get socket working:
Caddy File
nextcloud.hidden.com {
tls -omitted-
encode gzip zstd
header {
Strict-Transport-Security "max-age=31536000; includeSubDomains; preload"
X-Content-Type-Options "nosniff"
X-Frame-Options "SAMEORIGIN"
Referrer-Policy "no-referrer"
X-XSS-Protection "1; mode=block"
}
# ───── rewrite /ocm‐provider → index.php ─────
@ocmProvider path /ocm-provider /ocm-provider/*
rewrite @ocmProvider /index.php
#web socket handling
reverse_proxy /ocs/v2.php/apps/spreed/ws* {
to nextcloud-aio-apache:11000
transport http {
versions h2c 2
}
header_up Host {host}
header_up X-Real-IP {remote_host}
header_up X-Forwarded-For {remote_host}
header_up X-Forwarded-Proto {scheme}
header_up Upgrade {header.Upgrade}
header_up Connection {header.Connection}
header_up Origin {header.Origin}
}
# OCM provider endpoints
reverse_proxy /ocs-provider/* {
to nextcloud-aio-apache:11000
header_up Host {host}
header_up X-Real-IP {remote}
header_up X-Forwarded-For {remote}
header_up X-Forwarded-Proto {scheme}
}
reverse_proxy /* nextcloud-aio-apache:11000 {
header_up Host {host}
header_up X-Real-IP {remote_host}
header_up X-Forwarded-For {remote_host}
header_up X-Forwarded-Proto {scheme}
header_up X-Forwarded-Host {host}
header_up X-Forwarded-Port {server_port}
}
}
Nginx would work for everything but again still no worky with talk.
I have tried doing a complete re-setup on a completely different machine and gotten the same error.
I have tried DMZing to apache container, no worky.
I only theorize at this point that the apache container in this AIO is somehow just screwed because I can not find any issues online that are even remotely helpful in resolving this.
Setting websocket forwarding in caddy to the talk container seemed to also work for connecting to websocket.
I really just dont know at this point. Web version works just fine, but any of the client applications tell me to kick rocks and die. There are no logs for the client application either! So that is fantastic!
Best I could find in talk server logs was:
2025-07-20T21:15:29.660723546Z hub.go:867: Register user test@backend-1 from -omitted- in unknown-country (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Safari/537.36 Edg/138.0.0.0) --OMITTED KEY-- (private=--OMITTED KEY--)
2025-07-20T21:15:29.661139084Z hub.go:965: Unregister --SAME OMITTED KEY-- (private=--SAME OMITTED KEY--)
