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

QuickStart CanNOT running very well #234

Open
Daolang239342 opened this issue Aug 11, 2024 · 6 comments
Open

QuickStart CanNOT running very well #234

Daolang239342 opened this issue Aug 11, 2024 · 6 comments

Comments

@Daolang239342
Copy link

My English is NOT very good so I use translator.
When running the second line command of QuickStart, the first few replies such as "go: downloading GitHub/TwiN/go away v1.6.11" are normal until line 22 when the connection times out and an error message appears as shown in the figure.

My go version is 1.18.1 My Ubuntu version is22.04.4LTS

I'm REALLY sorry that I'm not a professional engineer, so my expression may not be very clear.
截屏2024-08-11 21 29 39
截屏2024-08-11 21 30 41
截屏2024-08-11 21 30 51

@PPTide
Copy link
Contributor

PPTide commented Aug 11, 2024

Your computer seems to not allow you to load https://proxy.golang.org/

You can try running export GOPROXY=direct before running any of the commands.

@Daolang239342
Copy link
Author

Daolang239342 commented Aug 11, 2024 via email

@Arkaeriit
Copy link
Collaborator

Please paste your logs instead of posting screenshot. And we didn't receive the last screenshot.

@Daolang239342
Copy link
Author

Now I have resolved the operational issue. But there was a situation where it could not be accessed through the public network (I am confident that I have turned off all firewalls).
SSH (port 22) access to the public network system is normal, but port 8080 cannot be accessed through the public network. When connecting to the public network, an error message will appear: 'Connection timeout'. May I ask what problem this may be? (If there are any errors in my expression, please feel free to correct me)

@Arkaeriit
Copy link
Collaborator

If one port works but not the other, it does look like a firewall issue.

@Daolang239342
Copy link
Author

I shut down all firewalls including routers, servers and clients

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants