A complete web-based remote monitoring and management web site. Once setup you can install agents and perform remote desktop session to devices on the local network or over the Internet.
Describe the bug
WebRelay connections are intermittently failing. Error messages such as “Bad AESGCM cookie due to exception: Error: Unsupported state or unable to authenticate data” appear in the application logs. These issues started after implementing peering.
To Reproduce
Steps to reproduce the behavior:
Go to the MeshCentral Dashboard.
Attempt to establish a remote session using WebRelay.
Wait for a connection.
Observe error messages in the logs and the failure to establish a consistent session.
Expected behavior
The WebRelay feature should provide a stable connection to remote agents without intermittent failures or errors related to cookie authentication.
Screenshots
Server Software (please complete the following information):
OS: Ubuntu 24.04 LTS
Virtualization: Docker
Network: Load balancer in GCP, agent and web ports in separate backends
Version: 1.1.33
Node: v20.15.1
Client Device (please complete the following information):
Device: Laptop
OS: Windows 11 Pro
Network: Remote over WAN
Browser: Google Chrome
Remote Device (please complete the following information):
Device: Mini Pc
OS: MX Linux 21
Network: Remote over WAN
Current Core Version : Nov 21 2022, 3188018466
Additional context
The infrastructure includes three MeshCentral servers connected by peer connections. Each server is deployed with Docker Compose on separate instances, with MongoDB configured in a replica set.
networks:
meshcentral-tier:
driver: bridge
services:
mongodb:
restart: always
container_name: mongodb
image: mongo:8.0
hostname: meshcentral01.mongodb.exemple.local
privileged: true
command: ["--replSet", "rs0", "--bind_ip_all", "--port", "27017", "--maxConns", "50000"]
ports:
- 27017:27017
environment:
- GLIBC_TUNABLES=glibc.pthread.rseq=0
volumes:
# mongodb data-directory - A must for data persistence
- ./meshcentral-mongodb-data:/data/db
- ./meshcentral-mongodb-config:/data/configdb
- ./meshcentral-mongodb-dump:/data/dump
networks:
- meshcentral-tier
meshcentral01:
restart: always
container_name: meshcentral01
# use the official meshcentral container
image: ghcr.io/ylianst/meshcentral:1.1.33
depends_on:
- mongodb
ports:
# MeshCentral will moan and try everything not to use port 80, but you can also use it if you so desire, just change the config.json according to your needs
- 80:80
- 8080:8080
env_file:
- .env
environment:
- CONFIG_FILE=../meshcentral-config/meshcentral.config.json
volumes:
- ./config:/opt/meshcentral/meshcentral-config
# config.json and other important files live here. A must for data persistence
- ./meshcentral/meshcentral-data:/opt/meshcentral/meshcentral-data
# where file uploads for users live
- ./meshcentral/meshcentral-files:/opt/meshcentral/meshcentral-files
# location for the meshcentral-backups - this should be mounted to an external storage
- ./meshcentral/meshcentral-backups:/opt/meshcentral/meshcentral-backups
# location for site customization files
- ./meshcentral/meshcentral-web:/opt/meshcentral/meshcentral-web
networks:
- meshcentral-tier
Describe the bug WebRelay connections are intermittently failing. Error messages such as “Bad AESGCM cookie due to exception: Error: Unsupported state or unable to authenticate data” appear in the application logs. These issues started after implementing peering.
To Reproduce Steps to reproduce the behavior:
Expected behavior The WebRelay feature should provide a stable connection to remote agents without intermittent failures or errors related to cookie authentication.
Screenshots
Server Software (please complete the following information):
Client Device (please complete the following information):
Remote Device (please complete the following information):
Additional context The infrastructure includes three MeshCentral servers connected by peer connections. Each server is deployed with Docker Compose on separate instances, with MongoDB configured in a replica set.
config.json file
docker-compose.yml file
Some Line logs