- bellaminer
- Archived posts: 20
- Joined: Sep 21, 2017
scrypt not allowing connections
I rebooted a miner and now it can't connect to prohashing's scrypt port. I rebooted a second miner of mine and the same thing is happening. Is this a known issue? I dont want to reboot my other miners or they won't be able to reconnect either.
FYI, from miner:
ping prohashing.com
PING prohashing.com (167.88.15.87): 56 data bytes
64 bytes from 167.88.15.87: seq=0 ttl=54 time=34.566 ms
64 bytes from 167.88.15.87: seq=1 ttl=54 time=34.285 ms
64 bytes from 167.88.15.87: seq=2 ttl=54 time=34.432 ms
64 bytes from 167.88.15.87: seq=3 ttl=54 time=34.212 ms
64 bytes from 167.88.15.87: seq=4 ttl=54 time=33.977 ms
64 bytes from 167.88.15.87: seq=5 ttl=54 time=34.581 ms
--- prohashing.com ping statistics ---
6 packets transmitted, 6 packets received, 0% packet loss
round-trip min/avg/max = 33.977/34.342/34.581 ms
FYI, from miner:
ping prohashing.com
PING prohashing.com (167.88.15.87): 56 data bytes
64 bytes from 167.88.15.87: seq=0 ttl=54 time=34.566 ms
64 bytes from 167.88.15.87: seq=1 ttl=54 time=34.285 ms
64 bytes from 167.88.15.87: seq=2 ttl=54 time=34.432 ms
64 bytes from 167.88.15.87: seq=3 ttl=54 time=34.212 ms
64 bytes from 167.88.15.87: seq=4 ttl=54 time=33.977 ms
64 bytes from 167.88.15.87: seq=5 ttl=54 time=34.581 ms
--- prohashing.com ping statistics ---
6 packets transmitted, 6 packets received, 0% packet loss
round-trip min/avg/max = 33.977/34.342/34.581 ms