ldurans / izing.open.io Goto Github PK

Não da para ouvir as gravaçoes de audios, nao exibi videos, fotos e documentos

Atendimento funciona normal quando não há filas cadastradas.

Ao cadastrar uma nova fila, não aparece nenhum ticket no atendimento, além disso, o chatbot não funciona, testei com vários números, incluindo business com e sem chrome.

Alguém dá uma luz?

Como fazer login no admin front end, instalei e mudei a url da api no quasar.conf.js, mas quando tendo login com as credenciais padrao ele entra e expira o login na hora

Teria como definir um bot separado para cada canal?

Nao estou conseguindo criar o qrcode para whatsapp, nos logs do back aparece:

error: 2022-11-16T14:20:04.095Z ERROR: checkMessages Tenant: 1:: Cannot read property 'evaluate' of null - TypeError: Cannot read property 'evaluate' of null
0|izing-backend | at Client.getState (/home/deploy/izing.io/backend/node_modules/whatsapp-web.js/src/Client.js:845:35)
0|izing-backend | at /home/deploy/izing.io/backend/src/libs/wbot.ts:31:49
0|izing-backend | at Generator.next ()
0|izing-backend | at /home/deploy/izing.io/backend/dist/libs/wbot.js:8:71
0|izing-backend | at new Promise ()
0|izing-backend | at __awaiter (/home/deploy/izing.io/backend/dist/libs/wbot.js:4:12)
0|izing-backend | at Timeout.checkMessages [as _onTimeout] (/home/deploy/izing.io/backend/src/libs/wbot.ts:29:74)
0|izing-backend | at listOnTimeout (internal/timers.js:559:11)
0|izing-backend | at processTimers (internal/timers.js:500:7)

Tem alguma informação sobre este erro?

Obrigado

Ola, tinha a versão 1.6 e ao atualizar para a versão 1.9, as mensagens trocadas não são mostradas automaticamente, tanto as recebidas como as enviadas, somente após apertar F5 para Atualizar elas aparecem.

Estou com problema na hora de gerar o qrcode do whatsapp, fica aternamente gerando e nada acontece. Analizando o banco de dados da pra ver que realmente não é gerado

Boa Tarde,

Estou percencendo que quando o bot transfere uma mensagem para uma fila a notificação não está acontecendo, e também algumas vezes está tendo problemas na notificação de novas mensagens.

Criar canal de atendimento E-mail, para que seja possível atender por e-mail.

Ao criar uma nova tenant, é necessário realizar a criação dos parâmetros para correto funcionamento.

Sistema está apresentando em Pendentes no Painel Atendimentos, tickets que já foram Resolvidos

Ao criar uma CAMPANHA, o campo "Enviar por" está vazio e não permite selecionar nenhum dado.

Olá, qual as configurações recomendadas para vps para rodar o projeto? Estou com uma maquina de 2gb de ram e 1 vCPU e o npm install trava.

Acessei as configurações dentro do chatbot, configurei o mesmo, e na hora de definir a repetição eu colocava o 1 ele seta o 1 na interface, porém no serviço continua repetindo 3 Vezes.

---BUG---
Nao esta funcionando a parte de notificações de som quando chega mensagem.

---SUGESTÕES---
No whaticket tem o popup tambem porem esta encrito em react, nao sei se tem na linguagem que usa no front ni izing essa opcao

Na tela de ticket mostrar no ticket qual conexao esta usando em caso de ter mais de 1 whatsapp ou outro, mostrar o nome da conexao embaixo do nome.

Ter um botao de selecao no chat para ocultar ou nao o nome do usuario na resposta.

No menu de Dashboard o campo de Ativo e Receptivo estão com as informações trocadas

Em algum momentos trava no status oppening. Implementar timeout no front para que seja possível solicitar nova tentativa.

Seria muito bom se fosse possivel ao finalizar ou em algum momento tivesse como colocar uma tag para cada chat, para que possamos ter como acompanha os pricipais tópicos de atendimentos.
ex.: Cadastraria algumas Tags como Suporte Impressoras, Instalação de Programas, Erro no sistema.
Quando o cliente entresse em contato iriamos classificar aquele ticket com a tag conforme problema, e tivesse como acompanhar quantos atendimento fizemos sobre aquele tag no periodo pelo dashboard ou relatorio.

