If your connection indicator is yellow, check your firewall settings and port forwarding to make sure incoming connections are allowed to your machine on the correct port (Default TCP 8444). If your connection indicator is green then you are already accepting incoming connections and helping the Bitmessage network. How do I become a node to help the network
BITMESSAGE 1488 HOW TO
Several examples of how to install Bitmessage on *nix and OSX platforms can be found in the forums.
BITMESSAGE 1488 WINDOWS
The start-on-boot and minimize-to-tray features are only implemented for Windows thus far. W 2015.07.Installation and configuration How do I install BitmessageĪ great write up for setting up and using Bitmessage on Windows can be found Here.īitmessage should run on any OS though it is only lightly tested on OSX. W 2015.07.23 16:03:59 - Checking route, 5° try failed (The request timed out) W 2015.07.23 16:03:49 - Checking route, 4° try failed (The request timed out) W 2015.07.23 16:03:39 - Checking route, 3° try failed (The request timed out) W 2015.07.23 16:03:29 - Checking route, 2° try failed (The request timed out)
W 2015.07.23 16:03:19 - Checking route, 1° try failed (The request timed out) I 2015.07.23 16:03:09 - DNS of a network adapter forced (Thunderbolt Ethernet) I 2015.07.23 16:03:09 - DNS of a network adapter forced (Bluetooth DUN) 2015.07.23 16:03:09 - OpenVPN > Initialization Sequence Completed Yesterday I was at Greece, all fine and working. Tue Jul 14 18:34:30 2015 SIGTERM received, process exiting Tue Jul 14 18:34:30 2015 RESOLVE: signal received during DNS resolution attempt Tue Jul 14 18:34:26 2015 RESOLVE: Cannot resolve host address: : El nombre solicitado es válido pero no se encontraron datos del tipo solicitado. Tue Jul 14 18:34:21 2015 RESOLVE: Cannot resolve host address: : El nombre solicitado es válido pero no se encontraron datos del tipo solicitado. Tue Jul 14 18:34:20 2015 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Tue Jul 14 18:34:20 2015 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Tue Jul 14 18:34:20 2015 Control Channel Authentication: tls-auth using INLINE static key file Tue Jul 14 18:34:20 2015 MANAGEMENT: CMD 'hold release'
Tue Jul 14 18:34:20 2015 Need hold release from management interface, waiting.
0 kommentar(er)
