serbyxp

I believe I am having the same issue... +---------+-------+ | name |result | +---------+-------+ |connected| yes | |dialable | yes | |nat_type | none | | height |1163251| +---------+-------+ ********************...

The miner name is Noisy Pine Seal. I will try, and figure that out I am new to this whole "dev forums" thing so pardon my formatting and what not....

well, I have attached the logs from var/data/log in a file below, its error.log error.log.1 error.log.0 , from console cat command Noisy Pine Seal , I finally got witnessed by...

@thardie could it be a versioning issue with erlang and the hotspot OS? when I originally tried to compile the gateway-rs for the light hotspot ( thought it would work...

@thardie the only reason I mentioned it, was the fact that all the different manufactures have their OS set up differently, Im sure they all run some sort of docker...

OK so I still haven't added my EEC Hardware to the AMD miner container on my laptop, I'm letting it catch up to the chain... but its not throwing any...

Ill check that out today. I understand the containers are "self contained" but if you got one self contained thing talking to another expecting a specific response, then it could...

As far as the "peer bug" I have not been seeing any peer issues recently my latest info summary... is having snapshot issues on the ARM64.. not sure if this...

Heh wrong place for this, but where you downloaded the script , go to the issues page there, I kinda made a small write up on it… I’m not a...

The refresh thing works, but not as good as my changes, instead of it doing a peer refresh , I changed it to do a peer connect. I mentioned this...