Quote from: Kolbas on September 12, 2016, 01:27:28 AM

Quote from: defaced on September 11, 2016, 01:34:33 PM

Quote from: 64dimensions on September 10, 2016, 11:16:21 AM

Is there an issue with synchronizing with the peers?

This is a new error message from gexp.

Where do you live?

The problem is that the TCP UDP settings etc were never fixed from the initial issues as noted below:

Quote from: defaced on September 14, 2015, 11:41:03 AM

All seven of my nodes appear to be on the main chain.

2 of which are on windows with 10+ peers.

ocminer what's your node ill add it to the bootnodes so that people are always trying your connection.

Furthermore, https://github.com/ethereum/go-ethereum/issues/1579

Its not just an expanse problem.

I have tried to put up an Expanse Pool for the last few days but it is almost impossible because errors continually pop up. Particularly the ones like "no new work available". I tried to hack Go-Expanse to work with the updates from ethereum but run into a wall at needing an "fdtrack" on Expanses github or I would need to copy the Erthereum one and create my own Github and GOPATH for it. That is to much damn work since those fixes could have been implemented in Aug 2015 but never were updated.

As you can see from the quote above, the Expanse team has known about it but has not fixed the files that are needed to be fixed. So I will list them for you here

1 - p2p/discover/node.go
2 - p2p/discover/table.go
3 - p2p/discover/udp.go
4 - p2p/server.go

If you need the link to the commits just click on the link from well, you. Then go to "files changed"

Or you can keep telling people that it has to do with where they live or some other BS

edited to add the link for the fix:
https://github.com/ethereum/go-ethereum/pull/1689/files

submit a pull request, thanks!