-
Notifications
You must be signed in to change notification settings - Fork 2
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
Connect to remote Cyphernode via nginx proxy #24
Comments
Hey, My pleasure, glad it's being used. There's two connections going on in your case, not sure which one is bugging out for you but:
If that's not working , can you give me a bit more details about the error your facing i could probably help you out a bit more.. PS Thanks for Types PR will check it this evening :) |
Thanks @gabidi, ended up getting it going shortly after this - I'd misconfigured the proxy originally, which was the cause of the errors. Is it also possible to use the cyphernode-js-sdk to connect to gatekeeper endpoints (e.g. /getbestblockhash) through the Tor Hidden Service/Gateway onion url? If so, I'm interested in hearing your thoughts on how such a setup would compare to a vanilla proxy setup over tls (assuming iptables/ufw/fail2ban etc), specifically in terms of security. Thanks! |
Hi, Glad you resolved the issue. Also Sifir's cyphernode app implements a more complicated use case where it creates it's own Tor endpoint on Traefik, you can see the docker file for some details: |
We're exploring making use of this great project to connect a server (with cyphernode-js-sdk installed) to a separate Cyphernode instance via a nginx proxy.
I haven't quite figured out how to get it going yet, but I was wondering if you have any thoughts on what might be the most secure and intelligent approach in achieving this. So far I've setup and played around with a local installation of the sdk connecting to a local Cyphernode and its working great, but I haven't yet manage to get connected to the Cyphernode gatekeeper through the proxy.
Thanks for the great project @gabidi !
The text was updated successfully, but these errors were encountered: