Open the dashboard remotely

Open https://connect.iqunet.com and use the server ID supplied with your gateway. The documented connection flow adds the server to your account, then opens its dashboard. Existing users may need to grant access before a new user can connect.

The gateway needs an outgoing network connection. The published guide distinguishes signaling failures from firewall restrictions on WebRTC traffic. A local dashboard connection working does not prove that the remote connection is permitted.

The documented remote-access route begins with an outgoing signaling connection and then establishes WebRTC data traffic. It does not require an inbound port-forwarding rule. When reporting a failure, distinguish whether signaling cannot be reached or whether the network blocks the later WebRTC connection.

The original diagnostic guide links the WebRTC Trickle ICE sample. Open that test in the affected browser and select Gather candidates. The guide expects at least one connection candidate. This checks candidate gathering; it does not by itself prove that the browser can reach a particular iQunet gateway.

For the installation described by that older guide, the signaling host is peer.iqunet.lu on ports 80 and 443. Give the applicable service endpoint and the observed failure to your network administrator. Confirm the endpoints for your installed service before using an older article as a firewall configuration reference.

The WebRTC connection described here opens the dashboard. Direct OPC UA and GraphQL clients use their own connection endpoints.