Forum Discussion

LChristian's avatar
LChristian
Occasional Contributor
14 years ago

[Resolved] Changing loadUI Agent listening port

Hey,

Is there any way to get the loadUI agent to listen on a port other than 8443?

Thanks.

5 Replies

  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    Hey!

    Yes there is. Add this to the end of loadUI-agent.bat:
    -Dloadui.https.port=4711
    -Dloadui.http.port=1337

    Most communication is done with HTTPS. HTTP is just for alerts/broadcasting and such.

    /Henrik
    eviware.com
  • Beno_Iskratel's avatar
    Beno_Iskratel
    Frequent Contributor
    hi,

    i'm using loadUI on windows.
    is it posible to connect on linux agents?
    when i turn on linux agent, the bright red light does not apper.
    if i have to change ports on linux agents, do i have to modify loadUI-agent.sh?

    regards,
    beno
  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    SmartBear Alumni (Retired)
    You should be able to connect to a linux agent with no trouble. When connecting to an agent which isn't running on the standard port (8447) you will need to provide the port when adding the agent, using the standard <ip>:<port> format. If the light doesn't turn bright red, that means that loadUI isn't able to connect to the agent (though this may take a few seconds).

    Regards,
    Dain
    eviware.com
  • Beno_Iskratel's avatar
    Beno_Iskratel
    Frequent Contributor
    agent is on fedora.
    it's started and listening.
    "nmap localhost" shows me that https-alt port 8443 is used after agent is started.
    should there be also any http port started?

    i can add agent to loadUI, it doesn't complain about ip or something like this.
    it just doesn't upload anything to agent and it doesn't appear bright red alike other agents that are running on windows.


    edit:
    i tried on redhat and it works.

    regards,
    beno
  • Beno_Iskratel's avatar
    Beno_Iskratel
    Frequent Contributor
    it works (loadUI agent on Fedora). it was my mistake.
    i just had to start agent from terminal window, not with shortcut from desktop.

    sry for false reporting,
    beno