Directly on the device (kiosk screen), the user interface runs on http://localhost:5000. From other computers on the network, you can additionally reach the same interface over an encrypted connection:
https://<edge-ip>:5443Both access paths show the same application with the same users and permissions.
Why HTTPS on a separate port?
Some embedded applications (e.g. the AppStore) require what browsers call a secure context. That is given for http://localhost on the device itself, but for access via a LAN IP it is only available over HTTPS. The edge therefore provides both access paths as of firmware 2.1.1: HTTP on port 5000 (local/kiosk) and HTTPS on port 5443 (remote access).
Certificate warning in the browser
On first startup, the edge generates a self-signed certificate covering all of the device’s IP addresses. Your browser shows a warning on the first visit (“Your connection is not private”) because the certificate is not issued by a public certificate authority. In a closed production network this is expected behavior: confirm the exception (“Advanced” → “Proceed to …”).
Multiple network ports
An openXEdge has up to three LAN ports with their own IP addresses (typically: office network, IO-Link subnet, service port). The interface — including all embedded applications — is reachable via every one of these addresses; simply use the IP of the port your computer is connected to. The port assignment is described in Wiring and connections.
Troubleshooting
- Page does not load → Are you on the right subnet? The IP addresses of all ports are shown on the edge’s display and under Settings → Network.
- Embedded view stays empty (only with HTTP via LAN IP) → Use the HTTPS access path
https://<edge-ip>:5443.