Issue changing FQDN workspace 2.1

[VirtualSven]

I have an issue changing the FQDN. I have one workspace appliance called "workspace-va01.domain.local" and I have a reverse proxy pointing to the local server with FQDN "workspace.domain.com". After deployment of the workspace portal, I want to change the FQDN of Horizon Workspace to the external address. Unfortunately I get the following error:

Error updating manager url on connector.

Updating IdP url on Connector...

Error updating IdP url on connector.

Updating workspace url in runtime config and restarting service...

The FQDN is correctly changed, but the manager url and the IdP url are not. When users want to login, they are redirected to the server address "workspace-va01.domain.local", which is not accessible externally of course. What am I doing wrong?

[pbjork]

Hard to say to be honest.. Workspace Portal 2.1 should by default hide the connector URL from users. There is a setting on the connector admin page to redirect users. Make sure that is not enabled.

Since you get Error updating IdP url on connector. Can it be because your VM is joined to the domain?

[VirtualSven]

The connector was joined to the domain, but I re-deployed the appliance and still get the error.

I've just tested from externally, and I get this error when trying to login:

Unable to read metadata from server

[pbjork]

Can you explain a little more about your setup?

What reverse proxy/load balancer do you use?

Are you using a publicly signed certificate?

Are you using split DNS? (i.e. internally Workspace FQDN points to a different IP than it resolves to externally)

Have you looked at this blog post? Workspace Portal - Trouble Changing the FQDN | Horizon Tech Blog - VMware Blogs

[VirtualSven · Accepted solution]

I figured it out. The problem was that I first replaced the certificate and then changed the FQDN. In the logfile I did see a couple of errors that the name of the workspace appliance was not in the certificate. I changed the certificate back to self-signed, then changed the FQDN to workspace.domain.com and then replaced the certificate. All is working well now!

[pbjork]

Glad it is all sorted..