Codespaces port forwarding stopped working

[aaronrubinstein]

Select Topic Area

Question

Body

As of a few hours ago port forwarding stop working for me (using the web version of VS code). When I run npm run dev typically I'll see a pop-up in VS code and the forwarded port will also appear under the 'ports' tab, but now neither happen. When I click the link shown in the terminal I get a 502 bad gateway message.

I tried opening a different repository in a new codespace instance and am having he same issue there as well.

[eljog]

@aaronrubinstein thank you for reporting this issue. We will take a look at this issue and get back to you.

[aaronrubinstein]

Per the suggestion here, I added --host to the end of my dev script in package.json and that solved the problem. Very strange as port forwarding had been working fine without --host up until yesterday (I double checked the package.json files in previous Vite projects I built in codespaces and none of them had that). Something must have changed.

[AliasHolmes]

I think Vite has some problem serving from a remote machine. I had the same issue; adding the --host flag did the magic.

[skifli]

Thanks, this solved the problem for me as well.

[vincentmaxwell]

If anyone else has issues with a school account where they are using Codespaces at school behind a firewall, instead of asking your IT department to open ports or whitelist the tunnels api for Visual Code Studio, try this trick instead. This made my port forwarding magically work!

[MarkBennett]

I use a Codespace for a Gatsby project and can confirm that the standard:

yarn gatsby develop

Will cause the connection to be refused and the 502 nginx bad gateway error.

Running with:

yarn gatsby develop -H 0.0.0.0

And using the port from the port list seems to solve this issue.

[benny-png]

Just use port-forwarding services like NGROK lol SUPER easy three line of shell commands https://ngrok.com/download
you can use this for reference https://youtu.be/AhiXVaWst24

[lihugang]

For me, changing to a new port for forwarding solves the problem.

[AlexYuleUSDS]

We are still having this issue -- changing the port visibility to private again seems to fix it but very annoying