Jump to content
Bicrypto v4.5.0 + All Plugins ×

Whatsapp Gateway | Multi Device v8.5.1


Magd Almuntaser

Recommended Posts

  • DW Members
7 hours ago, MUHAMMAD ADIB MUZAKKI said:

@Magd Almuntaser saya di hosting shared masih tidak bisa menggunakan storagelink dan tidak muncul qrscan

Apakah Anda memiliki Node.js di situs Anda?

Jika iya, apa panel kontrol yang Anda gunakan? Apakah itu cPanel atau aaPanel?

Link to comment
Share on other sites

  • DW Members
1 hour ago, agus amin said:

@Magd Almuntaser Is there a guide to installing on a VPS with Aapanel? I successfully installed on Aapanel without SSL, I want SSL, currently I already have SSL, if there are additional configurations please help

Look i've tried with cpanel and cloudflare ..

But with aapanel i don't try before, so i will try after 2 days because i'm in jakarta now ..

Becouse you need to change some code in script ..

Link to comment
Share on other sites

23 minutes ago, Gusik Prasetyo said:

v6.50 and v7.00 webhook working. may be your script. may be you can post here, so we can check it

Yang tidak dirubah scrip bisa tp yg dirubah gak reply, kalau atau replynya bisa

Link to comment
Share on other sites

47 minutes ago, Magd Almuntaser said:

Apakah maksud Anda bahwa ketika menggunakan script asli webhook berfungsi, tetapi ketika menggunakan script saya webhook tidak berfungsi?

Webhook saya tidak jalan dengan update dari tuan...apakah ada kawan lain yang mengalami? atau pada saya saja yang bermasalah

Link to comment
Share on other sites

1 hour ago, pak kacung said:

Webhook saya tidak jalan dengan update dari tuan...apakah ada kawan lain yang mengalami? atau pada saya saja yang bermasalah

Sama saya juga demikian bro, send via api juga gagal kirim terus, sebelum update aman

Link to comment
Share on other sites

  • DW Members
On 7/9/2024 at 1:35 PM, pak kacung said:

Webhook saya tidak jalan dengan update dari tuan...apakah ada kawan lain yang mengalami? atau pada saya saja yang bermasalah

Tidak ada masalah dengan webhook pada file saya, Anda harus memastikan bahwa Anda memasukkan jalur yang benar untuk webhook dengan format seperti ini:
http://yoursite/webook/index.php
Anda harus menulis nama file yang diwarnai merah.

23 hours ago, agus amin said:

Sama saya juga demikian bro, send via api juga gagal kirim terus, sebelum update aman

👆

6 hours ago, MUHAMMAD ADIB MUZAKKI said:

@Magd Almuntaser sudah jalankan node pada fitur cpanel, hosting saya menggunakan cpanel bukan aapanel

pastikan port Node.js berfungsi di situs Anda melalui tautan ini:
yougetsignal .com/tools/open-ports
Masukkan tautan situs Anda dan nomor port server WhatsApp 3100. Jika muncul berwarna hijau, itu berarti berfungsi dengan benar. Jika muncul berwarna merah, maka Node.js di situs Anda tidak berfungsi dan Anda harus memastikan untuk menjalankannya dengan benar.

  • Thanks 1
Link to comment
Share on other sites

  • DW Members
Posted (edited)

How To Run (Whatsapp Gateway Multi Device) Via SSL
(For All Version)

((Cpanel+Cloudflare))

 

In this guide, we will use SSL for cPanel and Cloudflare users only.

1- we need to know that Cloudflare uses these ports exclusively:

443
2053
2083
2087
2096

8443
We will use port 8443 because it is not used by cPanel.

2-  let's assume the script is located at this domain:

https:// magd.com/ws

We will go to Cloudflare and select SSL/TLS -> Overview, then choose Full.

image.thumb.jpeg.27a536c007888bb9469fa03d971a8c28.jpeg

 

3- we will edit the .env file located in the root directory of the script and change these fields to https:// and Port to 8443
 

APP_URL=https://magd .com
WA_URL_SERVER=https://magd .com:8443
PORT_NODE=8443

4- we will login to cPanel, go to SSL/TLS:

image.jpeg.665b2a65a119f62217e5539beaa117ad.jpeg

and then Manage SSL sites:

image.jpeg.e34273c20eb386411ff6dcbe3176d844.jpeg

5- Now we will select Use Certificate for New Site:

image.jpeg.834449444e0a8b069fa6f4da36c9e5dd.jpeg

Two fields will appear. The first is Certificate: (CRT) which we will copy and save in a file named cert.pem. The other is Private Key (KEY) which we will save in a file named key.pem:

image.jpeg.087e3b6d551147b10f973ab1b7ec994b.jpeg

6- We will upload the two files we saved, cert.pem and key.pem, to the root directory of the script. Then, we will edit the server.js file and replace this code from:

