Skip to content

Instantly share code, notes, and snippets.

@mwild1
Last active January 26, 2021 19:15
Show Gist options
  • Star 2 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save mwild1/aa2af95b520bd44283d9062e7846a874 to your computer and use it in GitHub Desktop.
Save mwild1/aa2af95b520bd44283d9062e7846a874 to your computer and use it in GitHub Desktop.
Snikket Server: Updating from the initial alpha release to 20200512+

This update requires changes to the configuration of the container. Assuming you followed the quickstart guide on our website, you need do the following:

cd /etc/snikket

Open docker-compose.yml and remove the 'ports' section, and add network_mode:host. You can view the changes you need to make, or just fetch the updated version of docker-compose.yml. For the alpha releases make sure your image: is set to snikket/snikket:alpha in docker-compose.yml.

Once you have updated docker-compose.yml simply update the service with the command:

docker-compose pull
docker-compose up -d

If all is well, you'll now have a working version of Snikket with audio/video support! :)

Snikket behind a reverse proxy

Despite warnings to the contrary in the quickstart, I know some of you are running Snikket in more adventurous setups... :) Here are some notes for you.

Snikket will now attempt to listen directly on port 80 and port 443 of the host server, which will cause a conflict with any other HTTP server that might be running. There is no ability to use Docker to remap ports now. However there are now some options you can add to snikket.conf (i.e. environment variables) to override the default HTTP(S) ports:

SNIKKET_TWEAK_HTTP_PORT=80
SNIKKET_TWEAK_HTTPS_PORT=443

You will need to adjust the configuration of your reverse proxy after making these changes, but as everyone has a different setup for this, you'll have to figure that out!

Firewalls

In addition to the existing HTTP, HTTPS and XMPP ports, Snikket now requires a bunch of additional TCP and UDP ports for relaying voice/video data during calls.

  • TCP only: 80, 443, 5222, 5269
  • TCP and UDP: 3478, 3479, 5349, 5350
  • UDP only: 49152-65535
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment