search

ldurans / izing.open.io

Chats Whatsapp multisessões
503 stars 278 forks source link

Problema nos Multíplos usuários simultâneos por canais de atendimento #198

Open XNINGUEMX opened 4 months ago

XNINGUEMX commented 4 months ago

Boa tarde.

Estou tentando acessar o Izing com usuários criados no painel do administrador, porem quando coloco e-mail e senha criada para um usuário e tento acessar pelo ip:8080 em outra maquina na mesma rede carrega a barra azul mas não acessa o aplicativo, eu fiz também ate uma conexão via túnel com cloudflare + registro.br mesmo assim deu o mesmo problema, acredito que não estou conseguindo estabelecer uma conexão de entrada somente saída esta funcionando pois consigo acessar a pagina de login, mas não consigo logar.

Alguém tem alguma dica para ajudar?

Logs info: 2024-05-22T15:52:00.094Z SendMessageSchenduled Initiated info: 2024-05-22T15:52:00.120Z Finalized SendMessageSchenduled error: 2024-05-22T15:52:21.389Z jwt must be provided - JsonWebTokenError: jwt must be provided at module.exports (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\jsonwebtoken\verify.js:53:17) at decode (C:\Users\rEALPIX\Desktop\izing.open.io\backend\dist\libs\decodeTokenSocket.js:19:51) at C:\Users\rEALPIX\Desktop\izing.open.io\backend\dist\libs\socket.js:45:60 at Generator.next () at C:\Users\rEALPIX\Desktop\izing.open.io\backend\dist\libs\socket.js:8:71 at new Promise () at __awaiter (C:\Users\rEALPIX\Desktop\izing.open.io\backend\dist\libs\socket.js:4:12) at Array. (C:\Users\rEALPIX\Desktop\izing.open.io\backend\dist\libs\socket.js:41:30) at run (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\socket.io\dist\namespace.js:66:19) at Namespace.run (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\socket.io\dist\namespace.js:77:9) at Namespace._add (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\socket.io\dist\namespace.js:110:14) at Client.doConnect (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\socket.io\dist\client.js:98:28) at Client.connect (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\socket.io\dist\client.js:69:25) at Client.ondecoded (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\socket.io\dist\client.js:206:22) at Emitter.emit (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\component-emitter\index.js:145:20) at Decoder.add (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\socket.io\node_modules\socket.io-parser\dist\index.js:120:23) at Client.ondata (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\socket.io\dist\client.js:188:26) at Socket.emit (node:events:517:28) at Socket.emit (node:domain:489:12) at Socket.onPacket (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\engine.io\lib\socket.js:121:16) at WebSocket.emit (node:events:517:28) at WebSocket.emit (node:domain:489:12) at WebSocket.onPacket (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\engine.io\lib\transport.js:86:10) at WebSocket.onData (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\engine.io\lib\transport.js:96:10) at WebSocket.onData (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\engine.io\lib\transports\websocket.js:59:11) at WebSocket.emit (node:events:517:28) at WebSocket.emit (node:domain:489:12) at Receiver.receiverOnMessage (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\engine.io\node_modules\ws\lib\websocket.js:834:20) at Receiver.emit (node:events:517:28) at Receiver.emit (node:domain:489:12) at Receiver.dataMessage (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\engine.io\node_modules\ws\lib\receiver.js:437:14) at Receiver.getData (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\engine.io\node_modules\ws\lib\receiver.js:367:17) at Receiver.startLoop (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\engine.io\node_modules\ws\lib\receiver.js:143:22) at Receiver._write (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\engine.io\node_modules\ws\lib\receiver.js:78:10) error: 2024-05-22T15:52:21.410Z jwt must be provided - JsonWebTokenError: jwt must be provided at module.exports (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\jsonwebtoken\verify.js:53:17) at decode (C:\Users\rEALPIX\Desktop\izing.open.io\backend\dist\libs\decodeTokenSocket.js:19:51) at C:\Users\rEALPIX\Desktop\izing.open.io\backend\dist\libs\socket.js:45:60 at Generator.next () at C:\Users\rEALPIX\Desktop\izing.open.io\backend\dist\libs\socket.js:8:71 at new Promise () at __awaiter (C:\Users\rEALPIX\Desktop\izing.open.io\backend\dist\libs\socket.js:4:12) at Array. (C:\Users\rEALPIX\Desktop\izing.open.io\backend\dist\libs\socket.js:41:30) at run (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\socket.io\dist\namespace.js:66:19) at Namespace.run (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\socket.io\dist\namespace.js:77:9) at Namespace._add (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\socket.io\dist\namespace.js:110:14) at Client.doConnect (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\socket.io\dist\client.js:98:28) at Client.connect (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\socket.io\dist\client.js:69:25) at Client.ondecoded (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\socket.io\dist\client.js:206:22) at Emitter.emit (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\component-emitter\index.js:145:20) at Decoder.add (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\socket.io\node_modules\socket.io-parser\dist\index.js:120:23) at Client.ondata (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\socket.io\dist\client.js:188:26) at Socket.emit (node:events:517:28) at Socket.emit (node:domain:489:12) at Socket.onPacket (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\engine.io\lib\socket.js:121:16) at WebSocket.emit (node:events:517:28) at WebSocket.emit (node:domain:489:12) at WebSocket.onPacket (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\engine.io\lib\transport.js:86:10) at WebSocket.onData (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\engine.io\lib\transport.js:96:10) at WebSocket.onData (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\engine.io\lib\transports\websocket.js:59:11) at WebSocket.emit (node:events:517:28) at WebSocket.emit (node:domain:489:12) at Receiver.receiverOnMessage (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\engine.io\node_modules\ws\lib\websocket.js:834:20) at Receiver.emit (node:events:517:28) at Receiver.emit (node:domain:489:12) at Receiver.dataMessage (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\engine.io\node_modules\ws\lib\receiver.js:437:14) at Receiver.getData (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\engine.io\node_modules\ws\lib\receiver.js:367:17) at Receiver.startLoop (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\engine.io\node_modules\ws\lib\receiver.js:143:22) at Receiver._write (C:\Users\rEALPIX\Desktop\izing.open.io\backend\node_modules\engine.io\node_modules\ws\lib\receiver.js:78:10)

