Make ports for Steve configurable (9080 and 9443)

[rak-phillip]

Problem Description

Other applications might already be bound to the ports that steve is using. It would be convenient to configure dashboard integration so that this can be changed if there is any conflict.

Proposed Solution

Introduce settings for Dashboard/Steve that will allow for changing ports or other settings.

Additional Information

This might be a bit difficult because dashboard expects a port to be specified when it is bundled, we might need to see if we can update this value on the fly.. Perhaps dashboard will need to be updated to read from some sort of configuration object.

[jandubois]

An alternative would be to let steve pick a random available port, and let RD pick that up somehow.

[sherifosama92]

I had the same problem. The dashboard uses 9080 as its default port. I used these commands Get-Process -Id (Get-NetTCPConnection -LocalPort YourPortNumberHere).OwningProcess Get-Process -Id (Get-NetUDPEndpoint -LocalPort YourPortNumberHere).OwningProcess to discover which application on my computer using this port and it was Logitech lghub mousr software! I closed the software then the dashboard worked!

[televi]

FYI, this isn't limited to Windows - I have this same issue on my Mac (Monterey 12.5) due to the referenced Logitech Ghub conflict. As a workaround, I can start RD first, then start Ghub and everything seems to work fine as Ghub will pick a different port than 9080. For me, using the workaround on my Mac results in the following port assignments:

$ lsof -l -P | grep LISTEN | grep -E 'steve|lghub
steve     42402      502    9u     IPv4 <snip>        0t0                 TCP localhost:9443 (LISTEN)
steve     42402      502   10u     IPv4 <snip>        0t0                 TCP localhost:9080 (LISTEN)
lghub_age 42592      502   23u     IPv4 <snip>        0t0                 TCP localhost:9081 (LISTEN)
lghub_age 42592      502   24u     IPv4 <snip>        0t0                 TCP localhost:9010 (LISTEN)

[skfazil]

Hi Team, my org is in the process of transitioning from Docker Desktop to Rancher Desktop, and during this process we are unable to get a local application up on port 9443 due to the fact that Rancher uses it. This was working with Docker Desktop before. Our local app is tightly configured with port 9443 and used across teams as standard config, so we cannot change it. Having no option of changing this port on the Rancher Desktop, seems to be a serious issue.

When will a solution be in place for this issue. Please provide some insight!

[KevinJoiner]

This would also be helpful for debugging applications outside of docker containers like https://github.com/rancher/webhook that use port 9443

[artemkaxboy]

Hello! Is there any workaround to customize Steve ports at the moment?

[swcolley]

Hi Team, Any update on this issue. Our services use the ports, and configuring rancher desktop to use specific ports would be a more elegant solution than other options.

[samuelfsk]

I'm having the same problem as I have another process running on port 9080. It would be great if it was configurable.

[scenek]

Not elegant, but (on Mac OS) simply kill the steve process if you don't need it to free up the port.

[phalicz-apptio]

I'm having the same problem. Please make ports configurable and use less typical (used in development) ports by default.