Hello,

I am testing out WinCC Unified in TIA V16 and I ran into an issue where now I can't connect to the https://localhost in the web browser. Is there a setting that I'm missing?

Regards,

masmith1553

Hi,

If IIS was right setting, the localhost should show something. It doesn't seems to be a WinCC problem but else a Windows setup questions.

Is the IIS rightly active (see https://support.industry.siemens.com/cs/ww/en/view/109773589 )? 

Which browser do you use (see https://support.industry.siemens.com/cs/ww/en/view/109757952)?

Did you have any "strange message" by installing WinCC unified?
Did you run the WinCC unified configuration? Did you have any "strange message" by there? 

Did you tried to type the computer name as address?

masmith1553

Thanks for the help, I was able to figure it out. The cert was using the machine name I had the default VM machine name in the cert. Once I redid the configuration I am able to connect.

 Hi!
Can you please give a short description of where and how you reconfigured the certificate, which certificate?

I dont get any answer from the localhost :(

Thank you!

masmith1553

Hello,

I am testing out WinCC Unified in TIA V16 and I ran into an issue where now I can't connect to the https://localhost in the web browser. Is there a setting that I'm missing?

Regards,

masmith1553

 can you show me some screen shot about fix this problem

I am using TIA V19 and WinCC unified, facing issue of WebRH page is not reachable with

https://localhost/WebRH

However I can connect with https://ipaddress/WebRH , but facing issue of 

Swaclogin is unavailable error.

SOLVED:

Both issues are resolved by switch off/disable the proxy server. ( In Windows 11 OS -> Network & Internet > Manual proxy setup > Under Edit proxy server switch off proxy server.)

Refer attachment for error details and proxy server settings.

Tell me where to look for the error

AutoGen_7501607

The project was created on another PC, transferred to the new PC 

If the project was configured for another PC and then moved to a machine with a different name, then you will need to run Unified Configuration on the new machine with the proper settings.

By proper settings I mean the correct PC-Name, since you are using it as identity provider.