
To disable peer-to-peer connections in the Client:.You can fix it either on the client’s or on the server’s side. If everything else is OK, but the connection process takes longer than 15 seconds, it most likely means that the client consistently fails to establish a peer-to-peer connection. 6.4 If the connection establishment takes too long If not changed manually, client and agent apps should use port 443 to connect with the gateway server and ports 9021, 19996, 19997, 19998 while establishing the connection. Please ensure that all of the required ports are open on all of the machines involved in the process. If everything – including nginx – seems to be fine according to the logs, but neither Agent nor Client apps can connect to the Gateway, there still may some connectivity problem. You can also find the Supervisor log here if needed: /var/log/supervisor/supervisord.log 6.3 If apps won’t connect to the Gateway Back or Front: first, check the Stdout log.Depending on the faulty module, check the following: If the status of any module differs from Running, check the related logs. If the file is empty, it may mean that nginx is set up incorrectly. Please check the nginx logs that are located at /var/log/nginx/error.log on the target machine. If you can access the server but still cannot access the maintenance page, something is wrong with nginx. 6.1 If the maintenance page won’t openįirst, please check that the machine running the Remotix Gateway server is accessible (e.g., by pinging it).

#Remotix on iphone 7 issue manual
If you choose manual installation, we assume that you may be using the same nginx and database servers for many deeds and will manage them as you need. Please note that Nginx and DB rows appear only for vapp and docker installation types. When everything is fine, each module will have status “ Running”. To ensure that every part of your Remotix Gateway Server runs fine (or to find out what might have gone wrong if anything), go to the maintenance page located at RXGW_BASE_URL/maint.
