This is part of the VPS Installation Guide!
Do not proceed if you are not using the recommendations from the Introduction step!
In this step, we will guide you on how to setup the WhatsApp server on the same VPS.
Login to your Zender site using the admin credentials you set during installation.
In the sidebar go to "ADMIN PANEL" then click "WA SERVERS".
Click "ADD SERVER":

Add the following details then press "SUBMIT":
You should copy the exact "Server URL" and "Server Port" from the image because the WhatsApp server is hosted on the same environment. Only change the value of "Secret Key". Make sure that your secret key only contains alpha numeric characters.

After that, click the green button:

A modal will popup. Copy the highlighted command because we will use it later:

Login to your VPS again via SSH using PuTTY.
Run these commands:
Replace "yourzenderdomain.com" with your actual Zender domain.
cd /home/admin/web/yourzenderdomain.commkdir whatsappcd whatsappNow run the command you copied from the modal and wait until it finish.
Run these commands:
sudo apt -y install npmsudo npm install n -gsudo n ltssudo rebootYour VPS will now reboot, wait for 5 minutes then login to SSH again.
Run these commands:
sudo npm install pm2 -gpm2 statusReplace "yourzenderdomain.com" with your actual Zender domain.
cd /home/admin/web/yourzenderdomain.com/whatsappReplace "PURCHASE_CODE" with your Zender purchase code and "SECRET_KEY" with your WA server entry secret key.
sudo pm2 start ./titansys-whatsapp-linux --name "WA Server" -- --pcode="PURCHASE_CODE" --key="SECRET_KEY" --host="0.0.0.0" --port="8899"pm2 saveAfter doing all the above steps, you should see the WA server online in your Zender admin dashboard:

You can now start linking WhatsApp accounts. PM2 will keep the WA server running in the background even if you restart the VPS.
You can view the running processes by using this command in the terminal:
pm2 statusIf you need to update the WA server, you should stop it first by running this command:
pm2 stop allAfter updating, start it again:
pm2 restart allpm2 save