cannot publish to core

[RobotART_Walter]

Hello,

I want to publish my project to a real ctrl x core.  I have a valid license on the ctrl x core. 
However, I am not able to publish succesfully.
I have tried both via VPN and a local connection. Firewall is turned off.
The ctrl x is not automaticially found and when entering the ip and port manually and try to login (default username and password, admin and boschrexroth) I see the following message:

I

I have tried reinstalling the app multiple times, as per this suggestion Solved: Connect To Remote WebIQ Server Environnment Connec... (boschrexroth.com)

Is there anything I am doing wrong? 

[webiq-sk · Accepted solution]

What happens when you enter http://192.168.2.10:10123/ in a browser on the same system WebIQ Designer is running? If it also does not show the WebIQ Runtime Manager then this should be fixed first as it means there's no WebIQ running on 192.168.2.10 or it's not running on port 10123 if you have changed the port manually (which is discouraged) or there is a firewall blocking the access.

When using WebIQ 2.14 on ctrlX the automatic discovery has been disabled because of a lackup issue after some time.

[RobotART_Walter]

This way I could actually reach it ( via http not https though). From there I could create a new user and password. And with this user I can actually load the project from the web iq designer.\

Thank you!

[webiq-sk]

Just some clarification:

To be able to connect via wss://192.168.2.10:10123 ("Connect via a TLS-encrypted websocket connection to IP 192.168.2.10 on port 10123") you'd have to do this:
- enable TLS on the default listener on port 10123
- setup and configure TLS certificates

If you'd do this this would happen:
- you could no longer connect to WebIQ on ctrlX with WebIQ Designer as it expects an unencrypted connection on port 10123

That's why you don't usually want to do that.

In TCP/IP you cannot have both HTTP/WS and HTTPS/WSS on the same port - this means that for using an encrypted connection you'd have to setup a separate listener on another port, e.g. 443, then you could connect using wss://192.168.2.10:443.

This also means that you should be able to connect to your system from WebIQ Designer using ws://192.168.2.10:10123 instead of wss://... which is probably the solution for your issue.