Docker update to 1.2.5 from 1.2.4 connection refused

codygamer666 commented 2 years ago

Is this a BUG REPORT or FEATURE REQUEST?:

[x] BUG
[ ] FEATURE

What happened: Just updated from 1.2.4 to 1.2.5 and the when connecting to port 8118 it won't work. After rolling back to 1.2.4 in the docker-compose.yml file it works normally.

What did you expect to happen: Normal operation

How to reproduce it (as minimally and precisely as possible): Install 1.2.4, populate and work a bit and then update to 1.2.5

Anything else we need to know?:

Environment:

Trudesk Version: 1.2.5
OS (e.g. from /etc/os-release): Debian, Docker
Node.JS Version:
MongoDB Version: 5.0
Is this hosted on cloud.trudesk.io: NO

rusty1281 commented 2 years ago

Was just about to open up a ticket on this. I have just tried it twice, and it is not working. Rolling back to 1.2.4, reverse to operational status.

codygamer666 commented 2 years ago

Was just about to open up a ticket on this. I have just tried it twice, and it is not working. Rolling back to 1.2.4, reverse to operational status.

Yea, even if you update the composer file with the new changes. I tried to log in into the container and the services are running. But if i list the ports that are currently listening the 8118 is missing, I will now double check the ports of the 1.2.4 container and see if the situation is the same.

rusty1281 commented 2 years ago

Yea, even if you update the composer file with the new changes. I tried to log in to the container and the services are running. But if I list the ports that are currently listening the 8118 is missing, I will now double check the ports of the 1.2.4 container and see if the situation is the same.

Same here. The services are running but the connection to the app on that port is not working, and ofc then forward to reverse proxy as well.

codygamer666 commented 2 years ago

Yea, even if you update the composer file with the new changes. I tried to log in to the container and the services are running. But if I list the ports that are currently listening the 8118 is missing, I will now double check the ports of the 1.2.4 container and see if the situation is the same.

Same here. The services are running but the connection to the app on that port is not working, and ofc then forward to reverse proxy as well.

Ok tried just now with "netstat -tulpn | grep LISTEN" using portainer, in the 1.2.4 the 8118 is present, but in the new version is not. The port is pointing to 19/app.js, i'll try to run again the 1.2.5 and see if it's running

codygamer666 commented 2 years ago

Yea, even if you update the composer file with the new changes. I tried to log in to the container and the services are running. But if I list the ports that are currently listening the 8118 is missing, I will now double check the ports of the 1.2.4 container and see if the situation is the same.

Same here. The services are running but the connection to the app on that port is not working, and ofc then forward to reverse proxy as well.

Ok tried just now with "netstat -tulpn | grep LISTEN" using portainer, in the 1.2.4 the 8118 is present, but in the new version is not. The port is pointing to 19/app.js, i'll try to run again the 1.2.5 and see if it's running

The services are all the same on both versions, only the 8118 is not published inside the container running 1.2.5.

rusty1281 commented 2 years ago

I can confirm the same. Dockerfile for 1.2.5 is still the same as it was 20+ days ago with EXPOSE 8118 port, but it's not listening on the latest version.