Meta tags:
description=You can forward ports in your codespace to test and debug your application. You can also manage the port protocol and share the port within your organization or publicly.;
keywords=Codespaces,Fundamentals,Developer;

Headings (most frequently used words):

port, forwarding, codespace, sharing, labeling, adding, to, the, configuration, help, ports, in, this, your, article, about, forwarded, using, https, did, doc, you, us, make, these, docs, great, still, need,

Text of the page (most frequently used words):
the (172), port (124), you (72), #codespace (64), ports (58), your (53), github (49), for (43), can (39), forwarded (38), codespaces (38), click (32), organization (30), make (22), label (20), then (19), and (19), visibility (19), that (18), forward (17), configuration (17), application (17), private (17), with (17), see (15), want (15), forwarding (14), under (13), editor (13), public (13), url (13), more (12), information (12), add (12), code (12), share (12), this (11), text (11), using (11), repository (11), after (11), about (10), browser (10), running (10), use (9), cli (9), local (9), machine (9), type (9), enter (9), set (9), update (9), automatically (9), list (9), note (9), docs (8), press (8), right (8), change (8), view (8), http (8), manually (7), desktop (7), from (7), adding (7), when (7), command (7), number (7), anyone (7), default (7), restrict (7), web (7), devcontainer (6), json (6), created (6), dev (6), labeling (6), team (6), sharing (6), access (6), security (5), all (5), open (5), policy (5), jetbrains (5), configure (5), will (5), select (5), icon (5), restricting (5), enterprise (5), publicly (5), https (5), help (4), any (4), introduction (4), containers (4), hover (4), over (4), org (4), who (4), knows (4), only (4), may (4), cloud (4), address (4), within (4), terminal (4), localhost (4), visual (4), studio (4), protocol (4), developing (4), prebuilds (4), api (3), support (3), pull (3), page (3), file (3), property (3), panel (3), opened (3), forwardports (3), previously (3), must (3), rebuilt (3), apply (3), easier (3), identify (3), replace (3), choose (3), setting (3), visible (3), members (3), choice (3), options (3), limited (3), configured (3), others (3), either (3), without (3), needing (3), authenticate (3), uses (3), also (3), into (3), forwards (3), ides (3), manage (3), search (3), english (3), free (3), pro (3), logs (3), repo (3), contact (2), privacy (2), 2022 (2), learn (2), how (2), are (2), source (2), article (2), manual (2), example (2), settings (2), entering (2), displayed (2), subcommand (2), send (2), copied (2), person (2), copy (2), menu (2), wasn (2), owners (2), ability (2), available (2), inside (2), prints (2), output (2), contains (2), such (2), string (2), converted (2), link (2), 127 (2), needed (2), beta (2), test (2), copilot (2), requests (2), started (2), gpg (2), verification (2), deletion (2), changes (2), timeout (2), encrypted (2), secrets (2), managing (2), container (2), template (2), create (2), 2021 (2), blog, training, developer, pricing, status, terms, inc, provide, feedback, still, need, contribute, contribution, something, wrong, unclear, submit, request, these, great, did, doc, alternatively, tab, top, section, documentation, model, labels, 3000, 3306, multiple, one, owns, there, three, details, remote, connect, remembered, lifetime, but, gives, tcp, particular, allows, testing, debugging, currently, subject, debug, 한국어, русский, français, deutsch, português, brasil, español, 日本語, 简体中文, versions, npm, codeql, electron, atom, education, pages, building, communities, sponsors, discussions, graphql, rest, developers, packages, actions, issues, organizations, site, billing, payments, administrators, repositories, authentication, account, profile, get, guides, based, working, clients, dotfiles, connection, creation, exporting, troubleshooting, disaster, recovery, full, rebuilds, palette, plugin, registry, reference, retention, period, periods, base, image, types, audit, costs, enable, allow, external, prebuilding, automatic, region, rename, personalize, customizing, badge, opening, files, features, minimum, spec, learning, connecting, network, environment, variables, stop, control, existing, delete, develop, deep, dive, lifecycle, quickstart, getting, overview, products, skip, main, content, wayback, archive, 20221208233829, com, timestamps, capture, fail, success, 2023, jan, dec, nov, jul, 2026, captures,

