hi, in an effort to document the torcloud process again i started another torlcoud node. this time i got an error. i don't know if it's of concern or not though i guess torcloud log viewing doesn't differ from a home node.
getting ssh to work for the uninitiated is a terrible chore using amazon's recommended windows putty. i just used a linux terminal but the process should be much easier than putty. better is 30 day trial "private shell" but that's not a rousing recommendation for windows usability in a secure tty app. but so far if windows users have difficulty using ssh that's what i'll suggest until i find something better. mac i just used the terminal. macos permits drag and drop for the keys (! nice) though i can understand want of dedicated app to guarantee success. Sep 16 21:02:55.000 [notice] Self-testing indicates your ORPort is reachable fro m the outside. Excellent. Publishing server descriptor. Sep 16 21:02:58.000 [notice] Performing bandwidth self-test...done. *Sep 16 21:03:41.000 [warn] Requested exit point '$xdelted st**ring**' is not known. Closing.** **Sep 16 21:03:41.000 [warn] Making tunnel to dirserver failed.* Sep 17 03:02:40.000 [notice] Heartbeat: Tor's uptime is 6:00 hours, with 0 circu its open. I've sent 2.22 MB and received 13.49 MB. Sep 17 03:02:40.000 [notice] Average packaged cell fullness: 87.125% Sep 17 03:02:40.000 [notice] TLS write overhead: 7% username@ip-xxx:/var/log/tor$ -- tor-talk mailing list - [email protected] To unsubscribe or change other settings go to https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
