Weesify

Weesify Meetings: install the media engine

For the server owner: install the media engine from the Console, open the firewall ports and check that calls connect.

2 min read · Updated 30 October 2026

Weesify Meetings carries audio and video with the Weesify Media Engine, which runs on your own server. No Zoom, Google Meet or outside video service is used. You install it once from the Console. No terminal is needed.

1. Install the engine

  1. Sign in to the Console and open Console › Meetings.
  2. Under Weesify Media Engine, choose Install. It downloads about 30 MB and installs in the background. You can leave the page.
  3. When the status shows Running, the engine is ready. The scheduler keeps it running.

2. Open the firewall ports

The engine uses ports above 1024, so it runs as your hosting account. Open these ports in your server's firewall:

Protocol Port What it is for
UDP 7882 Audio and video (the fastest path)
TCP 7881 Audio and video when UDP is blocked
UDP 3478 TURN relay for strict networks
TCP (TLS) 5349 TURN over TLS for strict office and mobile networks
UDP 40000–40199 Relay ports used by TURN

On WHM with ConfigServer Security & Firewall:

  1. Sign in to WHM as root.
  2. Search for ConfigServer and open ConfigServer Security & Firewall.
  3. Choose Firewall Configuration.
  4. Add the TCP ports (7881, 5349) to TCP_IN, and the UDP ports (7882, 3478, 40000:40199) to UDP_IN, each after a comma.
  5. Scroll down, choose Change, then Restart csf+lfd.

3. Let Apache pass signalling to the engine

Browsers reach the engine through your site at /_media. This needs Apache's proxy modules:

  1. In WHM, open EasyApache 4 and choose Customize.
  2. Under Apache Modules, switch on mod_proxy, mod_proxy_http and mod_proxy_wstunnel.
  3. Choose Review, then Provision.

Weesify's .htaccess already holds the rule that uses them.

4. Check it works

  1. Back in Console › Meetings, choose Check signalling. It should say Working.
  2. Choose Run browser test. It sends a moving test pattern from your browser to the engine and back, and reports whether media went over UDP, TCP or the TURN relay.
  3. For TURN over TLS, choose Read the AutoSSL certificate for your TURN domain.

Tips

  • Video meetings is the master switch. When it is off, meeting rooms say plainly that video isn't available.
  • Server limits protect your bandwidth: people at once, meetings at once and the longest meeting.
  • Stop ends meetings in progress. New keys disconnects meetings, and people can rejoin.

Was this guide helpful?

No

Still stuck?

Tell us what’s going on and a real person will get back to you, usually within a working day.

What we’re building

See what’s planned, in progress and just shipped, and vote for what you want next.