[en] Issue: Conflict Between Multiple Instances of wppconnect-server in Docker Swarm [pt-br] Problema: Conflito Entre Múltiplas Instâncias do wppconnect-server no Docker Swarm #2055
Labels
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
[en] Description
I'm experiencing an issue running multiple instances of the
wppconnect-serverin a Docker Swarm setup. When attempting to launch a new stack (e.g.,homologacao) alongside the production stack, Puppeteer/Chromium fails to initialize properly, causing a direct conflict between instances, which seem to interfere with each other despite being isolated. This behavior occurs only within container environments.The problem was identified while debugging an attachment upload limit (restricted to 60MB). This issue remains unresolved and will be reported separately.
[pt-br] Descrição
Estou enfrentando um problema ao executar múltiplas instâncias do
wppconnect-serverem uma configuração de Docker Swarm. Quando tento subir uma nova stack (por exemplo,homologacao) além da stack de produção, o Puppeteer/Chromium não consegue inicializar corretamente, causando um conflito direto entre as instâncias que, apesar de isoladas, parecem interferir uma com a outra. Esse comportamento é específico para containers e não ocorre fora desse ambiente.O problema foi identificado durante a tentativa de debugar uma limitação no envio de anexos, que está restrito a 60MB. Este problema ainda não foi resolvido, mas será reportado separadamente.
[en] Environment
[pt-br] Ambiente
{ "secretKey": "my_key", "host": "http://localhost", "port": "21465", "deviceName": "WppConnect", "poweredBy": "WPPConnect-Server", "startAllSession": true, "tokenStoreType": "file", "maxListeners": 15, "customUserDataDir": "./userDataDir/", "webhook": { "url": null, "autoDownload": true, "uploadS3": false, "readMessage": false, "allUnreadOnStart": false, "listenAcks": true, "onPresenceChanged": false, "onParticipantsChanged": false, "onReactionMessage": true, "onPollResponse": false, "onRevokedMessage": false, "onLabelUpdated": false, "onSelfMessage": false, "ignore": ["status@broadcast"] }, "websocket": { "autoDownload": false, "uploadS3": false }, "chatwoot": { "sendQrCode": true, "sendStatus": true }, "archive": { "enable": false, "waitTime": 10, "daysToArchive": 45 }, "log": { "level": "silly", "logger": ["console", "file"] }, "createOptions": { "browserArgs": [ "--disable-web-security", "--no-sandbox", "--disable-web-security", "--aggressive-cache-discard", "--disable-cache", "--disable-application-cache", "--disable-offline-load-stale-cache", "--disk-cache-size=0", "--disable-background-networking", "--disable-default-apps", "--disable-extensions", "--disable-sync", "--disable-translate", "--hide-scrollbars", "--metrics-recording-only", "--mute-audio", "--no-first-run", "--safebrowsing-disable-auto-update", "--ignore-certificate-errors", "--ignore-ssl-errors", "--ignore-certificate-errors-spki-list", "--remote-debugging-port=9277", "--remote-debugging-address=0.0.0.0" ], "puppeteerOptions": { "devtools": true, "dumpio": true, "protocolTimeout": 60000 } }, "mapper": { "enable": false, "prefix": "tagone-" }, "db": { "mongodbDatabase": "tokens", "mongodbCollection": "", "mongodbUser": "", "mongodbPassword": "", "mongodbHost": "", "mongoIsRemote": true, "mongoURLRemote": "", "mongodbPort": 27017, "redisHost": "localhost", "redisPort": 6379, "redisPassword": "", "redisDb": 0, "redisPrefix": "docker" }, "aws_s3": { "region": "sa-east-1", "access_key_id": null, "secret_key": null, "defaultBucketName": null, "endpoint": null, "forcePathStyle": null } }[en] Steps to Reproduce
wppconnect-serverin Docker Swarm (e.g., production).ProtocolErrorandNetwork.enable.[pt-br] Passos para Reproduzir
wppconnect-serverem Docker Swarm (por exemplo, para produção).ProtocolErroreNetwork.enable.[en] Log Output
[pt-br] Saída de Log
[en] Additional context / Screenshot
While investigating this issue, I also identified a separate problem: an attachment upload limit of 60MB, which remains unresolved but will be reported in a separate bug report.
[pt-br] Contexto Adicional / Screenshot
Ao investigar o problema, também identifiquei uma limitação de upload de anexos de 60MB que ainda não foi resolvida, mas pretendo abrir um relatório de bug separado para tratar essa questão.
The text was updated successfully, but these errors were encountered: