Skip to content

processes running on ports not showing up in Ports but are available #9074

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
sharkymark opened this issue Aug 14, 2023 · 11 comments
Closed

processes running on ports not showing up in Ports but are available #9074

sharkymark opened this issue Aug 14, 2023 · 11 comments
Labels
s3 Bugs that confuse, annoy, or are purely cosmetic site Area: frontend dashboard stale This issue is like stale bread. waiting-for-info The issue creator is asked to provide more information.

Comments

@sharkymark
Copy link
Contributor

Version: v2.0.2+76ad116

My template's startup_script starts an NGINX web server with docker run on 8080 and another process is a Python web server on 8000

They should be listed like in previous versions of Coder.

Both do not show up in the Ports UI but I can curl them or manually enter the port in the Ports UI.

image

image

image

image

image

image

image

@BrunoQuaresma
@sharkymark sharkymark added the bug label Aug 14, 2023
@sharkymark
Copy link
Contributor Author

@BrunoQuaresma found the bug of sorts. You have to refresh the UI for the ports to show up.

@matifali
Copy link
Member

@sharkymark I guess it might be related to #8834.

@BrunoQuaresma
Copy link
Collaborator

Maybe this happens when we try to fetch the ports and the agent is not ready? Or the process that identifies the ports is not ready? cc.: @deansheather do you think this makes sense?

@aslilac
Copy link
Member

aslilac commented Aug 17, 2023

I think it's something a little nastier than that. Even after plenty of time for things to settle, I can refresh the page and only ever see half of the ports being forwarded.

@BrunoQuaresma
Copy link
Collaborator

@aslilac yes, we are not able to automatically find all the ports. @deansheather has more context on that I guess.

@aslilac
Copy link
Member

aslilac commented Aug 17, 2023

@BrunoQuaresma should we add a little warning that the list may not be exhaustive? or is the goal to make it exhaustive?

@BrunoQuaresma
Copy link
Collaborator

I think Dean and @bpmct have more context.

@bpmct
Copy link
Member

bpmct commented Aug 17, 2023

Related: #9135

@deansheather
Copy link
Member

Can you please provide the output of ss -tlpn and the result of accessing http://localhost:8080/api/v0/listening-ports while running coder port-forward workspace --tcp 8080:4?

@deansheather
Copy link
Member

Actually since these are both on workspace proxy enabled deployments I think this is caused by #8909.

@matifali matifali added site Area: frontend dashboard s3 Bugs that confuse, annoy, or are purely cosmetic labels Oct 2, 2023
@matifali
Copy link
Member

matifali commented Oct 2, 2023

@sharkymark, do you still have this? If not let us close this as completed.

@matifali matifali added the waiting-for-info The issue creator is asked to provide more information. label Oct 2, 2023
@github-actions github-actions bot added the stale This issue is like stale bread. label Mar 31, 2024
@sreya sreya closed this as completed Apr 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
s3 Bugs that confuse, annoy, or are purely cosmetic site Area: frontend dashboard stale This issue is like stale bread. waiting-for-info The issue creator is asked to provide more information.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@aslilac @sharkymark @BrunoQuaresma @sreya @matifali @deansheather @bpmct