-
-
Notifications
You must be signed in to change notification settings - Fork 60
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
Remote servers #60
Comments
If I had a static IP I would help you out. I'm under a strict NAT on a Wireless ISP (WISP) connected to another local ISP as a backbone. Far from an ideal situation. |
Quick tip in case you want to upgrade the main server; |
Hey thanks for the link. I'm checking them out now, seems I could shrink my monthly bill to ~90CAD and have a single server managing it all. Right now I use a "main" server and a secondary for the actual node because both need 50gb+ data. They seem to support 2TB for ~90CAD which is all I need :) |
Hi, |
@SnowLeopard71 I'm already using let's encrypt (see website certs). When it comes to hosting I'm using Hetzner atm. which has nice prices for the bang. The main issue is that atm. Geth needs an SSD. I bought 500gb one to get it syncing but it fills up after a while needing a re-sync from scratch (which reduces use to ~15%!). I'm hoping when geth 1.8 is out with the HDD improvements I can switch back to the big HDD and forget about re-pruning. |
Etherwall needs more remote servers to provide a consistent thin client experience.
I'm currently paying 80CAD/month for the main node but it's running out of space quick.
The server infrastructure now supports offloading to multiple servers. If anyone is willing to donate a server please provide the info here.
The requirements are:
Any sane CPU and RAM for running geth (8gb RAM+)
At least 100gb of free space, more preffered
SSL certificate for WSS/HTTPS support (SSL cert is free, I can provide howto on SSL here and make a *.etherwall.com subdomain for it too)
Capable of setting up nginx and a service for geth (systemd most probably)
The text was updated successfully, but these errors were encountered: