I have NC and the Talk app installed, and I have Spreed running on another container. However, when I try to connect to Spreed (either with curl, a browser, or configuring it in Talk) I get an HTTP 404 error with a trivial “page not found” body.
This happens for the root and for the /standalone-signaling path that the Spreed README (above) says to use. The documentation doesn’t indicate where else to point it. Am I missing something?
Related: Does the Spreed server need any open ports beyond 80/443? It seems like the optional external NATS server does, but I am not using that. (Because my web host doesn’t support non-HTTP ports.)
Yes, it’s not that simple indeed. Check the comments of the linked post for some simplifications, someone provides pre-built packages. That at least takes away some of the complexity but it still is a non-trivial setup.
Technically what I’m trying to do here is make a BigBlueButton setup for running Talk on the webhost I work for, Platform.sh. We’re all container based, but not Docker based, so I can’t just yoink a Docker setup. We also only support incoming/outgoing HTTP ports to the public right now (for security), which seems to kill the idea. :-/