Troubleshooting
Why WinCC Unified simulation will not open in a browser
Short answer
Browse to the engineering PC's host name followed by /WebRH, because WinCC Unified simulation runs on that PC and not at the configured device IP. If the page still will not load, confirm the project runs in Runtime Manager, then check the WinCC Unified certificate in IIS. If the page opens and login fails, download again with 'keep user administration data' unchecked.
On this page
WinCC Unified simulation runs on the engineering PC, not on the HMI device you configured, so the browser must address that PC: enter the PC's host name followed by /WebRH, as an https address. The device IP in the HMI configuration is never the simulation endpoint, and administrator access on the project user does not open the page. If the address is right and the page still will not load, two causes remain: the project runtime is not running in Runtime Manager, or the WinCC Unified certificate in IIS is missing. If the page opens and login then fails, download the project again with "keep user administration data" unchecked.
Two failures that get confused #
A browser that never renders a page is an endpoint problem: wrong host, no running runtime, or a certificate blocking the https connection. A browser that renders the login page and then rejects your credentials is a user administration problem. The first-time setup that fails most often shows every green light — project compiled, user configured with administrator access, device IP set — and still no page, because none of those three settings makes the configured device address serve the simulation. Decide which failure you have before changing anything: no page means work the endpoint; page then rejection means work the users.
Why the address is the PC, not the panel #
Simulating a Unified Comfort Panel runs the runtime on the engineering PC and opens it in a standard browser such as Microsoft Edge or Google Chrome. The runtime is served from that PC, so the address is the PC's host name followed by /WebRH, written with the exact capitalization shown, because the documented web client path warns that letter case matters.
The device IP you set in the HMI configuration belongs to the panel's own runtime. On the panel itself, that runtime is reached through the panel's https address ending in /WebRH, built from the HMI device's address. Reading a runtime from a PC other than its host is a different arrangement, covered in running a PLC-hosted visualization on a remote HMI panel PC.
Worked example: building the address #
Take an illustrative setup: the panel is configured at 192.0.2.10 in the HMI settings, and the engineering PC's host name is ENG-PC-01.
Simulation address = https:// + host name of the PC running the simulation + /WebRH = https://ENG-PC-01/WebRH
The habit that fails is https://192.0.2.10/WebRH: that request goes to the panel, and the panel is not running your simulation. On the engineering PC the browser always gets the PC's host name; the configured device address serves the panel runtime only.
The fix, in order #
- Compile the project in TIA Portal and confirm it completes without errors. Resolve compile errors before testing anything else.
- Open Runtime Manager and confirm the project is running. If it is not, start the simulation from TIA Portal and look again.
- In the browser on the engineering PC, enter
https://followed by the PC's actual host name and/WebRH, keeping the capitalization exactly as written. Replace any address built from the device IP. - If the browser reports a certificate problem, open IIS and look for the WinCC Unified certificate. If it is not installed, create the certificate, then reload the same address.
- If the login page opens and rejects the configured user, download the project again with "keep user administration data" unchecked, then log in with that user.
What each check proves #
- Compile without errors: the project content is valid. Decision: no browser test means anything until this passes.
- Runtime Manager shows the project running: an endpoint exists. Decision: while it shows stopped, no address will work.
https://+ host name +/WebRHloads: the browser reaches the engineering PC. Decision: a device-IP address in the address bar is the fault until it is replaced.- WinCC Unified certificate present in IIS: the https connection can complete. Decision: create the missing certificate and retry the same address.
- Login page appears: reachability is proven. Decision: credential failures from this point are user administration data, not network or certificate problems.
Time-wasters on a first simulation #
- Reading a green compile as a running runtime. They are separate states in separate tools.
- Treating administrator access as a connection fix. Rights apply after the page renders.
- Browsing to the device IP because it sits in the HMI configuration. That address serves the panel, not the simulation.
- Unchecking "keep user administration data" when no page ever opened. That option addresses login failures, not reachability.
- Retyping the path with different capitalization. The documented path is
/WebRH; match it exactly instead of guessing variants.
After the page opens #
An open simulation is a test bench, not a deployed HMI. Pointing the simulated screens at a live controller is a separate step, and testing HMI simulation against a live PLC covers the connection path. Writes from a simulated screen reach the real PLC outputs, so test against a controller on isolated or test hardware. When the project moves past simulation, where WinCC Unified Runtime can run covers the host options for the runtime.
Questions asked
Can I open the simulation with localhost or the panel's IP address?
No. Simulation runs on the engineering PC's own web server, so the documented address is that PC's host name followed by /WebRH, entered as an https address. The panel IP from the HMI configuration serves the device runtime, not the simulation, and documented cases show localhost forms failing where the https host name address loaded.
Why does a clean compile not prove the browser will open the runtime?
Compilation validates project content; it neither starts the runtime nor proves the browser can reach it. Runtime Manager separately reports whether the project is running, and a compiled project with a stopped runtime leaves the browser nothing to connect to. Look at Runtime Manager after compiling, before judging the address or the certificate.
Does giving the user administrator access fix a browser that will not open?
No. User rights apply at the login page, after the runtime has answered the browser. When no page appears at all, the failure sits in the address, the runtime state, or the certificate, and changing user access changes nothing. Configure users once the page opens.
What does unchecking 'keep user administration data' do during download?
Left checked, the download preserves the user administration data already on the target, so a missing or misconfigured account survives it. Unchecked, the download delivers the project's user administration data, which is the documented step when the login page opens and then rejects the configured user.
Why do browser errors still mention WinCC Unified after uninstalling it?
Removing a local WinCC Unified installation suppresses the start screen, but browser requests can still return errors referencing WinCC Unified, because the web server entries outlive the uninstall. Check IIS on that PC for the remaining site and certificate entries; the errors clear only when those are removed.