Uma sugestão de melhoria para melhorar a comunicação com o cliente, é de colocar uma mensagem de encerramento do ticket, isso pode ocorrem quando atendente finaliza o ticket ou quando o cliente digitar o valor correspondente ao parâmetro configurado em configurações do ChatBot.

Uma sugestão de melhoria seria disponibilizar variáveis como, Saudações, Nome do Contato, Numero do contato, Número de Protocolo (ex: data+hora+numero do ticket) para que estas possam ser utilizadas no envio das mensagens, construção do chatbot e envio de campanhas, abaixo uma sugestão:

Opção de deletar mensagem não está habilitando mesmo estando dentro do prazo de 5 minutos estabelecido pelo sistema

está dando um problema quando estou instalando o izing via docker.

analisando os container vi que tem um que não está iniciando.

gostaria de saber como posso está fazendo para resolver esse problema?

Quando vou cadastrar o CHATBOT e coloco a condição se qualquer Resposta e quando mando mensagem e respondo qualquer coisa, ele me retorna o erro falando que nao entendeu a minha resposta, e nao segue e condição.

Ao iniciar o atendimento. o ticket está sumindo da listagem e não fica focado como desejado.

Instalei o docker o postgre e tudo mais, porém me gera varios erros ao executar os códigos no terminal :

PS C:\Users\dfsil\OneDrive\Área de Trabalho\projetoNovo\izing.io> docker compose -f "docker-compose.yml" up -d --build
time="2022-12-15T00:59:00-03:00" level=warning msg="The "HOME" variable is not set. Defaulting to a blank string."
time="2022-12-15T00:59:00-03:00" level=warning msg="The "HOME" variable is not set. Defaulting to a blank string."
time="2022-12-15T00:59:00-03:00" level=warning msg="The "HOME" variable is not set. Defaulting to a blank string."
time="2022-12-15T00:59:00-03:00" level=warning msg="The "HOME" variable is not set. Defaulting to a blank string."
time="2022-12-15T00:59:00-03:00" level=warning msg="The "HOME" variable is not set. Defaulting to a blank string."
time="2022-12-15T00:59:00-03:00" level=warning msg="The "HOME" variable is not set. Defaulting to a blank string."
time="2022-12-15T00:59:00-03:00" level=warning msg="The "HOME" variable is not set. Defaulting to a blank string."
open C:\Users\dfsil\OneDrive\Área de Trabalho\projetoNovo\izing.io\backend.env: O sistema não pode encontrar o arquivo especificado.

Como posso solucionar?

Para que as conversar atualizem em alguns testes (esta intermitente) é necessário teclar F5 para que as novas e atuais conversas sejam mostradas na tela de atendimento.

Error compiling or running docker

Running docker:

[izingio-izing-backend 11/14] RUN npm run build:
#0 0.513
#0 0.513 > [email protected] build /usr/src/app
#0 0.513 > tsc
#0 0.513
#0 16.30 node_modules/@types/express-serve-static-core/index.d.ts(99.68): error TS1110: type expected.
#0 16.30 node_modules/@types/express-serve-static-core/index.d.ts(99.77): TS1005 error: '}' expected.

Compiling manually:

root@vmi675017:/opt/izing.io/backend# npm run build

[email protected] build /opt/izing.io/backend
tsk

error TS2688: Cannot find type definition file for 'pino-pretty'.

1 error found.

npm ERR! ELIFECYCLE code
npm ERR! mistake 2
npm ERR! [email protected] build: tsc
npm ERR! exit state 2
npm ERR!
npm ERR! Build script [email protected] failed.
npm ERR! This is probably not a problem with npm. There is probably additional log output above.

npm ERR! A complete log of this run can be found at:
npm ERR! /root/.npm/_logs/2022-11-13T20_46_39_485Z-debug.log

Problema com o scroll no atendimento ainda persiste mesmo após o fix: ajuste no scroll das mensagens

Quando é enviado a mensagem pelo atendimento o scroll funciona, porem quando recebe uma mensagem a tela não faz o scroll automático

Fala pessoal, queria saber se mais alguém já teve este problema no backend e conseguiu resolver.

Estou usando o node v14.21.1
Já rodei rm -rf node_modules, rm -rf package-lock.json, npm cache clean -f e npm install -f
Antes do pull dessa última versão, estava rodando.

Valeu

Quando recebe um novo atendimento ou resposta não atualiza no painel, apenas se atualizar a página.

