Troubleshooting
Fix Vijeo Designer WebGate not working after an update
Short answer
Match the WebGate client version on the operator PC to the Vijeo Designer version that performed the last transfer to the panel, then open the session in Microsoft Edge. If it still fails, classify it by stage: unreachable page, client that will not load, authentication, or application without remote functions.
On this page
WebGate stopped the moment Vijeo Designer was updated because the client on the operator PC no longer matches the software that programmed the panel. The fix: identify the Vijeo Designer version that performed the last transfer to the HMI, install the WebGate client of exactly that release on the PC, and open the session in Microsoft Edge. Concretely: a panel transferred with 6.2 needs the 6.2 control — an installed "Vijeo-WebGate Control 1.4" entry is a mismatch and is the fault itself. If the session still fails, classify it by stage — unreachable page, client that will not load, failed sign-in, application without remote functions — because each stage has one next check, and none of them starts on the panel.
What the update actually changed #
Three pieces of software carry a WebGate session, and the update touched only the first:
- the Vijeo Designer editor on the engineering station — the piece that was updated;
- the WebGate application deployed on the panel as part of the project — unchanged until a new transfer is made;
- the WebGate client, the PC-side control also called the Vijeo Viewer, installed on the operator PC — untouched by an engineering-station update.
WebGate therefore cannot break from an editor update alone. It broke because the project was re-transferred with the new version, or because the client on the PC changed: the documented requirement is that the WebGate be compatible with the version of Vijeo Designer used to program the panel. WebGate runs on targets with an Ethernet port and Compact Flash or hard-disk memory — the XBT GT/GK class, among others.
The same editor-to-target version pairing bites in other ecosystems; Matching Crimson software version to HMI firmware documents the Red Lion case.
Pin down the version that last programmed the panel #
Record four facts before changing any software:
- the Vijeo Designer version of the last transfer to the panel, from the deployment or transfer record;
- the installed WebGate client version on the operator PC, read from the installed-programs entry rather than the installer file name;
- the editor version now on the engineering station, and whether a transfer followed the update;
- the exact browser symptom at first failure.
The editor's current version is not evidence of what programmed the panel; only the transfer record is. If the editor refuses a new transfer with a project version mismatch, that is a different fault, covered in Fix a Vijeo Designer project version mismatch by updating the build.
Install the matching WebGate client #
- Obtain the client release that matches the transfer version, from Schneider Electric or an authorized distributor.
- Close open WebGate sessions and browser windows first, so no previously loaded client components survive the swap.
- Follow the release's documented upgrade or removal path with installer privileges, and complete any restart it requests.
- Read the installed version back from the installed-programs entry and compare it with the transfer record; proceed only when they are identical.
For a panel transferred with 6.3, the client is a separate download; Where to Find the Vijeo Web Gate Client 6.3 Installer covers its location. Do not install releases at random as trial and error: the documented control line runs 6.2, 1.7, 1.6, 1.4, 1.3 and 1.0, and only the number equal to your transfer version is the match.
Microsoft Edge and the ActiveX exception #
Open the session in Microsoft Edge — that is the browser Schneider Electric's WebGate guidance uses. The classic WebGate control is ActiveX, however, and only Internet Explorer hosts ActiveX natively; Chrome, Firefox and a plain Chromium tab in Edge will not load it. In practice that means Edge with Internet Explorer mode enabled for the panel's address. Do not weaken browser security globally to force a load; set the one prerequisite the release documents.
This separates two faults that look identical. A page that opens with a client area that never loads is a browser-capability failure on the old control; the same symptom immediately after a version change points back at the client version.
Classify the failure by stage #
Capture the exact message at the first failure, then place it:
| Observed at first failure | Where the fault is | Next check |
|---|---|---|
| Destination not reachable | Addressing and network path | HMI address, route, and access to the WebGate service |
| Page opens, client never loads | PC client or browser capability | Installed control version, then the Edge Internet Explorer mode prerequisite |
| Client loads, sign-in fails | Accounts | Authorized WebGate user and permissions in the deployed project |
| Application opens, remote functions unusable | Project configuration | WebGate enablement and permissions in the deployed project |
A response to a basic network test proves only part of the path; the application session must also succeed. A corrected setting in the editor has no effect until that project is deployed, and a project correction belongs in a planned window with a backup.
Worked example: a panel transferred with 6.2 and a 1.4 client #
Inputs: the customer's transfer record shows the last download to the panel was made with Vijeo Designer 6.2 after the update; the operator PC's installed-programs entry reads Vijeo-WebGate Control 1.4; the documented control releases are 6.2, 1.7, 1.6, 1.4, 1.3 and 1.0 — six in total; the browser is Edge, the page opens, and the client area never loads.
Rule: the control installed on the PC must carry the same version number as the Vijeo Designer release that performed the last transfer, with both components equal.
Arithmetic:
- major component: 1 ≠ 6;
- minor component: 4 ≠ 2 — one differing component would already be a mismatch, and this pair differs in both;
- exact matches among the six listed releases: 1, the 6.2 control, so 6 − 1 = 5 releases do not match;
- brute-force swapping through the list means up to 6 installs; the version-matched path is 1.
Result: install Vijeo-WebGate Control 6.2 on the operator PC and read the version back. The panel takes no new transfer for this fault.
Decision: when the installed control differs from the transfer version in either component, replace the control before touching the browser or the panel. When the two numbers are identical and the client still will not load in a plain Edge tab, the fault has moved to the browser stage — enable Internet Explorer mode for that address rather than reinstalling.
Verify the fix end to end #
- Open a fresh Edge session to the recorded address — the recorded one, not a re-typed guess — and sign in with an authorized account.
- Choose one live value or status visible on the local panel and confirm the remote view follows a real change; a rendered screen alone does not prove the session is communicating.
- Test one approved, non-hazardous control action and confirm the local panel reflects it.
Treat the remote session as live machine access: keep an authorized person at the panel with the machine in a safe state for the first control test.
Questions asked
Which WebGate client runs on Windows 11?
Schneider Electric documents the Vijeo Viewer — the WebGate client — working with Vijeo Designer 6.2 and 6.3 on current Windows. The 1.x controls predate that generation, so a Windows 11 operator PC belongs on the 6.2 or 6.3 client that matches the transfer version of your panel.
Does the client version have to match the HMI firmware?
No. The match is against the Vijeo Designer release that performed the last project transfer, not the panel's firmware number and not the editor version currently installed. Two panels with identical firmware can still need different clients if their projects were transferred with different releases.
Where do the WebGate client files come from?
The Web Gate Client Files Installation wizard can install the client files from the Vijeo Designer installation itself, and the control is also distributed by Schneider Electric as a separate download matched to each release. Either source works; the version number left behind is what must match.
Can a browser extension make Chrome or Firefox load the old client?
No. The classic control is ActiveX, which only Internet Explorer hosts natively, and no add-on changes that in Chromium browsers. The supported routes are Edge with Internet Explorer mode enabled for the panel's address, or the client generation your Vijeo Designer release documents.