You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
About one week ago, everything works well. And today I meet the same error.
Uable to forward localhost:3000. Network Error.
We noticed that you were unable to forward a port due to an issue with your network. Our port forwarding infrastructure has been upgraded and there might be additional actions for you to take to in order to avoid disruption.
I have tried on two of my Windows computer. And one of my friend also tried on his. None of the 3 Windows works.
However, I have tested on this, and it works well.
I open this project in a codespace, and then docker run -p 6080:80 -p 5900:5900 -v /dev/shm:/dev/shm dorowu/ubuntu-desktop-lxde-vnc to start the remote ubuntu desktop.
From the remote desktop, I installed VSCode and extensions, and open a codespace with this "remote desktop VSCode", everything works well. The port can be forwarded.
So I don't think it is a firewall issue. I believe the Github team or VSCode team have done something that lead to this bug. It may be temporary or not.
By the way, I live in China and I use a VPN. (We cannot connect to Github without a VPN.) I'm not sure if that matters. The 3-Windows-tests above all use a VPN tool called clash. Here is the link https://github.com/MetaCubeX/mihomo/tree/Alpha
That issue was reported few months ago. I think the Github team may have fixed that issue at that time. But the modification today(or yesterday) breaks things down agian.
CodespacesYour development environment, in the cloud. Run VS Code and code on GitHub's cloud platform,Question
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Select Topic Area
Question
Body
About one week ago, everything works well. And today I meet the same error.
I have tried on two of my Windows computer. And one of my friend also tried on his. None of the 3 Windows works.
However, I have tested on this, and it works well.
https://github.com/fcwu/docker-ubuntu-vnc-desktop
I open this project in a codespace, and then
docker run -p 6080:80 -p 5900:5900 -v /dev/shm:/dev/shm dorowu/ubuntu-desktop-lxde-vnc
to start the remote ubuntu desktop.From the remote desktop, I installed VSCode and extensions, and open a codespace with this "remote desktop VSCode", everything works well. The port can be forwarded.
So I don't think it is a firewall issue. I believe the Github team or VSCode team have done something that lead to this bug. It may be temporary or not.
By the way, I live in China and I use a VPN. (We cannot connect to Github without a VPN.) I'm not sure if that matters. The 3-Windows-tests above all use a VPN tool called clash. Here is the link https://github.com/MetaCubeX/mihomo/tree/Alpha
This bug is duplicated with https://github.com/orgs/community/discussions/68324#discussioncomment-9235675
That issue was reported few months ago. I think the Github team may have fixed that issue at that time. But the modification today(or yesterday) breaks things down agian.
Beta Was this translation helpful? Give feedback.
All reactions