quando tento realizar o login encontro um erro This request has been blocked; the content must be served over HTTPS.

Olá Duran, já conseguiu identificar porque em momentos não conseguimos fazer o npx sequelize db:migrate, retorna no final o erro

ERROR: column "queue" of relation "Tickets" already exists

Olá, qual o caminho para cadastrar uma segunda empresa, é no admin-front? caso sim, nao estou encontrando.
é possivel adicionar dois canais do mesmo tipo para a mesma empresa? quando tento cadastrar o segundo canal para a empresa -1, da erro. abaixo o log.

error: 2022-11-16T18:04:46.554Z Validation error - SequelizeUniqueConstraintError: Validation error
0|izing-backend | at Query.formatError (/home/deploy/izing.io/backend/node_modules/sequelize/lib/dialects/postgres/query.js:324:18)
0|izing-backend | at /home/deploy/izing.io/backend/node_modules/sequelize/lib/dialects/postgres/query.js:72:18
0|izing-backend | at tryCatcher (/home/deploy/izing.io/backend/node_modules/bluebird/js/release/util.js:16:23)
0|izing-backend | at Promise._settlePromiseFromHandler (/home/deploy/izing.io/backend/node_modules/bluebird/js/release/promise.js:547:31)
0|izing-backend | at Promise._settlePromise (/home/deploy/izing.io/backend/node_modules/bluebird/js/release/promise.js:604:18)
0|izing-backend | at Promise._settlePromise0 (/home/deploy/izing.io/backend/node_modules/bluebird/js/release/promise.js:649:10)
0|izing-backend | at Promise._settlePromises (/home/deploy/izing.io/backend/node_modules/bluebird/js/release/promise.js:725:18)
0|izing-backend | at _drainQueueStep (/home/deploy/izing.io/backend/node_modules/bluebird/js/release/async.js:93:12)
0|izing-backend | at _drainQueue (/home/deploy/izing.io/backend/node_modules/bluebird/js/release/async.js:86:9)
0|izing-backend | at Async._drainQueues (/home/deploy/izing.io/backend/node_modules/bluebird/js/release/async.js:102:5)
0|izing-backend | at Immediate.Async.drainQueues [as _onImmediate] (/home/deploy/izing.io/backend/node_modules/bluebird/js/release/async.js:15:14)
0|izing-backend | at processImmediate (internal/timers.js:464:21)

Obrigado

I can't login after installation

https://atendimento.clubeplus.com.br

Após a instação pelo docker não consigo logar usando o login : [email protected] e senha: 123456
alguém consegui me ajudar?

Quando é feito o login ele já sai do painel falando que a sessão expirou.

Identifiquei que ao tentar deletar uma mensagem agendada ela é interpretada como uma mensagem já enviada. Com isso, nos logs, é apresentado o erro "Cannot found message within 100 last messages" (Mensagem não encontrada nas últimas 100 mensagens) pois no arquivo GetWbotMessage ao procurar a mensagem ela não é encontrada. Talvez uma possível solução seja identificar e tratar mensagens agendadas de uma maneira diferente das mensagens enviadas/recebidas.

ola, estou rodando localmente para testar, usei o tutorial do inicio ali rodei o primeiro comando para criar os container apos fui rodar o segundo e ja deu erro
ai fui ver o container do backend esta restanrd e no log aparece a seguinte mensagem
command not found: sequelize... e fica nesse loop, ja removi todos os container e tentei novamente segue o erro, ate abre no navegador a pagina do izing porem nao faz login.

Bom dia! Sistema não obedece as configurações feitas nas regras de horário.

Boa noite,

Prezados, estou recebendo o seguinte erro ao tentar realizar o:
npm run db:migrate
e o
npm run db:seed

error TS2688: Cannot find type definition file for 'pino-pretty'.

sempre que tento realizar ambos os comandos são retornados os seguintes erros:


qualquer ajuda é bem-vinda!

Hello, thank you for this interesting project.
I have some inconveniences when synchronizing with WhatsApp the QR code is not generated and I see an error in the console. Does anyone know how to fix this.

I am running on Ubuntu 20.04

Olá, obrigado por este interessante projeto.
Eu tenho alguns problemas ao sincronizar com o WhatsApp o código QR não é gerado e vejo um erro no console. Alguém sabe como consertar isto.

Estou correndo no Ubuntu 20.04

Estou recebendo reabertura de chamado quando clicamos em resolver na conversa, e ai reabre novamente. como resolver.

