Steps to reproduce
1.when the server is runnin, temporarily block UDP port 3478.
2.Open Calendar and create an event with an attendee – the “Create Talk room” button disappears.
3.Re‑open the port; the button stays missing for all users.
Expected behavior
After restoring network conditions, the button should reappear and work as before.
Actual behavior
The button is still invisable after opening the port back.
Calendar app version
Calendar: 6.2.3 , Talk: 23.0.4
CalDAV-clients used
DAVx5
Browser
all
Client operating system
win 11
Server operating system
debian 13
Web server
None
Database engine version
None
PHP engine version
None
Nextcloud version
latest
Updated from an older installed version or fresh install
Fresh install
List of activated apps
Nextcloud configuration
name: nextcloud-aio
services:
nextcloud-aio-mastercontainer:
image: ghcr.io/nextcloud-releases/all-in-one:latest
init: true
restart: always
container_name: nextcloud-aio-mastercontainer
volumes:
- nextcloud_aio_mastercontainer:/mnt/docker-aio-config
- /var/run/docker.sock:/var/run/docker.sock:ro
network_mode: bridge
ports:
- "8080:8080"
# - "8443:8443"
# - "80:80"
environment:
APACHE_PORT: 11000
#APACHE_IP_BINDING: 0.0.0.0
APACHE_IP_BINDING: 127.0.0.1
SKIP_DOMAIN_VALIDATION: false
NEXTCLOUD_MEMORY_LIMIT: 2048M
TALK_PORT: 3478
volumes:
nextcloud_aio_mastercontainer:
name: nextcloud_aio_mastercontainer
Web server error log
Log file
Browser log
Additional info
Current state
-
The button is missing for every user, despite the port being reopened.
-
Browser console originally showed: [Vue error]: TypeError: can't access property "scheduleDefaultCalendarUrl", this.currentUserPrincipal is undefined
-
PROPFIND to /remote.php/dav/ returns a valid for the tested user, but calendar-home-set consistently yields 404 Not Found (even though the user’s calendar collection is reachable at /remote.php/dav/calendars//).
-
The talkEnabled app config is forced to yes globally and per user.
-
Disabling/enabling both Calendar and Talk apps, flushing Redis (FLUSHALL), running occ maintenance:repair, restarting the Nextcloud container, and clearing all browser-side caches have not restored the button.
Hypothesis
The transient UDP block caused a failure in Talk’s conferencing provider registration or capability advertisement that was never recovered. This leaves Calendar’s frontend unable to load the Talk conferencing provider for any user, preventing the button from rendering despite correct individual DAV principals. The global nature points to a server‑side capability/cache issue rather than a per‑user problem.
Steps to reproduce
1.when the server is runnin, temporarily block UDP port 3478.
2.Open Calendar and create an event with an attendee – the “Create Talk room” button disappears.
3.Re‑open the port; the button stays missing for all users.
Expected behavior
After restoring network conditions, the button should reappear and work as before.
Actual behavior
The button is still invisable after opening the port back.
Calendar app version
Calendar: 6.2.3 , Talk: 23.0.4
CalDAV-clients used
DAVx5
Browser
all
Client operating system
win 11
Server operating system
debian 13
Web server
None
Database engine version
None
PHP engine version
None
Nextcloud version
latest
Updated from an older installed version or fresh install
Fresh install
List of activated apps
Nextcloud configuration
Web server error log
Log file
Browser log
Additional info
Current state
The button is missing for every user, despite the port being reopened.
Browser console originally showed: [Vue error]: TypeError: can't access property "scheduleDefaultCalendarUrl", this.currentUserPrincipal is undefined
PROPFIND to /remote.php/dav/ returns a valid for the tested user, but calendar-home-set consistently yields 404 Not Found (even though the user’s calendar collection is reachable at /remote.php/dav/calendars//).
The talkEnabled app config is forced to yes globally and per user.
Disabling/enabling both Calendar and Talk apps, flushing Redis (FLUSHALL), running occ maintenance:repair, restarting the Nextcloud container, and clearing all browser-side caches have not restored the button.
Hypothesis
The transient UDP block caused a failure in Talk’s conferencing provider registration or capability advertisement that was never recovered. This leaves Calendar’s frontend unable to load the Talk conferencing provider for any user, preventing the button from rendering despite correct individual DAV principals. The global nature points to a server‑side capability/cache issue rather than a per‑user problem.