Matt-mrea

I can setup un-secure access using an IP address with no problem using the static IP of my server and access the runtime also as a test but definitely not going to do this for a production environment. 

I have contacted siemens about this and they just kept referring me to articles about swac-login etc did not provide much help and then gave me the option for paid support. 

I have tried renaming my CN on the cert to the same as the Siemens certs but this did not work. At this stage, there is no way to use secure SSL and DNS to access the runtime part of the web server over the internet. If someone was experienced enough on the web development side I'm sure they could find a workaround or remove the swac-login requirements in the webserver scripts ( there is a lot of scripts by siemens in the webserver folders ) 

Other platforms are easy to set up secure access to the webserver HMI/SCADA, I have done this with Rapid SCADA, Indusoft, and Ignition perspective no problem, but really struggling with WinCC Unified. 

UPDATE: I now have this working across the internet using SSL from let's encrypt and DNS from my domain. With update 3 it is now possible under the configuration where you enter the identity provider IP Address you can now also enter DNS. You can now put in the DNS and all redirects to UMC work correctly and no longer get Swaclogin errors. 

 Hi Matt,

Did you tried with update 4? Or you just stick with Update 3 since it worked for you? 

1.- In the self-signed certificate add the public IP. 

2.- When adding the device in WinCC Unified Certificate Manager, also add the public IP 

 I also have the same error. who can help me?

AutoGen_7658332

 

Matt-mrea

I can setup un-secure access using an IP address with no problem using the static IP of my server and access the runtime also as a test but definitely not going to do this for a production environment. 

I have contacted siemens about this and they just kept referring me to articles about swac-login etc did not provide much help and then gave me the option for paid support. 

I have tried renaming my CN on the cert to the same as the Siemens certs but this did not work. At this stage, there is no way to use secure SSL and DNS to access the runtime part of the web server over the internet. If someone was experienced enough on the web development side I'm sure they could find a workaround or remove the swac-login requirements in the webserver scripts ( there is a lot of scripts by siemens in the webserver folders ) 

Other platforms are easy to set up secure access to the webserver HMI/SCADA, I have done this with Rapid SCADA, Indusoft, and Ignition perspective no problem, but really struggling with WinCC Unified. 

UPDATE: I now have this working across the internet using SSL from let's encrypt and DNS from my domain. With update 3 it is now possible under the configuration where you enter the identity provider IP Address you can now also enter DNS. You can now put in the DNS and all redirects to UMC work correctly and no longer get Swaclogin errors. 

 So you can use Dynamic DNS adress by just enter domain name in identity provider IP Address at server configurator and it works?

I have it works with V17. 

1. Open and forward necessary ports in router. 8443, 443 etc

2. Give Unified station a static or DHCP IP in your local network. also add an extra IP address to the same network adaptor, which is same as your public IP address. 

3. Stop running project,  create the certificate with computer name and the public address. 

4. Run WinCC Unified Configuration, in step 2, user management, in "Use IP address for identity provider and website", chose your public address. then apply. 

5. Start project. 

You may see "generic error" the first time log in. if it happens,  chose the right language and try again. 

Good luck. 

I am using eWon m2web access which is similar to DNS 

By the way it’s working very fine if connected through VPN , So only the issue while connecting through internet through publishing the server IP whether if Static IP or DNS 

Can you write a little bit more description of what you have done ?

I am facing the same issue , but runtime isn’t opening and gives messages that can’t connect to server

I am using eWon m2web access which is similar to DNS

By the way it’s working very fine if connected through VPN , So only the issue while connecting through internet through publishing the server IP whether if Static IP or DNS

ZhizhuangQiangGDS

I have it works with V17. 

1. Open and forward necessary ports in router. 8443, 443 etc

2. Give Unified station a static or DHCP IP in your local network. also add an extra IP address to the same network adaptor, which is same as your public IP address. 

3. Stop running project,  create the certificate with computer name and the public address. 

4. Run WinCC Unified Configuration, in step 2, user management, in "Use IP address for identity provider and website", chose your public address. then apply. 

5. Start project. 

You may see "generic error" the first time log in. if it happens,  chose the right language and try again. 

Good luck. 

 

Mi ricordo che tempo fà anchio feci queste operazioni e funzionava tranquillamente.

solo che a distanza di tempo non trovo più questa funzione di aggiungere ip statico quando vai a creare il certificato. Alla versione 16 siemens mi disse che non era possibile farlo funzionare da un IP esterno alla rete e inseribile nella versione 17. Comunque all'epoca funzionava anche sulla versione 16, ma sempre inserendo come nell'esempio in foto.

Hello ZIOLUCIO,

thank you for sharing your experiences! 

For the next time, please try to discuss in English language. This is an international community, and we try to focus on one language.

This is the translation of your post:

ZIOLUCIO

I remember that some time ago I also did these operations and it worked smoothly.

only that after some time I no longer find this function of adding static IP when you go to create the certificate. On version 16 Siemens told me that it was not possible to make it work from an IP external to the network and insertable in version 17. However, at the time it also worked on version 16, but always inserting as in the example in the photo.

 Regards,
Jen_Moderator