Description
This has been giving me issues the entire time and I can’t figure this out for whatever reason. I sucessfully deployed the docker compose file. Properly setup the .env but whenever the Node.js TCP transporter starts up it listens to a new port and it’s always magically in use. I’ve tried checking with netstat and lsof and this port does not show up at all. I can’t trace whatever could possibly be listening to this port and with the port changing every single time there’s no way in my opinion that the port could be already bound to something else. I don’t even have any port ranges that occupy the space it’s trying to take. Trying to figure out if it’s something I messed up on my end or if it’s a configuration issue.
Server Setup Information
- Version of Rocket.Chat Server: 7.5.1
- Operating System: Ubuntu 22.04.5 LTS
- Deployment Method: Docker
- Number of Running Instances: 1
- DB Replicaset Oplog:
- NodeJS Version: 20.17.0
- MongoDB Version: 6
- Proxy: Traefik
- Firewalls involved: None
Any additional Information
No extra variables added, base configuration combined with Traefik.