/**
 * EXPRESS FOR ROUTING
 */
const express = require("express");
const app = express();
const http = require("http");
const server = http.createServer(app);

To:
 

/**
 * EXPRESS FOR ROUTING
 */
const serverOptions = {
  key: fs.readFileSync('key.pem'),
  cert: fs.readFileSync('cert.pem')
}

const express = require("express");
const app = express();
const https = require("https");
const server = https.createServer(serverOptions, app);

7- And finally, the last step, is to edit the routes/web.php file and add this code at the end of the file:
 

URL::forceScheme('https');

 

Now you can restart Node.js and enjoy using the script over HTTPS
I will later post how to use SSL on the aaPanel control panel. Therefore, if anyone has a website using this panel, please send your site details (PM) so I can use them for the explanation, as I don't currently have aaPanel 🙂

Edited by Magd Almuntaser
  • Like 1
  • Love 1
Link to comment
Share on other sites

20 hours ago, Magd Almuntaser said:

Cara Menjalankan (Whatsapp Gateway Multi Device) Melalui SSL
(Untuk Semua Versi)

((Cpanel+Cloudflare))

 

Dalam panduan ini, kami akan menggunakan SSL untuk pengguna cPanel dan Cloudflare saja .

1- kita perlu tahu bahwa Cloudflare menggunakan port ini secara eksklusif:

443
2053
2083
2087
2096

8443
Kami akan menggunakan port 8443 karena tidak digunakan oleh cPanel.

2-   mari kita asumsikan skrip tersebut terletak di domain ini:



		

Kita akan masuk ke Cloudflare dan pilih SSL/TLS -> Ikhtisar, lalu pilih Penuh.

gambar.thumb.jpeg.27a536c007888bb9469fa03d971a8c28.jpeg

 

3- kita akan mengedit file .env yang terletak di direktori root skrip dan mengubah bidang ini menjadi https:// dan Port menjadi 8443
 

4-  kita akan login ke cPanel, masuk ke SSL/TLS :

gambar.jpeg.665b2a65a119f62217e5539beaa117ad.jpeg

lalu Kelola situs SSL:

gambar.jpeg.e34273c20eb386411ff6dcbe3176d844.jpeg

5- Sekarang kita akan memilih Gunakan Sertifikat untuk Situs Baru :

gambar.jpeg.834449444e0a8b069fa6f4da36c9e5dd.jpeg

Dua kolom akan muncul. Yang pertama adalah Certificate: (CRT) yang akan kita salin dan simpan dalam file bernama cert.pem . Yang kedua adalah Private Key (KEY) yang akan kita simpan dalam file bernama key.pem :

gambar.jpeg.087e3b6d551147b10f973ab1b7ec994b.jpeg

6-  Kita akan mengunggah dua file yang kita simpan, cert.pem  dan key.pem , ke direktori root skrip. Kemudian, kita akan mengedit file server.js dan mengganti kode ini dari:





Ke:
 


 





7- Dan akhirnya, langkah terakhir, adalah mengedit file routes/web.php dan menambahkan kode ini di akhir file:
 

 

Sekarang Anda dapat memulai ulang Node.js dan menikmati penggunaan skrip melalui HTTPS .
Nanti saya akan memposting cara menggunakan SSL di panel kontrol aaPanel . Oleh karena itu, jika ada yang memiliki situs web yang menggunakan panel ini, silakan kirim detail situs Anda (PM) sehingga saya dapat menggunakannya untuk penjelasannya, karena saat ini saya tidak memiliki aaPanel . :)

Ada kelebihan apa tuan dengan cara ini?

Link to comment
Share on other sites

  • DW Members
Posted (edited)
13 hours ago, pak kacung said:

Ada kelebihan apa tuan dengan cara ini?

Dengan cara ini, koneksi Anda akan aman, dan juga koneksi Anda ke server WhatsApp yang sebenarnya akan melalui WSS yang aman dan kompatibel dengan WhatsApp. Terakhir, ada kesulitan dalam menggunakan situs dengan Cloudflare karena sebagian besar situs menggunakan HTTPS secara default, yaitu (force redirect to https), sehingga akan sulit menjalankan skrip kecuali Anda menonaktifkan fitur ini di situs Anda.

25 minutes ago, agus amin said:

@Magd Almuntaser agar auto konek bagaimana settingnya om, setelah konek, besok pagi diskonek, node js berjalan normal semua, hanya itu saja saat ini masalahnya?

 

You can see my comment on page number 34 about:

npm install pm2@latest -g

Edited by Magd Almuntaser
Link to comment
Share on other sites

On 7/12/2024 at 11:38 AM, pak kacung said:

menurut saya itu juga tergantung hostingnya

