• W
    Wingnut2.0

    Thanks Guys.

    Just thinking about options...
    In order to get all client events, is there any way to use a local datasource to connect to /rest/v1/websocket/events on the client and write the updates to an alphanumeric point?

    posted in User help read more
  • W
    Wingnut2.0

    Thank you, Matt. Works perfectly.

    Just curious if you are monitoring other Mango Internal points on the remote clients and if you have created any type of central dashboard to view the 'health' of these clients? Ex. Disk Space, Event Count, user sessions, etc.

    Have you figured out a way to have events that originate at the client level propagate to the server using PTCP?

    posted in User help read more
  • W
    Wingnut2.0

    Thanks Jared. Looking forward to this.

    posted in User help read more
  • W
    Wingnut2.0

    Looking for suggestions as far as the best way to accomplish the following -

    The goal is to monitor the status of cloud connect clients via the cloud connect server and alert/generate an event if a client becomes unresponsive.

    Is it possible to leverage the mangoWatchdog service?

    • Would/Can this be done by creating points on the clients and publish to the server?
    • Could the server somehow broadcast to all clients periodically and the points reside on the server?

    Thank you.

    posted in User help read more
  • W
    Wingnut2.0

    Thank you, Jared. This has been resolved.

    The issue was wrong port numbers on the Cloud connect -> Client settings.
    For the MangoES the ports need to be changed to match the defaults or whatever you may have changed them to.

    • Web forward port
    • SSH forward port

    posted in User help read more
  • W
    Wingnut2.0

    After resolving some DNS issues, I am now able to connect back to 3 of the 4 clients. When attempting to connect to the 4th I receive a 502 Bad Gateway error. The only difference between the clients is that the 4th is a MangoES.

    Are there any ES specific settings required?

    Thank you.

    posted in User help read more
  • W
    Wingnut2.0

    Now I am getting the 401 when accessing via subdomain.domain.

    posted in User help read more
  • W
    Wingnut2.0

    Thank you, Jared.

    When I add this with appropriate domain to the env.properties file of either the client or server and restart mango, I am no longer able to login to the mango instance as I normally would via HTTP://IPaddress:8080.

    posted in User help read more
  • W
    Wingnut2.0

    Hello,

    I currently have 4 clients connected to server and showing in the connected client page (/ui/administration/cloud-connect-clients). Launching the web interface from this page points to http://GUID.subdomain.domain:8080, where I receive a Proxy error 401 Not authenticated.

    Proxy enabled on the server and configured with these options checked: Require authentication, Inject authentication token, and Sync user from server to client.

    When disabling Require authentication I receive a Proxy error 403 Not authenticated when launching.

    Should Fixed Authentication Token be used? Are changes to the env.properties file required? Thank you

    posted in User help read more
  • W
    Wingnut2.0

    Hey Phillip,

    If you inadvertently have both the client and server set to start with Mango and cause Mango to restart neither the client or server will have public keys available. You will also see CloudConnectServer errors in the logs for bind exception.

    posted in User help read more