Troubleshooting
Why WebIQ Deployment to ctrlX CORE Rejects Your Login
Short answer
An invalid username or password reply while connecting WebIQ Designer to a ctrlX CORE means the WebIQ server app checks logins against its own user database, so no controller account or permission can fix it. Reach the management WebSocket on port 10123, sign in with the WebIQ application account from the vendor's documented initial procedure, then transfer and start the project.
On this page
- What the invalid-credentials reply proves
- Stage 1: confirm the WebIQ server app is running
- Stage 2: bypass discovery with the direct address
- Worked example: connecting to a ctrlX CORE at 192.168.1.1 when discovery hangs
- Stage 3: sign in with a WebIQ application account
- Stage 4: transfer and start the project
- Stage 5: when the layout loads but values stay dead
- Symptom-to-cause table
- Questions asked
When WebIQ Designer reaches the ctrlX CORE and the server answers Given username / or passoword are invalid, the login was checked against the WebIQ server app's own user database, not against ctrlX CORE user management. The controller account with every permission switched on cannot pass that check, and no firewall change can either, because the reply proves the server already received and processed the attempt. Work the deployment as five stages, each with one acceptance check: server app running, direct connection to the management endpoint, WebIQ application login, project transfer, and the deployed runtime's OPC UA connection.
What the invalid-credentials reply proves #
A login attempt that comes back with a credential error has already made the network trip: the request reached the WebIQ server on the controller and was evaluated there. From that moment, two fixes are wrong no matter how often they are repeated:
- Opening more ports or switching off the PC firewall cannot change an answer the server has already given.
- Giving the ctrlX CORE user every permission cannot change it either, because that user is not in the database being queried.
The WebIQ server app keeps its own authentication, separate from the controller's user management. That separation is documented app behavior, not a fault in your installation, so treat it as a boundary: everything before the login prompt is network and server state, everything after it is application accounts.
Stage 1: confirm the WebIQ server app is running #
Installing an app places its software on the controller; it does not by itself prove the server process is accepting connections. In the controller's app management, verify three facts separately:
- The WebIQ server app is installed. A working OPC UA app or any other app on the same controller proves nothing about this one.
- Its operating state reports running. The controller's app management shows each app's state and diagnostics, and a stopped server will not answer on any port.
- The installed server version and the Designer version are a compatible pair per the vendor's compatibility information. Resolve a mismatch before transferring, not after a failure.
Installation, server operation, and later project startup are three separate states; check each one.
Stage 2: bypass discovery with the direct address #
Remote Manager's automatic search uses UPnP, and operating-system configuration or network filtering can block that while the controller stays fully reachable. An endless search is a discovery result, not a connection result. The field at the bottom left of Remote Manager takes the WebSocket address directly: scheme, controller address, colon, management port, with no spaces around any of them. Connecting on that address removes UPnP from the test; what remains is server state and TCP access to the port.
Worked example: connecting to a ctrlX CORE at 192.168.1.1 when discovery hangs #
Inputs:
- Controller address: 192.168.1.1, the target controller's address in this installation; substitute yours.
- Management port: 10123, the port the WebIQ server app listens on, the same port the vendor's connection examples and the Designer command line use.
- Tool: Remote Manager in WebIQ Designer, address field at the bottom left.
Rule: the direct WebSocket address is the scheme, the controller address, a colon, and the port, joined with no spaces.
Assembly:
ws:// + 192.168.1.1 + : + 10123 = ws://192.168.1.1:10123
The same server can also be reached by handing Designer the host and port at launch:
"C:\Program Files (x86)\WebIQ\Designer\webiq-designer.exe" --ws-host=192.168.1.1 --ws-port=10123
Result and decision: after you connect, one of two things happens. A login prompt appears, which means discovery was the only fault and the network is cleared; go straight to the application account. No prompt appears, which means the fault is server state or TCP filtering on 10123; recheck Stage 1, then test TCP access to that single port from the engineering PC and allow that one destination rather than disabling the firewall.
Stage 3: sign in with a WebIQ application account #
The account that authenticates here lives in the WebIQ server app's own user database. For the first login on a new installation, use the initial application account exactly as the vendor's documentation defines it for your installed version; if those credentials are lost later, use the vendor's documented reset or recovery path, or official support. After the first successful login, change that password and create the users you actually want, inside the WebIQ environment.
The acceptance check is the Project Manager opening with the remote project area visible. That is the moment application access is proven; anything failing after it is a project or runtime matter, not a login matter.
Keep the management credentials out of project notes, screenshots, and shared example files, and keep them separate from the OPC UA credentials the project itself uses. If engineers reach the HMI engineering PC over remote desktop, disabling cached Windows credentials stops that login from persisting on a shared machine.
Stage 4: transfer and start the project #
The Project Manager lists local projects on one side and the controller's projects on the other; on a fresh installation the remote side is empty, which is normal. Transfer with the arrows between the two lists, then start the project so the controller's runtime serves it. Once the project is on the controller, starting a published WebIQ HMI project without Runtime Manager follows its own startup path.
Stage 5: when the layout loads but values stay dead #
A successful local preview proves the PC-side HMI and its OPC UA client, not the deployed runtime's connection. The project running on the controller evaluates its OPC UA settings from the controller, so verify that the endpoint address and security settings are valid from there, then check variable quality in the running HMI. The variable side of that chain, showing PLC variables in WebIQ over OPC UA on a ctrlX CORE, is its own procedure.
Symptom-to-cause table #
| What you see | Stage that failed | Next action |
|---|---|---|
| Remote Manager searches endlessly | Discovery, UPnP blocked or filtered | Enter the direct WebSocket address in the bottom-left field |
| Direct address never reaches a login prompt | Server state, wrong address, or TCP filtering | Check the app's operating state, then test TCP to port 10123 |
Given username / or passoword are invalid |
WebIQ application authentication | Use the vendor-documented WebIQ application account |
| Login works, remote project list is empty | None, fresh installation | Transfer a project with the arrows, then start it |
| HMI loads on the controller, values do not update | Deployed runtime's OPC UA connection | Verify the endpoint from the controller, check variable quality |
Read the table top to bottom and stop at the first row that matches: every row above it is proven working, and only that row's action is next.
Questions asked
Why does my ctrlX CORE administrator account fail at the WebIQ login?
No controller role can help, because WebIQ authentication and ctrlX CORE user management are separate systems; sharing accounts between them is not part of the documented behavior of this app. The reply actually confirms the server received and processed the attempt, so treat it purely as an account problem and sign in with the WebIQ application account from the vendor's initial procedure.
Remote Manager searches forever and never finds the controller. What is wrong?
Discovery uses UPnP, which operating-system settings or network filtering can block while the controller is reachable, so type the WebSocket address into the bottom-left field instead: ws://, the controller address, and port 10123, with no spaces. Both this method and the command-line launch reach the same server, so switching between them never fixes an authentication error.
Is the WebIQ management connection TCP or UDP?
The management connection is a TCP WebSocket to port 10123; UPnP discovery is the UDP part, and enabled UDP does not prove the TCP connection can pass. If the direct address still fails before any login prompt, test TCP access to 10123 from the engineering PC. A successful ping proves only that the controller is reachable, not that the service answers.
The transferred HMI loads on the controller but shows no values. Why?
The browser drawing your layout already proves transfer, web serving, and the project running; only the data path is left. The local preview exercised the OPC UA client on the engineering PC, while the deployed runtime evaluates the project's OPC UA settings from the controller, so check the endpoint address and security from the controller side, then check variable quality.
Where do I change the WebIQ password after the first successful login?
Once Remote Manager authenticates and the Project Manager opens, users and passwords are managed inside the WebIQ environment. Change the initial password as the first action after login, create the accounts you actually want, and keep those credentials separate from the ctrlX CORE account and from the OPC UA credentials the project uses.