Text of the page (random words):
forwarding ports in your codespace github docs 56 captures 06 may 2021 08 jul 2026 nov dec jan 08 2021 2022 2023 success fail about this capture timestamps the wayback machine http web archive org web 20221208233829 https docs github com en codespaces developing in codespaces forwarding ports in your codespace skip to main content github docs all products github codespaces overview getting started quickstart for codespaces the codespace lifecycle deep dive into codespaces developing in a codespace develop in a codespace create a codespace for a repo create a codespace from a template delete a codespace open an existing codespace source control pull requests stop a codespace forward ports default environment variables connecting to a private network machine learning visual studio code jetbrains ides github cli setting up your repository introduction to dev containers add a dev container to your repository set a minimum machine spec adding features automatically opening files add a codespaces badge set up a template repo customizing your codespace personalize your codespaces rename a codespace change the machine type set the default editor set the default region set the timeout configure automatic deletion prebuilding your codespaces about prebuilds configure prebuilds allow external repo access manage prebuilds test dev container changes managing your codespaces encrypted secrets repository access security logs gpg verification managing your organization enable codespaces list organization codespaces manage codespaces costs encrypted secrets repository access audit logs restrict machine types restrict base image restrict port visibility restrict timeout periods restrict the retention period reference access a private registry copilot in codespaces plugin for jetbrains vs code command palette security in codespaces full rebuilds disaster recovery troubleshooting codespaces logs exporting changes creation and deletion connection codespaces prebuilds dotfiles port forwarding codespaces clients gpg verification working with support web based editor guides github codespaces developing in a codespace forward ports free pro team english search github docs github docs github codespaces developing in a codespace forward ports github codespaces get started account and profile authentication repositories enterprise administrators billing and payments site policy organizations code security pull requests github issues github actions github copilot github codespaces github packages search on github developers rest api graphql api github cli github discussions github sponsors building communities github pages education github desktop github support atom electron codeql npm free pro team free pro team enterprise cloud about versions english english 简体中文 日本語 español português do brasil deutsch français русский 한국어 search github docs forwarding ports in your codespace in this article about forwarded ports forwarding a port using https forwarding sharing a port labeling a port adding a port to the codespace configuration forwarding a port sharing a port labeling a port adding a port to the codespace configuration sharing a port labeling a port adding a port to the codespace configuration forwarding a port you can forward ports in your codespace to test and debug your application you can also manage the port protocol and share the port within your organization or publicly github cli jetbrains ides beta visual studio code web browser note using github codespaces with jetbrains ides is currently in public beta and is subject to change about forwarded ports port forwarding gives you access to tcp ports running within your codespace for example if you re running a web application on a particular port in your codespace you can forward that port this allows you to access the application from the browser on your local machine for testing and debugging when an application running inside a codespace prints output to the terminal that contains a localhost url such as http localhost port or http 127 0 0 1 port the port is automatically forwarded if you re using github codespaces in the browser or in visual studio code the url string in the terminal is converted into a link that you can click to view the web page on your local machine by default github codespaces forwards ports using http you can also forward a port manually label forwarded ports share forwarded ports with members of your organization share forwarded ports publicly and add forwarded ports to the codespace configuration note organization owners can restrict the ability to make forward ports available publicly or within the organization for more information see restricting the visibility of forwarded ports forwarding a port you can manually forward a port that wasn t forwarded automatically in your codespace under the text editor click ports under the list of ports click add port type the port number or address then press enter using https forwarding by default github codespaces forwards ports using http but you can update any port to use https as needed if you update a port with public visibility to use https the port s visibility will automatically change to private in your codespace under the text editor click ports right click the port you want to update then hover over change port protocol select the protocol needed for this port the protocol that you select will be remembered for this port for the lifetime of the codespace sharing a port note you can only make a port private to an organization if your organization uses github team or github enterprise cloud if you want to share a forwarded port with others you can either make the port private to your organization or make the port public after you make a port private to your organization anyone in the organization with the port s url can view the running application after you make a port public anyone who knows the url and port number can view the running application without needing to authenticate note your choice of port visibility options may be limited by a policy configured for your organization for more information see restricting the visibility of forwarded ports in your codespace under the text editor click ports right click the port that you want to share select the port visibility menu then click private to organization or public to the right of the local address for the port click the copy icon send the copied url to the person you want to share the port with labeling a port when you open a codespace in the browser or in the vs code desktop application you can label a forwarded port to make it easier to identify in a list in your codespace under the text editor click ports hover over the port you want to label then click the label icon type a label for your port then press enter adding a port to the codespace configuration you can add a forwarded port to the github codespaces configuration for the repository so the port will automatically be forwarded for all codespaces created from the repository after you update the configuration any previously created codespaces must be rebuilt for the change to apply for more information see introduction to dev containers you can manually configure forwarded ports in a devcontainer json file using the forwardports property or you can use the ports panel in a codespace that you ve opened in the browser or the vs code desktop application in your codespace under the text editor click ports right click the port you want to add to the codespace configuration then click set label and update devcontainer json type a label for your port then press enter when an application running inside a codespace prints output to the terminal that contains a localhost url such as http localhost port or http 127 0 0 1 port the port is automatically forwarded if you re using github codespaces in the browser or in visual studio code the url string in the terminal is converted into a link that you can click to view the web page on your local machine by default github codespaces forwards ports using http you can also forward a port manually label forwarded ports share forwarded ports with members of your organization share forwarded ports publicly and add forwarded ports to the codespace configuration note organization owners can restrict the ability to make forward ports available publicly or within the organization for more information see restricting the visibility of forwarded ports forwarding a port you can manually forward a port that wasn t forwarded automatically in your codespace under the text editor click ports under the list of ports click add port type the port number or address then press enter sharing a port note you can only make a port private to an organization if your organization uses github team or github enterprise cloud if you want to share a forwarded port with others you can either make the port private to your organization or make the port public after you make a port private to your organization anyone in the organization with the port s url can view the running application after you make a port public anyone who knows the url and port number can view the running application without needing to authenticate note your choice of port visibility options may be limited by a policy configured for your organization for more information see restricting the visibility of forwarded ports in your codespace under the text editor click ports right click the port that you want to share select the port visibility menu then click private to organization or public to the right of the local address for the port click the copy icon send the copied url to the person you want to share the port with labeling a port when you open a codespace in the browser or in the vs code desktop application you can label a forwarded port to make it easier to identify in a list in your codespace under the text editor click ports hover over the port you want to label then click the label icon type a label for your port then press enter adding a port to the codespace configuration you can add a forwarded port to the github codespaces configuration for the repository so the port will automatically be forwarded for all codespaces created from the repository after you update the configuration any previously created codespaces must be rebuilt for the change to apply for more information see introduction to dev containers you can manually configure forwarded ports in a devcontainer json file using the forwardports property or you can use the ports panel in a codespace that you ve opened in the browser or the vs code desktop application in your codespace under the text editor click ports right click the port you want to add to the codespace configuration then click set label and update devcontainer json type a label for your port then press enter to learn more about github cli see about github cli to forward a port use the gh codespace ports forward subcommand replace codespace port local port with the remote and local ports that you want to connect after entering the command choose from the list of codespaces that s displayed gh codespace ports forward codespace port local port for more information about this command see the github cli manual to see details of forwarded ports enter gh codespace ports and then choose a codespace sharing a port note you can only make a port private to an organization if your organization uses github team or github enterprise cloud if you want to share a forwarded port with others you can either make the port private to your organization or make the port public after you make a port private to your organization anyone in the organization with the port s url can view the running application after you make a port public anyone who knows the url and port number can view the running application without needing to authenticate note your choice of port visibility options may be limited by a policy configured for your organization for more information see restricting the visibility of forwarded ports to change the visibility of a forwarded port use the gh codespace ports visibility subcommand there are three visibility settings private visible only to you this is the default setting when you forward a port org visible to members of the organization that owns the repository public visible to anyone who knows the url and port number replace codespace port with the forwarded port number replace setting with private org or public after entering the command choose from the list of codespaces that s displayed gh codespace ports visibility codespace port settings you can set the visibility for multiple ports with one command for example gh codespace ports visibility 80 private 3000 public 3306 org for more information about this command see the github cli manual labeling a port when you open a codespace in the browser or in the vs code desktop application you can label a forwarded port to make it easier to identify in a list in your codespace under the text editor click ports hover over the port you want to label then click the label icon type a label for your port then press enter you can see the port labels when you list the forwarded ports for a codespace to do this use the gh codespace ports command and then select a codespace adding a port to the codespace configuration you can add a forwarded port to the github codespaces configuration for the repository so the port will automatically be forwarded for all codespaces created from the repository after you update the configuration any previously created codespaces must be rebuilt for the change to apply for more information see introduction to dev containers you can manually configure forwarded ports in a devcontainer json file using the forwardports property or you can use the ports panel in a codespace that you ve opened in the browser or the vs code desktop application in your codespace under the text editor click ports right click the port you want to add to the codespace configuration then click set label and update devcontainer json type a label for your port then press enter forwarding a port for information on how to forward a port in a codespace to a port on your local machine see the port forwarding section of the security model article in the jetbrains documentation alternatively you can use github cli to forward a port for more information click the github cli tab at the top of this page did this doc help you privacy policy help us make these docs great all github docs are open source see something that s wrong or unclear submit a pull request make a contribution or learn how to contribute still need help provide github feedback contact support 2022 github inc terms privacy security status help contact github pricing developer api training blog about