nextcloud / nextcloud/spreed

No way to remove default STUN

Open
#9,182 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug feature: WebRTC 🚡
Dominant language
PHP
Stars
2.2k
Forks
587
Avg merge
18h 27m
Merged PRs (30d)
333

Description

I have deployed nextcloud and talk in the private network, and nextcloud talk server cannot access the Internet, which means there is no way to access any public network deployed stun server, including the default stun.nextcloud.com: 443, how should I configure it

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the issue details and locating how Nextcloud Talk configures the default stun.nextcloud.com:443 server for deployments without Internet access. Define how an administrator should remove or replace that default, then verify that a private-network deployment can operate without attempting to reach a public STUN server.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
audio-video-rtc, networking
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.