@Magd Almuntaser Wkwkwk SSTI ternyata master kita 🤣🤣🤣

6 minutes ago, Jei Grey said:

bot AI utk settingan multi bot punya saya belum bisa. nama sudah menggunakan huruf kecil semua, node.js sudah dicoba  restart. tetap tidak respon. utk settingan one bot lancar.. 

Ini bekerja secara normal untuk saya, saya hanya mengetikkan gemini di opsi bot dan memanggil namanya di whatsapp seperti ini:
hei gemini apa kabar

9 minutes ago, Serpul Cloud said:

@Magd Almuntaser Wkwkwk SSTI ternyata master kita 🤣🤣🤣

Saya bukan SSTI, saya tidak takut padanya, tapi tetap saja saya akan mati syahid 🤣🤣

@Magd Almuntaser Master, bolehkah saya bertamu 😁😁😁.

1 hour ago, Magd Almuntaser said:

Anda perlu melakukan dua hal seperti yang telah saya jelaskan sebelumnya:
1 - Ubah berkas env untuk mengubah URL situs Anda dari http ke https
2 - Mulai ulang nodejs

Env saya seperti ini tuan

4 hours ago, Magd Almuntaser said:

I apologize. It's working. I tried typing and it works.
Make sure you have restarted nodejs

 

i tried restart, change, stop and start nodejs, nothing happen. "typing" still disappear sir. still "online".

 

Hello Sir, 

 

I am new in this forum so please provide installation document for the same. 

26 minutes ago, Gusik Prasetyo said:

i tried restart, change, stop and start nodejs, nothing happen. "typing" still disappear sir. still "online".

 

HW mean webhook.. typing for webhook:

 

Bot typing:

 

Autorply typing:

Halo, after i update to 7.0.0.5, this happen to my server. Its seem using all resource of my server (using aaPanel).

Anyone same problem? and how to optimase this?

2 hours ago, Enno The Explorer said:

Env saya seperti ini tuan

Silakan ganti file yang terlampir di jalur ini, lalu coba dan beri tahu saya apakah masalahnya sudah teratasi:
 

app/Http/Controllers

 

SettingController.php

After update to v7.0.0.5, node cant start, failed to start.
before i use v7.0.0.2 start all working

44 minutes ago, MURASAKI. said:

Halo, after i update to 7.0.0.5, this happen to my server. Its seem using all resource of my server (using aaPanel).

Anyone same problem? and how to optimase this?

Are you running the node through pm2 or directly from the node?
If you have terminal or ssh, can you type this command and make a screenshot:

top

 

7 minutes ago, Gak Taw said:

After update to v7.0.0.5, node cant start, failed to start.
before i use v7.0.0.2 start all working

Does your node use SSL?
Which control panel do you use, cpanel or aapanel?
Are you running the node through pm2 or directly from the node?

48 minutes ago, MURASAKI. said:

Halo, after i update to 7.0.0.5, this happen to my server. Its seem using all resource of my server (using aaPanel).

Anyone same problem? and how to optimase this?

Same here. My hosting also shown cpu 100% 

Edited August 12, 20241 yr by Unicode

2 minutes ago, Unicode said:

Same here. My hosting also shown cpu 100% 

Ok screenshot your terminal with this command:
top

And are you using pm2 or node?
I need to know exactly where the issue is, whether it's from the pm2 or not.

1 minute ago, Magd Almuntaser said:

Does your node use SSL?
Which control panel do you use, cpanel or aapanel?
Are you running the node through pm2 or directly from the node?

i use aapanel, directly from the node, not use SSL
 

8 minutes ago, Magd Almuntaser said:

Ok screenshot your terminal with this command:
top

And are you using pm2 or node?
I need to know exactly where the issue is, whether it's from the pm2 or not.

My hosting not have terminal feature.

i use node js

1 hour ago, MURASAKI. said:

Halo, after i update to 7.0.0.5, this happen to my server. Its seem using all resource of my server (using aaPanel).

Anyone same problem? and how to optimase this?

 

11 minutes ago, Magd Almuntaser said:

Ok screenshot your terminal with this command:
top

And are you using pm2 or node?
I need to know exactly where the issue is, whether it's from the pm2 or not.

problem fixed after i change server.js with old version 7.0.0.2

Omg i am shocked see my cpu usage

server.js

13 minutes ago, Gak Taw said:

i use aapanel, directly from the node, not use SSL
 

change your server.js with version 7.0.0.2  above bro.

I have upload it

1 minute ago, Unicode said:

change your server.js with version 7.0.0.2  above bro.

I have upload it

Already try, still cant running

Just now, Gak Taw said:

Already try, still cant running

This problem same like my aapanel. Cant running this script.

so i use shared hosting for it

3 minutes ago, Unicode said:

 

problem fixed after i change server.js with old version 7.0.0.2

Omg i am shocked see my cpu usage

server.js 1.97 kB · 0 downloads

Okay, this means one of two things: either the issue is with pm2 or is-online. If pm2 is not the problem, we can consider removing it in the next release.
you can use server.js 7.0.0.2 without problem because the modifications were for pm2 and is-online, you can use server.js 7.0.0.2

i try update and test from 7.0.0.2 until 7.0.0.3 node working properly after update 7.0.0.4 node cant start

1 minute ago, Magd Almuntaser said:

Okay, this means one of two things: either the issue is with pm2 or is-online. If pm2 is not the problem, we can consider removing it in the next release.
you can use server.js 7.0.0.2 without problem because the modifications were for pm2 and is-online, you can use server.js 7.0.0.2

I think that is because node js always sending too many request.

If @MURASAKI. dont say about it, i dont know if 100% of my cpu today cause of server.js

I think cause from my another web

@Magd Almuntaser hello sir. can you make api for get status session?
 so if the user gets status with apikey. then all sessions will appear along with is_connected or not. For example, 3 connects will get a response from 3 sessions

34 minutes ago, Gak Taw said:

After update to v7.0.0.5, node cant start, failed to start.
before i use v7.0.0.2 start all working

If you're using aapanel, it means that you updated the script version without turn off the node first.
I put a warning when updating that you must turn off the node before updating because aapanel has a lot of issues, including hanging the port until the site is restarted.

You have two solutions:
One. Restart the site from the rightmost button on the aapanel control panel.
OR
Second. Change the port number from the env file and restart the node, but remember that you have to open the new port from security