1.4.1 Problem with Janus in (NC Talk Backend)

[Lawkss]

With Janus 1.4.1 I get the following in NC Talk high performance backend container:

2026-05-15T17:59:02.753052158Z [ERR] [ice.c:janus_ice_set_turn_server:1277] Could not resolve vom-bruch.com/cloud... 2026-05-15T17:59:02.753059142Z [FATAL] [janus.c:main:5309] Invalid TURN address vom-bruch.com/cloud:3478

It seems to want to add the subdirectory as the main domain.

I can override it with a dedicated domain parameter but in 1.4.0 this did not happen and it launched correctly by default.

[Pharao01]

It seems that I'm experiencing the same problem:
May 30 17:56:18 instance3 nextcloud-talk-hpb[17652]: Logger plugins folder: /usr/local/lib/janus/loggers
May 30 17:56:18 instance3 nextcloud-talk-hpb[17652]: ---------------------------------------------------
May 30 17:56:18 instance3 nextcloud-talk-hpb[17652]: Starting Meetecho Janus (WebRTC Server) v1.4.1
May 30 17:56:18 instance3 nextcloud-talk-hpb[17652]: ---------------------------------------------------
May 30 17:56:18 instance3 nextcloud-talk-hpb[17652]:
May 30 17:56:18 instance3 nextcloud-talk-hpb[17652]: Checking command line arguments...
May 30 17:56:18 instance3 nextcloud-talk-hpb[17652]: Debug/log level is 3
May 30 17:56:18 instance3 nextcloud-talk-hpb[17652]: Debug/log timestamps are disabled
May 30 17:56:18 instance3 nextcloud-talk-hpb[17652]: Debug/log colors are disabled
May 30 17:56:18 instance3 nextcloud-talk-hpb[17652]: [ERR] [ice.c:janus_ice_set_turn_server:1277] Could not resolve nextcloud.test-x.net:8443...
May 30 17:56:18 instance3 nextcloud-talk-hpb[17652]: [FATAL] [janus.c:main:5309] Invalid TURN address nextcloud.test-x.net:8123:3478
May 30 17:56:18 instance3 nextcloud-talk-hpb[17652]: 2026-05-30 17:56:18,321 WARN exited: janus (exit status 1; not expected)
May 30 17:56:20 instance3 nextcloud-talk-hpb[17652]: settings.go:70: Maximum bandwidth 1 Mbps per publishing stream
May 30 17:56:20 instance3 nextcloud-talk-hpb[17652]: settings.go:78: Maximum bandwidth 2 Mbps per screensharing stream
May 30 17:56:20 instance3 nextcloud-talk-hpb[17652]: janus.go:182: Using a timeout of 10s for MCU requests
May 30 17:56:20 instance3 nextcloud-talk-hpb[17652]: janus.go:194: No candidates allowlist
May 30 17:56:20 instance3 nextcloud-talk-hpb[17652]: janus.go:206: No candidates blocklist
May 30 17:56:20 instance3 nextcloud-talk-hpb[17652]: main.go:287: Could not initialize janus MCU (dial tcp 127.0.0.1:8188: connect: connection refused) will retry in 16s

Where my nextcloud instance is running at nextcloud.test-x.net:8123 configurd via the env parameter NC_DOMAIN and 3478 is configured with the TALK_PORT.

I'm using the backend with the docker container (ghcr.io/nextcloud-releases/aio-talk:latest).

[lminiero]

I don't know why you're opening this issue here, and not on NC Talk. That said, configuring TURN for Janus itself is almost always a terrible idea: TURN should be configured for users to use, not Janus.

[Pharao01]

I don't know why you're opening this issue here, and not on NC Talk. That said, configuring TURN for Janus itself is almost always a terrible idea: TURN should be configured for users to use, not Janus.

Sorry. I found this issue here and that's why I posted my findings. Feel free to ignore it if it does not belong here.