Saya pakai VPS om, status Connect di MPWA, tapi di WA Disconnect, harus logout dulu, login lagi begitu seterusnya wkwkk belum dapat obat nya saya hikk

Link to comment
Share on other sites

 

@Magd Almuntaser

please what's is the solution?
This seems to be the cause of the disconnect.

 

/home/bspsun/subdomain/wa.bspsun.com/node_modules/@whiskeysockets/baileys/lib/Utils/generics.js:137
            .then(() => reject(new boom_1.Boom('Timed Out', {
                               ^

Error: Timed Out
    at /home/bspsun/subdomain/wa.bspsun.com/node_modules/@whiskeysockets/baileys/lib/Utils/generics.js:137:32 {
  data: {
    stack: 'Error\n' +
      '    at promiseTimeout (/home/bspsun/subdomain/wa.bspsun.com/node_modules/@whiskeysockets/baileys/lib/Utils/generics.js:132:19)\n' +
      '    at waitForMessage (/home/bspsun/subdomain/wa.bspsun.com/node_modules/@whiskeysockets/baileys/lib/Socket/socket.js:119:53)\n' +
      '    at query (/home/bspsun/subdomain/wa.bspsun.com/node_modules/@whiskeysockets/baileys/lib/Socket/socket.js:141:22)\n' +
      '    at sendPassiveIq (/home/bspsun/subdomain/wa.bspsun.com/node_modules/@whiskeysockets/baileys/lib/Socket/socket.js:331:37)\n' +
      '    at WebSocketClient.<anonymous> (/home/bspsun/subdomain/wa.bspsun.com/node_modules/@whiskeysockets/baileys/lib/Socket/socket.js:515:15)\n' +
      '    at processTicksAndRejections (node:internal/process/task_queues:96:5)'
  },
  isBoom: true,
  isServer: false,
  output: {
    statusCode: 408,
    payload: {
      statusCode: 408,
      error: 'Request Time-out',
      message: 'Timed Out'
    },
    headers: {}
  }
}

Link to comment
Share on other sites

  • DW Members
38 minutes ago, The Billionaire said:

Tolong apakah ada yang tahu alasan mengapa koneksi terus terputus setelah beberapa hari

Please does anybody know the reason why it keeps disconnecting after some days

If you mean the connection from Node.js is getting disconnected:
I installed PM2.js, and now it's been 7 months without any interruptions, except for two times when I stopped it to update the version.
I tried using (forever.js) before, but it was bad and had many issues. However, PM2.js is very good; it even gives me a link through which I can monitor issues or restart the Node, among other things.

If you mean logging out of WhatsApp:
In the version I have, I haven't been logged out of the session for a long time. This might be because I modified the server.js file to keep WhatsApp always connected. Anyway, I will prepare the latest version of my modifications today and upload it as a complete compressed file with instructions on how to update your version without any issues.

7 minutes ago, Putra Pertama said:

 

@Magd Almuntaser

please what's is the solution?
This seems to be the cause of the disconnect.

 

/home/bspsun/subdomain/wa.bspsun.com/node_modules/@whiskeysockets/baileys/lib/Utils/generics.js:137
            .then(() => reject(new boom_1.Boom('Timed Out', {
                               ^

Error: Timed Out
    at /home/bspsun/subdomain/wa.bspsun.com/node_modules/@whiskeysockets/baileys/lib/Utils/generics.js:137:32 {
  data: {
    stack: 'Error\n' +
      '    at promiseTimeout (/home/bspsun/subdomain/wa.bspsun.com/node_modules/@whiskeysockets/baileys/lib/Utils/generics.js:132:19)\n' +
      '    at waitForMessage (/home/bspsun/subdomain/wa.bspsun.com/node_modules/@whiskeysockets/baileys/lib/Socket/socket.js:119:53)\n' +
      '    at query (/home/bspsun/subdomain/wa.bspsun.com/node_modules/@whiskeysockets/baileys/lib/Socket/socket.js:141:22)\n' +
      '    at sendPassiveIq (/home/bspsun/subdomain/wa.bspsun.com/node_modules/@whiskeysockets/baileys/lib/Socket/socket.js:331:37)\n' +
      '    at WebSocketClient.<anonymous> (/home/bspsun/subdomain/wa.bspsun.com/node_modules/@whiskeysockets/baileys/lib/Socket/socket.js:515:15)\n' +
      '    at processTicksAndRejections (node:internal/process/task_queues:96:5)'
  },
  isBoom: true,
  isServer: false,
  output: {
    statusCode: 408,
    payload: {
      statusCode: 408,
      error: 'Request Time-out',
      message: 'Timed Out'
    },
    headers: {}
  }
}

I think you have an issue with some modules in Node being incompatible due to version differences. Today, I will upload the latest modifications I have in a compressed file, and you can update your version with mine. It works without any issues, and most of the problems you faced have been fixed.

  • Like 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...