rownaas commented 3 months ago

Opa amigo, verificou se apareceu alguma coisa dentro do console do navegador ao fazer a requisição de login? As vezes pode ser por conta do cors, dai você precisa instalar uma extensão no navegador chamada cors unblock, quando ativa ela resolve este problema, além disto pode ser algum erro de rota do frontend pra api/backend

XNINGUEMX commented 3 months ago

O amigo muito obrigado pela dica a principio agora consigo acessar no mesmo PC usando cors unblock com host ip e tunel, porem quando vou logar, em outro PC mesmo tendo também a extenção cors unblock não loga no console do Chorme da esses erros aqui. mesmo assim muito obrigado pela dica ^^ vou continuar tentando resolver esse probleminha se siter mais uma saida por onde devo estudar eu agradeço ^^

   Failed to load resource: net::ERR_CONNECTION_REFUSED

websocket.js:87 WebSocket connection to 'ws://localhost:3100/socket.io/?EIO=4&transport=websocket' failed: doOpen @ websocket.js:87 Mostrar mais 1 frame Mostre menos socket.js:21 socket error Error: websocket error at WS.onError (transport.js:29:1) at ws.onerror (websocket.js:116:1) (anónimo) @ socket.js:21 websocket.js:87 WebSocket connection to 'ws://localhost:3100/socket.io/?EIO=4&transport=websocket' failed: doOpen @ websocket.js:87 Mostrar mais 1 frame Mostre menos websocket.js:87 WebSocket connection to 'ws://localhost:3100/socket.io/?EIO=4&transport=websocket' failed: doOpen @ websocket.js:87 Mostrar mais 1 frame Mostre menos socket.js:21 socket error Error: websocket error at WS.onError (transport.js:29:1) at ws.onerror (websocket.js:116:1) (anónimo) @ socket.js:21 push../node_modules/component-emitter/index.js.Emitter.emit @ index.js:145 (anónimo) @ manager.js:127 push../node_modules/component-emitter/index.js.Emitter.emit @ index.js:145 onError @ socket.js:594 (anónimo) @ socket.js:213 push../node_modules/component-emitter/index.js.Emitter.emit @ index.js:145 onError @ transport.js:32 ws.onerror @ websocket.js:116 Mostrar mais 8 frames Mostre menos websocket.js:87 WebSocket connection to 'ws://localhost:3100/socket.io/?EIO=4&transport=websocket' failed: doOpen @ websocket.js:87 open @ transport.js:44 open @ socket.js:183 Socket @ socket.js:107 push../node_modules/engine.io-client/lib/index.js.module.exports @ index.js:3 open @ manager.js:112 (anónimo) @ manager.js:339 Mostrar mais 7 frames Mostre menos websocket.js:87 WebSocket connection to 'ws://localhost:3100/socket.io/?EIO=4&transport=websocket' failed: doOpen @ websocket.js:87 open @ transport.js:44 open @ socket.js:183 Socket @ socket.js:107 push../node_modules/engine.io-client/lib/index.js.module.exports @ index.js:3 open @ manager.js:112 (anónimo) @ manager.js:339 Mostrar mais 7 frames Mostre menos socket.js:21 socket error Error: websocket error at WS.onError (transport.js:29:1) at ws.onerror (websocket.js:116:1)