F.A.Q

  1. Home
  2. F.A.Q

InsMsg PC Client

Port Bindings

  • TCP 5065: Remote Control/Assistant
  • TCP/UDP 5066: P2P file transfer. InsMsg will try next port when it was used by another program or instance.
  • TCP/UDP 5075: Video/Audio chat. InsMsg will try next port when it was used by another program or instance.

    • Connection fails when client try to login

    There may be many reasons for the failure of the connection. Please follow the steps below

  • Confirm the login address/port is correct, you can change it in client program Settings->Network tab.
    The value can be found in InsMsgServer Network tab
  • Make sure the client and the server network are connected. Generally can be confirmed by telnet.exe command. If the client and the server are connected through a router, you should open these port in firewall.
  • Check the InsMsgServer running status and logs, make sure the database is connected

    • Why the file transfer is slow?

  • Online file transfer, the client will try Peer-to-Peer transmission first. After the failure, the transfer will be relayed by server. So it will be little slow
  • Offline file transfer, the client only communicate with the InsMsgServer, The speed depends on the network condition between the client and server
  • Client will take UDP/TCP 8600 port for Peer-to-Peer transfer. So open these port in firewall will speed up the transfer
  • If you run multiple client programs at the same time, the port number occupied by P2P will be extended

    • Why the video/audio chat is slow？

    Video/Audio chat will use TCP/UDP 8900 port, make sure no firewall blocking these port

    InsMsgServer does not relay these package

    InsMsg Server

    Port Bindings

    You can change the port number before starting the server. The default value is list below:

  • TCP/UDP 5055, TCP 5056-5057: PC client
  • TCP 5058: Mobile client
  • TCP 5085: InsMsgAdmin
  • TCP 5086: Http open API

    • Failed to start

  • Usually, you can find the reason through the server's 'run log'
  • Mostly, the reason are：Failed to connect Database, Failed to bind(listening) to port, Another InsMsgServer is running

    • Client cannot login

  • Make sure the login account is valid. The account can be found in InsMsgAdmin user list
  • Make sure the database is running and InsMsgServer can access to it.
  • If InsMsgServer is running inside a Local Network, Internet user need to access it, Port Forwarding must be set on your router

    • InsMsgServer not starting after system reboot

  • Make sure you have install InsMsgServer as system service, this can be done by click Install button in Running tab
  • Make sure Database is also running as Windows service

    • How to check out the early running log？

  • The server's running log is been kept in [DataRoot]\log\*
  • [DataRoot] is set by in Data tab. InsMsgServer will create it before actually running.

    • Client upgrade file not found

  • InsMsgServer has two build-in client upgrade files along with setup file.
  • The files are stored in client\ directory under installation directory.

    • Android / iOS Client

    Login failed?

  • The login port is different from PC client login port
  • The default port is 5058
  • Make sure InsMsg client has right to access netwrok