Ao tentar cadastrar uma campanha, ao tentar selecionar uma opção no campo obrigatório Enviar Por, não aparece opções.

Não encontrei opções no sistema para ajustar esta opção.

Quando conecto mais de 1 conexao de whatsapp, mesmo uma sendo default, ela começa a alternar as conexoes qdo se responde um chamado, exempo..
Cadastrei Whatsapp 1 , 2 e 3
eu chamo no Whatsapp 1 , qdo respondo o cliente ele sai pelo whatsapp 2 ou 3 e vai alternando, mesmo estando em tenant diferente.

Boa tarde,

Prezados, estou tentando realizar o login porem nao entra com os dados passados:
https://fronti.ojauum.xyz/#/login

Quando aberto um ticket e ao tentar tickar a Carteira e/ou Etiquetas, ele parece não tickar, porém ao atualizar a página ele aparece tickado.

deploy@izing:~/izing/backend$ npm start

[email protected] start /home/deploy/izing/backend
nodemon --inspect dist/server.js

[nodemon] 2.0.20
[nodemon] to restart at any time, enter rs
[nodemon] watching path(s): .
[nodemon] watching extensions: js,mjs,json
[nodemon] starting node --inspect dist/server.js
Debugger listening on ws://127.0.0.1:9229/ae17bdd8-b332-4b8b-951c-8127e4ab0075
For help, see: https://nodejs.org/en/docs/inspector
info: 2022-11-14T15:48:11.753Z Server started on port: 3000
ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14) {
command: { name: 'select', args: [ '3' ] }
}
ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14) {
command: { name: 'info', args: [] }
}
Error: Error initializing Lua scripts
at /home/deploy/izing/backend/node_modules/bull/lib/queue.js:153:30
at processTicksAndRejections (internal/process/task_queues.js:95:5)
(node:40370) UnhandledPromiseRejectionWarning: ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14)
(Use node --trace-warnings ... to show where the warning was created)
(node:40370) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:40370) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:40370) UnhandledPromiseRejectionWarning: ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14)
(node:40370) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14) {
command: { name: 'select', args: [ '3' ] }
}
ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14) {
command: { name: 'info', args: [] }
}
Error: Error initializing Lua scripts
at /home/deploy/izing/backend/node_modules/bull/lib/queue.js:153:30
at processTicksAndRejections (internal/process/task_queues.js:95:5)
(node:40370) UnhandledPromiseRejectionWarning: ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14)
(node:40370) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)
(node:40370) UnhandledPromiseRejectionWarning: ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14)
(node:40370) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4)
ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14) {
command: { name: 'select', args: [ '3' ] }
}
ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14) {
command: { name: 'info', args: [] }
}
Error: Error initializing Lua scripts
at /home/deploy/izing/backend/node_modules/bull/lib/queue.js:153:30
at processTicksAndRejections (internal/process/task_queues.js:95:5)
(node:40370) UnhandledPromiseRejectionWarning: ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14)
(node:40370) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 5)
(node:40370) UnhandledPromiseRejectionWarning: ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14)
(node:40370) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 6)
ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14) {
command: { name: 'select', args: [ '3' ] }
}
ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14) {
command: { name: 'info', args: [] }
}
Error: Error initializing Lua scripts
at /home/deploy/izing/backend/node_modules/bull/lib/queue.js:153:30
at processTicksAndRejections (internal/process/task_queues.js:95:5)
(node:40370) UnhandledPromiseRejectionWarning: ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14)
(node:40370) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 7)
(node:40370) UnhandledPromiseRejectionWarning: ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14)
(node:40370) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 8)
ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14) {
command: { name: 'select', args: [ '3' ] }
}
ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14) {
command: { name: 'info', args: [] }
}
Error: Error initializing Lua scripts
at /home/deploy/izing/backend/node_modules/bull/lib/queue.js:153:30
at processTicksAndRejections (internal/process/task_queues.js:95:5)
(node:40370) UnhandledPromiseRejectionWarning: ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14)
(node:40370) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 9)
(node:40370) UnhandledPromiseRejectionWarning: ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14)
(node:40370) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 10)
ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14) {
command: { name: 'select', args: [ '3' ] }
}
ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14) {
command: { name: 'info', args: [] }
}
Error: Error initializing Lua scripts
at /home/deploy/izing/backend/node_modules/bull/lib/queue.js:153:30
at processTicksAndRejections (internal/process/task_queues.js:95:5)
(node:40370) UnhandledPromiseRejectionWarning: ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14)
(node:40370) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 11)
(node:40370) UnhandledPromiseRejectionWarning: ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14)
(node:40370) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 12)
ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14) {
command: { name: 'select', args: [ '3' ] }
}
ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14) {
command: { name: 'info', args: [] }
}
Error: Error initializing Lua scripts
at /home/deploy/izing/backend/node_modules/bull/lib/queue.js:153:30
at processTicksAndRejections (internal/process/task_queues.js:95:5)
(node:40370) UnhandledPromiseRejectionWarning: ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14)
(node:40370) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 13)
(node:40370) UnhandledPromiseRejectionWarning: ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14)
(node:40370) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 14)
[ioredis] Unhandled error event: ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14)
[ioredis] Unhandled error event: ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14)
ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14) {
command: { name: 'select', args: [ '3' ] }
}
ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14) {
command: { name: 'info', args: [] }
}
(node:40370) UnhandledPromiseRejectionWarning: ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14)
(node:40370) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 15)
ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14) {
command: { name: 'select', args: [ '3' ] }
}
ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14) {
command: { name: 'info', args: [] }
}
(node:40370) UnhandledPromiseRejectionWarning: ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14)
(node:40370) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 16)
ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14) {
command: { name: 'select', args: [ '3' ] }
}
ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14) {
command: { name: 'info', args: [] }
}
(node:40370) UnhandledPromiseRejectionWarning: ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14)
(node:40370) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 17)
ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14) {
command: { name: 'select', args: [ '3' ] }
}
ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14) {
command: { name: 'info', args: [] }
}
(node:40370) UnhandledPromiseRejectionWarning: ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14)
(node:40370) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 18)
ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14) {
command: { name: 'select', args: [ '3' ] }
}
ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14) {
command: { name: 'info', args: [] }
}
(node:40370) UnhandledPromiseRejectionWarning: ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14)
(node:40370) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 19)
ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14) {
command: { name: 'select', args: [ '3' ] }
}
ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14) {
command: { name: 'info', args: [] }
}
(node:40370) UnhandledPromiseRejectionWarning: ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14)
(node:40370) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 20)
ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14) {
command: { name: 'select', args: [ '3' ] }
}
ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14) {
command: { name: 'info', args: [] }
}
(node:40370) UnhandledPromiseRejectionWarning: ReplyError: NOAUTH Authentication required.
at parseError (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:179:12)
at parseType (/home/deploy/izing/backend/node_modules/redis-parser/lib/parser.js:302:14)
(node:40370) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 21)
(node:40370) UnhandledPromiseRejectionWarning: Error: Socket closed abruptly during opening handshake
at Socket.endWhileOpening (/home/deploy/izing/backend/node_modules/amqplib/lib/connection.js:260:17)
at Socket.emit (events.js:412:35)
at endReadableNT (internal/streams/readable.js:1333:12)
at processTicksAndRejections (internal/process/task_queues.js:82:21)
(node:40370) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 22)
(node:40370) UnhandledPromiseRejectionWarning: Error: Socket closed abruptly during opening handshake
at Socket.endWhileOpening (/home/deploy/izing/backend/node_modules/amqplib/lib/connection.js:260:17)
at Socket.emit (events.js:412:35)
at endReadableNT (internal/streams/readable.js:1333:12)
at processTicksAndRejections (internal/process/task_queues.js:82:21)
(node:40370) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 23)
(node:40370) UnhandledPromiseRejectionWarning: Error: Socket closed abruptly during opening handshake
at Socket.endWhileOpening (/home/deploy/izing/backend/node_modules/amqplib/lib/connection.js:260:17)
at Socket.emit (events.js:412:35)
at endReadableNT (internal/streams/readable.js:1333:12)
at processTicksAndRejections (internal/process/task_queues.js:82:21)
(node:40370) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 24)
(node:40370) UnhandledPromiseRejectionWarning: Error: Socket closed abruptly during opening handshake
at Socket.endWhileOpening (/home/deploy/izing/backend/node_modules/amqplib/lib/connection.js:260:17)
at Socket.emit (events.js:412:35)
at endReadableNT (internal/streams/readable.js:1333:12)
at processTicksAndRejections (internal/process/task_queues.js:82:21)
(node:40370) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 25)
[nodemon] app crashed - waiting for file changes before starting...