I’ve been running Nextcloud in a Docker container with its own MacVLAN for a while now to make files available online (via my own domain). I’m using the “classic” Nextcloud in Docker, not the Nextcloud All-in-One.
Now I’d like to activate and use Nextcloud Talk as well. I’ve read that this requires setting up a TURN server and integrating it into Nextcloud for Talk. Sounds complicated?
Is that really the case, or can Nextcloud Talk be used without a TURN server? If not, can someone recommend a Docker-based TURN server that I can use with my local Nextcloud instance in Docker with MacVLAN? Is there any documentation on how to set up such a system?
I’ve looked at the links and other posts on this topic. Thanks for that. The answer I’ve gathered is: Yes, I would need a TURN server to use Nextcloud Talk, but I don’t know if it’s worth the effort. From what I’ve read, setting up a TURN server is quite complicated and prone to errors. Some users have written that they eventually gave up.
Then I also read that a TURN server isn’t enough. I would probably also need a WebRTC signaling server.
Everywhere I read, it’s about setting it up on a host PC or in a Docker container on the host network. However, I assume that with my Nextcloud setup (with Caddy and other web services) in a Docker container with its own MacVLAN, there are entirely different challenges. Furthermore, I plan to move my web services to a separate network behind a router running OpenWRT (which is behind the Netzwork of FritzBox) in the future, as this will allow me to use additional security mechanisms.
Then I read everywhere that it’s best to set it up on a host PC or in a Docker container on the host network. One solution that might simplify things is switching from regular Nextcloud in Docker to Nextcloud All-in-One. My question is whether and how I can switch from my somewhat complex setup of “classic Nextcloud in Docker” to Nextcloud All-in-One (in Docker), ideally without having to reconfigure everything.
Another question I have is whether a TURN server can have a domain independent of my Nextcloud domain. I’m currently using a free DynDNS subdomain from IPV64.net and can’t add another prefix like turn.nextcloud.ipv64.net.
Besides the Nextcloud forum, is there another forum for hobby users here? Thanks for the welcome, but I’m not actually new here. I’ve avoided the forum so far because my few inquiries were always met with rather harsh and unfriendly responses.
I showed you easy ways to setup TURN server and you keep asking for alternatives.. did you try and hit any issue? then please ask the question using support template and many details, open one topic for each specific..
You write you read a lot - I also prefer to understand things before I start.. but there is no reason to switch back and forth different architectures just because the other look little better. There many installation kinds - from native, AiO, docker micro-service, snap to NextcloudPi etc and each of them covers specific niche, has advantages and drawbacks.
I would recommend to stick a technology you know best because self-hosting not only involves setup and initial configuration but also continuos operation efforts like backup which you need to adjust if you change your architecture..
I’m sorry to hear you didn’t feel welcome we definitely look for civilized discussions. but honestly if your previous questions are similar I can understand kind of “not welcoming” responses… Please don’t forget people spend their spare time here to hep others.. and you are asking open questions about multiple different complex questions which have been discussed many many many times already
