Ports stuck at detecting

[DataCleansingEnthusiast]

Bug description

Ports stuck at detecting...
I am a paid customer of gitpod. From past 24 hours, when I try to run docker compose up to bring up my application I get Ports stuck at detecting. I tried to change the ports to a different number and tested. It worked, but when I commited the code and opened the workspace and I have the same error.
I am in US region. Please help
Thanks

Steps to reproduce

1. open new gitpod workspace from github
2. docker-compose up
3. Ports are stuck at detecting

Workspace affected

No response

Expected behavior

Example repository

Anything else?

No response

[axonasif]

Hi @DataCleansingEnthusiast, is this still happening?
Also, could you please share an example workspace ID and a timestamp of the event?

[DataCleansingEnthusiast]

Yes, still happening from yesterday early morning PST.
Workspace ID : datacleansi-awsbootcamp-f3y8veklrpt
I just checked again 12.26 PM PST

[NsinghP]

I am suffering from same problem. It has been over 24 hours now. Please see the attached image on windows11/firefox:

and the "Ports" window shows "detecting" for port 3000.

EDIT/FYI: I have also tried from Linux Mint PC/Firefox and same problem happens.

[alesanchezr]

Yes this is happening since friday, all our students have the same issue, some times it gets fixed by running gp ports expose <port number> but then its impossible to make the ports public.

[cjensenius]

@axonasif We have been experiencing this since Friday afternoon as well, at least 5 in our org have confirmed. I am currently experiencing this in the greenit-spower-bulwhfapuce workspace in ws-us96b

This is the state for any ports marked 'public' in the .gitpod.yml file. If I click the 'lock' icon in the ports tab nothing happens. Let me know if I can provide any debugging information that would be helpful

[axonasif]

@alesanchezr I think you're looking for gp ports visibility <port>:public.

• https://www.gitpod.io/docs/references/gitpod-cli#visibility

[cjensenius]

I'm seeing if others on the team can replicate this, on my workstation if I have the gitpod local companion app running (Windows 10) the ports do not become stuck in 'detecting...' state. I replicated this workaround three times, and confirmed that if I do not have the companion app running the issue manifests two times.

[mikenikles]

Still happening, for public ports only in our case. On cluster ws-us96b. At which point is this considered an issue and gets reported via https://www.gitpodstatus.com?

Looking at recent GitHub issues and the Questions in Discord, there have been a number of reports over the last few days.

[axonasif]

Hey folks, sorry about the issue you experienced, it was resolved a while back.

https://www.gitpodstatus.com/incidents/6h1gd447lk7b

All newly created workspaces should contain the fix.

[cjensenius]

@axonasif The ports issue persists after the fix, I have confirmed reports from other team members. I am personally observing the issue currently in a newly launched workspace (greenit-spower-s6tvc58lvcr.ws-us96b.gitpod.io)

If I have the local-app running (Windows 10), the issue is not triggered

[axonasif]

@cjensenius oops, please hold on a bit. There was a mismatch in our recent deployment an hour ago that bought it back. It should be fixed in our next deployment.

Meanwhile, as a workaround you can use VSCode desktop or gp preview command

[axonasif]

@cjensenius a new deployment was made about 30 mins before, should be working again.