0

I'm trying to deploy Mesibo On-Premise with Google Cloud.

Mesibo Console shows following status: "running but not accessible - refer to Firewall settings in the on-premise doc":

Picture 1

Logs by running Mesibo container: Picture 2

Firewall settings for Mesibo on the Google Cloud have highest priority and allow all external IPs through all ports to connect to all instances: Picture 3

The connection between SQL database and Mesibo On-Premise server was verified. Strict mode is disabled.

The problem was in the missing command --net=host by applying docker $ sudo docker run -d mesibo/mesibo <APP_TOKEN>

user14934010
  • 1
  • 1

1 Answers1

0

Is your IP address changed? I could not ping the IP address in the screenshot nor netcat. It is recommended to use a fixed IP address with mesibo. Once mesibo running on your server, click on the check status and the IP address will be refreshed. use netcat or similar tools to see if it is accessible from the public network

mesibo
  • 3,970
  • 6
  • 25
  • 43
  • The IP address was static. I did some experiments in between. That's why it was changed. The new static IP is 34.89.145.208. It can be accessed via netcat from outside only through port 22 (ssh). netstat --listen confirms this information. I still have the same issue and statement in mesibo console: "running but not accessible...". – user14934010 Jan 04 '21 at 09:59
  • You have answered your question. As you have said server is only accessible through port 22. That means your firewall is not open. – mesibo Jan 04 '21 at 12:39
  • As I mentioned in the main topic all ports for all IPs are open with applied firewall rules. The question is why mesibo instance is not listening on dedicated ports mentioned in mesibo documentation 5222 and 5228? – user14934010 Jan 04 '21 at 15:08
  • 1
    I missed the --net=host parameter by sudo doker run... Now it works. Thanks! – user14934010 Jan 04 '21 at 23:47