Robotic Process Automation RPA

Expand all | Collapse all

Issue with hostname when connecting to on prem WDG

  • 1.  Issue with hostname when connecting to on prem WDG

    Posted Mon July 26, 2021 05:44 PM
    Hi there,
    I have wdg installed, and just about everything is working.  I had one issue during the install however.  When it asked for the hostname or ip, I wanted to put our external dns name in there, but it only allowed me to put the hostname of the server (rpaserver).  Now when I try and connect the wdg client to the server, it tries to use the internal hostname, instead of the external domain.  It should be connecting to https://externalhostname.com:30000, but you can see from the logs that it's not.  Is there a way to tell the wdg server to only use the external hostname?


    2021-07-20 13:45:20.8256896WARNPersistedHubConnectionWDG.Automation.Service[SignalR (https://rpaserver:30000/v1.0)] Connection closed. Waiting 00:00:10 to reconnect(null)'g C9 9 2021-07-20 13:45:20.8068023INFOPersistedHubConnectionWDG.Automation.Service[SignalR (https://rpaserver:30000/v1.0)] from Connecting to Disconnected(null)'f C9 9 2021-07-20 13:45:18.4897545INFOPersistedHubConnectionWDG.Automation.Service[SignalR (https://rpaserver:30000/v1.0)] from Disconnected to Connecting(null) e C5 9o 2021-07-20 13:45:17.7435037INFOConsoleServiceWorkerWDG.Automation.ServiceLaunching 'WDG.Automation.AgentHost' on session=1(null),d C7 9) 2021-07-20 13:45:15.6135172INFOLoggingMessageHandlerWDG.Automation.ServiceStart [GET] https://rpaserver:30000/secureapi/v1.0/en-US/queue-provider/system(null)‚c C7 9‚u 2021-07-20 13:45:15.5608303INFOLoggingMessageHandlerWDG.Automation.ServiceStart [GET] https://rpaserver:30000/secureapi/v1.0/en-US/computer/8c85c065-241b-49c2-be96-a8c5a9ca675d/info?includePrivateKey=True&includePublicKey=False&includeQueueProvider=False(null)1b CM 9™ 2021-07-20 13:45:15.5238437INFOSelfSignedCertificatesGenerationWDG.Automation.Service[NetworkShell] Command <cmd.exe /c netsh http show sslcert ipport=0.0.0.0:8098> executed
    Exit Code=0

    ------------------------------
    Michael Ottersen
    ------------------------------


  • 2.  RE: Issue with hostname when connecting to on prem WDG

    Posted Thu July 29, 2021 09:04 AM
    @Jukka Juselius - Any ideas on this? We really need to be able to do an on-prem install. This is blocking us. Thanks.​​

    ------------------------------
    Brian French
    Managing Partner
    Salient Process, Inc
    ------------------------------



  • 3.  RE: Issue with hostname when connecting to on prem WDG

    Posted Thu July 29, 2021 10:13 AM

    Hello, Michael!

    As I understand from your report, the problem was only during the installation. After that, your instance is behaving as expected, following what was configured.

    If after the installation you want or need to update the API endpoint where your client instance is looking at, just open the instance configuration by navigating to the following page: "https://localhost:8099/web/en-US/configuration". In the second tab, provide the API address in this pattern: "https://address:port", not ending with "/", and confirm. Note that this will make your whole client environment stop communicating through the previous path and start looking for the API through the new address provided. If something goes wrong in this process, you will have to point to a valid API endpoint.

    I'm curious about what you experienced during the installation. You mentioned that it didn't allow you to provide the external address. Can you give more details on this?
    Basically, you need to put the Server API address in this pattern: "https://address:port" (not ending with "/"). But you must make sure that you have access to it beforehand. This may include: pinging the server address, running a "tracert" command, or even trying to access "https://address:port/v1.0/en-us/configuration" that is one of the available endpoints in the API. If this returns an XML with server information, your client machine is able to reach most of the API endpoints without external interference (a firewall, for example). If your machine can't see the API, the installer won't proceed to the next step. I would suggest you open a ticket because this would be the first report of this behavior (if everything suggested above is ok).

    Please share your results.



    ------------------------------
    Antonio Campos - WDG
    ------------------------------



  • 4.  RE: Issue with hostname when connecting to on prem WDG

    Posted Thu July 29, 2021 11:02 AM
    Hi Antonio, thanks for the response. We'll try your suggestions within the next hour or two.

    ------------------------------
    Brian French
    Managing Partner
    Salient Process, Inc
    ------------------------------



  • 5.  RE: Issue with hostname when connecting to on prem WDG

    Posted Fri July 30, 2021 08:40 AM
    No luck with that so we're going to go the PMR route. Thanks for your reply.

    ------------------------------
    Brian French
    Managing Partner
    Salient Process, Inc
    ------------------------------



  • 6.  RE: Issue with hostname when connecting to on prem WDG

    Posted Thu August 05, 2021 03:55 PM
    Hi Antonio,
    Just for reference, I'll show you where I'm having an issue.  In the hostname part of the install, If I use a fully qualified domain name that's defined in the hosts file and dns, it complains that the address is not valid.  I'm forced to use the hostname of the machine itself.  So then when trying to connect the client to the rpa server, it switches back to the internal hostname, which isn't exposed.  Hopefully that makes sense.



    ------------------------------
    Michael Ottersen
    ------------------------------