Skip to content

[vscode-desktop]: Can't preview private ports #8015

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

Closed
filiptronicek opened this issue Feb 3, 2022 · 3 comments
Closed

[vscode-desktop]: Can't preview private ports #8015

filiptronicek opened this issue Feb 3, 2022 · 3 comments
Labels
editor: code (desktop) feature: ports meta: never-stale This issue can never become stale team: IDE type: bug Something isn't working

Comments

@filiptronicek
Copy link
Member

filiptronicek commented Feb 3, 2022

Bug description

Private Gitpod ports can't be accesed by the VS Code Desktop WebViews, rendering them unusable (well, not rendering them at all 😝)

I think this is a similar issue to #4924 (comment), at least the root cause - we need to send a cookie / header with the request, because the WebView does not auth at all, so it receives a 401, which is expected.

Steps to reproduce

  1. Open a workspace, which exposes a port right away so no further repro setup is required, for example the Node.js demo
  2. Open the top context menu (hamburger), click Gitpod: Open in VS Code Insiders
  3. On your desktop VS Code, start
  4. Go to port on the bottom of the screen and click the book with the magnifying glass to preview in Simple Browser.
  5. Observe a white blank screen

Workspace affected

all of 'em

Expected behavior

All ports, private and public can be accessed via the VS Code Desktop integration.

Example repository

https://github.com/gitpod-io/template-typescript-node

Anything else?

No response

@stale
Copy link

stale bot commented Jul 12, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Jul 12, 2022
@filiptronicek filiptronicek added meta: never-stale This issue can never become stale and removed meta: stale This issue/PR is stale and will be closed soon labels Jul 12, 2022
@mustard-mh
Copy link
Contributor

mustard-mh commented Jul 19, 2022

It's correct since 3000 with frame is blocked by server (see error log), try with other port, and it works well

3000 8080
image image

@mustard-mh
Copy link
Contributor

mustard-mh commented Jul 19, 2022

You can disable that blocking behavior by comment this line and re-build + re-serve the server

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
editor: code (desktop) feature: ports meta: never-stale This issue can never become stale team: IDE type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants