-
Notifications
You must be signed in to change notification settings - Fork 85
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
[Feature Request] Set proxy for internal full node or light client. #3099
Comments
Good point, it should be available in the following releases |
Mark this issue stale because no activity for 60 days |
Close this issue because it's inactive since marked stale |
WIP |
Sorry, we can't support this suggestion at this time. @yangby-cryptape After our technical team tried to develop it, we realized that node support was needed, but after evaluation by the ckb core team, it was not considered a high-priority task. So we suggest you try global proxy or adjust proxy rules to add node proxy, because if only Neuron uses proxy can't control the node. |
Ref: nervosnetwork/ckb#4473 (comment). ping @Danie0918 |
Hi @yangby-cryptape |
Due to the poor Internet in some countries, both the internal full node and the internal light client are really slow with the default configuration.
So, I used the parameter
--proxy-server="socks5://localhost:8888"
to start Neuron.It's a common parameter for all Applications based on Electron.
But I found it didn't work for the internal node or the internal light client, it only worked for the Neuron itself. Because I only found logs to query
github.com
andgithubassets.com
from my proxy server.As the developers of Neuron said in #3098:
I think an official setting for set proxy for the internal node and the internal light client is required.
The text was updated successfully, but these errors were encountered: