Skip to content
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.

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

[BUG] Cannot open port on cloud shell #372

Open
alefred opened this issue Jan 18, 2024 · 8 comments
Open

[BUG] Cannot open port on cloud shell #372

alefred opened this issue Jan 18, 2024 · 8 comments
Labels
bug Something isn't working Priority 1

Comments

@alefred
Copy link

alefred commented Jan 18, 2024

Hi everyone,
I was testing some labs from cloud shell and I identify this error.

To Reproduce

When try to open port to do a external access from cloud shell:

curl -X POST http://localhost:8888/openPort/8000

Also if it's executed by Portal UI:
image

Observed Behavior

From the command line:

{"message":"Port 8000 is open","url":"https://ux.console.azure.com//proxy/8000/"}

From portal UI after click on Open and Browse:
image

Expected behavior

After open a port is expected to show the gateway url such us:

{"message":"Port 8000 is open","url":"https://gateway11.northeurope.console.azure.com/n/cc-4016c848/cc-4016c848/proxy/8000/"}

Is this specific to Cloud Shell?

Yes

Interface information

https://shell.azure.com
ttps://portal.azure.com

Additional context

If I executed from Cloud Shell url show another url access:
https://ccon-prod-westeurope-aci-02.servicebus.windows.net/cc-E7RF-C8E55DBE/proxy/8000/

image

Let me know if there is a workaround to solve this.

Luis

@alefred alefred added bug Something isn't working Triage-needed Triage needed by Cloud Shell team labels Jan 18, 2024
@darrentu
Copy link
Contributor

Hi @alefred, yes, we do see this problem and are working on it. Sorry for the inconvenience.

@ivanthewebber
Copy link

See also: #343

@alexandru-negoita
Copy link

Still happening

@BFuhry
Copy link

BFuhry commented Mar 28, 2024

@christianviller
Copy link

Still observing the same issue, any updates or workarounds?

@mbifeld mbifeld added Priority 1 and removed Triage-needed Triage needed by Cloud Shell team labels Apr 9, 2024
@faulkdev
Copy link

faulkdev commented May 8, 2024

Still a problem on May 08, 2024. Anyone from the Azure team addressing this issue? (Tasks that should be simple now require lots of manual work-arounds by customers.)

@marcelloraffaele
Copy link

I have the same problem completing the https://learn.microsoft.com/en-us/training/modules/control-access-to-azure-storage-with-sas/4-exercise-use-shared-access-signatures?source=learn

@f0x4c1d
Copy link

f0x4c1d commented Sep 25, 2024

I have the same problem completing the https://learn.microsoft.com/en-us/training/modules/control-access-to-azure-storage-with-sas/4-exercise-use-shared-access-signatures?source=learn

I have also the same issue to complete this exercise. I got the following message:

The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Priority 1
Projects
None yet
Development

No branches or pull requests

10 participants