[MOJO] MOJOv3 has been taken over by new devs

[dsutil]

Sorry, I meant:
The explanation here was, that there was a fork, but I can't believe that this was the reason for connection problems.

I don't believe this either ...

I compile ALL wallets with use_upnp=-  under linux and create the port forwarding by hand in iptables. I never open incoming ports on my windows machine (for obvlious reasons) and of course don't use UPNP and have it disabled on the router.
I hardly get one connection to the network now with my controller wallet and it takes forever to establish something.
There must be another problem.

Regards

My configuration is the same as yours and I get the same problem. The problems started about the last week.... Before the last week the client connects ok and fast.

[1714246756]

1714246756

[1714246756]

1714246756

[1714246756]

1714246756

[dsutil]

Sorry, I meant:
The explanation here was, that there was a fork, but I can't believe that this was the reason for connection problems.

I don't believe this either ...

I compile ALL wallets with use_upnp=-  under linux and create the port forwarding by hand in iptables. I never open incoming ports on my windows machine (for obvlious reasons) and of course don't use UPNP and have it disabled on the router.
I hardly get one connection to the network now with my controller wallet and it takes forever to establish something.
There must be another problem.

Regards

My configuration is the same as yours and I get the same problem. The problems started about the last week.... Before the last week the client connects ok and fast.

Also, I have recompiled the client with upnp enabled and I get the same number of connections and slowly connections.

[GoldenEye]

... I get the same number of connections and slowly connections.

.. means the same number as before or nothing (as we)?

[dsutil]

... I get the same number of connections and slowly connections.

.. means the same number as before or nothing (as we)?

Usually none, and sometimes one connection.

[EBK1000]

We are looking into it. I have 9 connections now:



We will consider any issues around peer discovery

[megacryptonstatus]

Trade MOJOCOIN with Megacrypton.com

BTC/MOJO[Current Rate: 0.00000010]: https://live.megacrypton.com/market/66
LTC/MOJO[Current Rate: 0.00000022]: https://live.megacrypton.com/market/67

[drays]

We are looking into it. I have 9 connections now:

We will consider any issues around peer discovery

Does your machine have real IP address, or it is behind NAT router? I suppose it is real IP, right?

This is not about peer discovery. I have the same issue other guys are reporting here, and here is what I can add:

I tried the wallet on two different windows machines on two different locations - the symptoms are the same.

I have put a tremendous amount of "addnode" in my mojocoin.conf, and I would tell - those nodes are indeed being found, but wallet cannot connect to them!
I see the "connection" icon in the bottom-right corner is almost blinking, showing 1 peer, then zero, then again 1 peer, then zero again, and so on.

The peers are being found, but no connection could be established to them. In debug.log on both machines I see big amount of "socket recv error 10054".
Both machines are placed behind routers, which could be the problem, however switching UPNP on/off from the settings did not help.

The output is like this:

Code:

2016-09-08 16:18:26 socket recv error 10054
2016-09-08 16:18:27 socket recv error 10054
2016-09-08 16:18:27 UPnP: ExternalIPAddress = x.x.x.x
2016-09-08 16:18:27 AddLocal(x.x.x.x:22255,3)
2016-09-08 16:18:28 socket recv error 10054
2016-09-08 16:18:29 socket recv error 10054
2016-09-08 16:18:29 UPnP Port Mapping successful.
2016-09-08 16:18:29 socket recv error 10054
2016-09-08 16:18:30 socket recv error 10054
2016-09-08 16:18:31 socket recv error 10054
2016-09-08 16:18:32 socket recv error 10054
2016-09-08 16:18:33 socket recv error 10054
2016-09-08 16:18:34 socket recv error 10054
2016-09-08 16:18:35 socket recv error 10054
2016-09-08 16:18:36 socket recv error 10054
2016-09-08 16:18:36 socket recv error 10054
2016-09-08 16:18:37 socket recv error 10054
2016-09-08 16:18:38 socket recv error 10054
2016-09-08 16:18:39 socket recv error 10054
2016-09-08 16:18:40 socket recv error 10054
2016-09-08 16:18:40 socket recv error 10054
2016-09-08 16:18:41 socket recv error 10054
2016-09-08 16:18:42 socket recv error 10054
2016-09-08 16:18:43 socket recv error 10054
2016-09-08 16:18:44 socket recv error 10054
2016-09-08 16:18:45 socket recv error 10054
2016-09-08 16:18:46 socket recv error 10054
2016-09-08 16:18:47 socket recv error 10054
2016-09-08 16:18:48 socket recv error 10054
2016-09-08 16:18:48 socket recv error 10054
2016-09-08 16:18:49 socket recv error 10054
2016-09-08 16:18:50 socket recv error 10054
2016-09-08 16:18:51 socket recv error 10054
2016-09-08 16:18:52 socket recv error 10054
2016-09-08 16:18:53 socket recv error 10054
2016-09-08 16:18:54 socket recv error 10054
2016-09-08 16:18:54 socket recv error 10054
2016-09-08 16:18:55 socket recv error 10054
2016-09-08 16:18:56 socket recv error 10054
2016-09-08 16:18:57 socket recv error 10054
2016-09-08 16:18:58 socket recv error 10054

BTW, about a week ago the same wallet was synching nicely. This is serious issue, as there are many people already hit by this problem here.

[CryptoHobo]

...
The peers are being found, but no connection could be established to them. In debug.log on both machines I see big amount of "socket recv error 10054".
Both machines are placed behind routers, which could be the problem, however switching UPNP on/off from the settings did not help.
...

after turning upnp on check your routers upnp configuration page, there will be no port assigned. upnp appears to not to be working in the current windows build.

I had the exact same "blinking" and error in debug.log (i also have a ton of addnodes) which is what led me to check my routers upnp page

unfortunately I'm still failing to build the qt on linux seems to be something to do with my libgmp  though. 

[EBK1000]

We are looking into it. I have 9 connections now:

We will consider any issues around peer discovery

Does your machine have real IP address, or it is behind NAT router? I suppose it is real IP, right?

This is not about peer discovery. I have the same issue other guys are reporting here, and here is what I can add:

I tried the wallet on two different windows machines on two different locations - the symptoms are the same.

I have put a tremendous amount of "addnode" in my mojocoin.conf, and I would tell - those nodes are indeed being found, but wallet cannot connect to them!
I see the "connection" icon in the bottom-right corner is almost blinking, showing 1 peer, then zero, then again 1 peer, then zero again, and so on.

The peers are being found, but no connection could be established to them. In debug.log on both machines I see big amount of "socket recv error 10054".
Both machines are placed behind routers, which could be the problem, however switching UPNP on/off from the settings did not help.

The output is like this:

Code:

2016-09-08 16:18:26 socket recv error 10054
2016-09-08 16:18:27 socket recv error 10054
2016-09-08 16:18:27 UPnP: ExternalIPAddress = x.x.x.x
2016-09-08 16:18:27 AddLocal(x.x.x.x:22255,3)
2016-09-08 16:18:28 socket recv error 10054
2016-09-08 16:18:29 socket recv error 10054
2016-09-08 16:18:29 UPnP Port Mapping successful.
2016-09-08 16:18:29 socket recv error 10054
2016-09-08 16:18:30 socket recv error 10054
2016-09-08 16:18:31 socket recv error 10054
2016-09-08 16:18:32 socket recv error 10054
2016-09-08 16:18:33 socket recv error 10054
2016-09-08 16:18:34 socket recv error 10054
2016-09-08 16:18:35 socket recv error 10054
2016-09-08 16:18:36 socket recv error 10054
2016-09-08 16:18:36 socket recv error 10054
2016-09-08 16:18:37 socket recv error 10054
2016-09-08 16:18:38 socket recv error 10054
2016-09-08 16:18:39 socket recv error 10054
2016-09-08 16:18:40 socket recv error 10054
2016-09-08 16:18:40 socket recv error 10054
2016-09-08 16:18:41 socket recv error 10054
2016-09-08 16:18:42 socket recv error 10054
2016-09-08 16:18:43 socket recv error 10054
2016-09-08 16:18:44 socket recv error 10054
2016-09-08 16:18:45 socket recv error 10054
2016-09-08 16:18:46 socket recv error 10054
2016-09-08 16:18:47 socket recv error 10054
2016-09-08 16:18:48 socket recv error 10054
2016-09-08 16:18:48 socket recv error 10054
2016-09-08 16:18:49 socket recv error 10054
2016-09-08 16:18:50 socket recv error 10054
2016-09-08 16:18:51 socket recv error 10054
2016-09-08 16:18:52 socket recv error 10054
2016-09-08 16:18:53 socket recv error 10054
2016-09-08 16:18:54 socket recv error 10054
2016-09-08 16:18:54 socket recv error 10054
2016-09-08 16:18:55 socket recv error 10054
2016-09-08 16:18:56 socket recv error 10054
2016-09-08 16:18:57 socket recv error 10054
2016-09-08 16:18:58 socket recv error 10054

BTW, about a week ago the same wallet was synching nicely. This is serious issue, as there are many people already hit by this problem here.

Yes, real IP I guess, static IP and so on. Ok, I get it now, we will deal with it. I don't know Windows much but will discuss with Limxdev and others.

[FogHorn_LegHorn]

Yes, this fucking sucks. I am losing stakes for over a week now. fuck.

[doriangray]

Yes, this fucking sucks. I am losing stakes for over a week now. fuck.

Well, you're not the only one.

[dsutil]

We are looking into it. I have 9 connections now:

We will consider any issues around peer discovery

Does your machine have real IP address, or it is behind NAT router? I suppose it is real IP, right?

This is not about peer discovery. I have the same issue other guys are reporting here, and here is what I can add:

I tried the wallet on two different windows machines on two different locations - the symptoms are the same.

I have put a tremendous amount of "addnode" in my mojocoin.conf, and I would tell - those nodes are indeed being found, but wallet cannot connect to them!
I see the "connection" icon in the bottom-right corner is almost blinking, showing 1 peer, then zero, then again 1 peer, then zero again, and so on.

The peers are being found, but no connection could be established to them. In debug.log on both machines I see big amount of "socket recv error 10054".
Both machines are placed behind routers, which could be the problem, however switching UPNP on/off from the settings did not help.

The output is like this:

Code:

2016-09-08 16:18:26 socket recv error 10054
2016-09-08 16:18:27 socket recv error 10054
2016-09-08 16:18:27 UPnP: ExternalIPAddress = x.x.x.x
2016-09-08 16:18:27 AddLocal(x.x.x.x:22255,3)
2016-09-08 16:18:28 socket recv error 10054
2016-09-08 16:18:29 socket recv error 10054
2016-09-08 16:18:29 UPnP Port Mapping successful.
2016-09-08 16:18:29 socket recv error 10054
2016-09-08 16:18:30 socket recv error 10054
2016-09-08 16:18:31 socket recv error 10054
2016-09-08 16:18:32 socket recv error 10054
2016-09-08 16:18:33 socket recv error 10054
2016-09-08 16:18:34 socket recv error 10054
2016-09-08 16:18:35 socket recv error 10054
2016-09-08 16:18:36 socket recv error 10054
2016-09-08 16:18:36 socket recv error 10054
2016-09-08 16:18:37 socket recv error 10054
2016-09-08 16:18:38 socket recv error 10054
2016-09-08 16:18:39 socket recv error 10054
2016-09-08 16:18:40 socket recv error 10054
2016-09-08 16:18:40 socket recv error 10054
2016-09-08 16:18:41 socket recv error 10054
2016-09-08 16:18:42 socket recv error 10054
2016-09-08 16:18:43 socket recv error 10054
2016-09-08 16:18:44 socket recv error 10054
2016-09-08 16:18:45 socket recv error 10054
2016-09-08 16:18:46 socket recv error 10054
2016-09-08 16:18:47 socket recv error 10054
2016-09-08 16:18:48 socket recv error 10054
2016-09-08 16:18:48 socket recv error 10054
2016-09-08 16:18:49 socket recv error 10054
2016-09-08 16:18:50 socket recv error 10054
2016-09-08 16:18:51 socket recv error 10054
2016-09-08 16:18:52 socket recv error 10054
2016-09-08 16:18:53 socket recv error 10054
2016-09-08 16:18:54 socket recv error 10054
2016-09-08 16:18:54 socket recv error 10054
2016-09-08 16:18:55 socket recv error 10054
2016-09-08 16:18:56 socket recv error 10054
2016-09-08 16:18:57 socket recv error 10054
2016-09-08 16:18:58 socket recv error 10054

BTW, about a week ago the same wallet was synching nicely. This is serious issue, as there are many people already hit by this problem here.

Yes, real IP I guess, static IP and so on. Ok, I get it now, we will deal with it. I don't know Windows much but will discuss with Limxdev and others.

I have the problem on Windows as well as on Linux. But not in my VPS  with a real public IP.

[Limx Dev]

Yes, this fucking sucks. I am losing stakes for over a week now. fuck.

That is not possible to lose a stake. Can you give me more infos about that?

[kenscho]

my wallet dont connect to a node? i have to add the nodes manually? where i can do that?

[EBK1000]

my wallet dont connect to a node? i have to add the nodes manually? where i can do that?

There are 3 hard coded seed nodes and they should be up and running, I will check later when I'm back on my other computer. You shouldn't have to add nodes manually.

[kenscho]

hmmm very strange..
0 connections installed a new wallet to test = NOK

[drays]

hmmm very strange..
0 connections installed a new wallet to test = NOK

If your PC is placed behind a NAT router (no real IP address), then you have exactly the same problem as everybody else here - you connect to nodes, then disconnect from them immediately. Read the last two pages for more information. This is known problem, devs are looking into it.

[drays]

Yes, this fucking sucks. I am losing stakes for over a week now. fuck.

That is not possible to lose a stake. Can you give me more infos about that?

Christian, he wanted to say: his wallet cannot stake because of this problem, so he is losing money. Its reasonable, but a bit too emotional

[kenscho]

i have only 200 mojo, so dont worry i dont stake atm...
i directly connectet to my router (real IP!) i dont NAT

[cryptospreader]

hmmm very strange..
0 connections installed a new wallet to test = NOK

If your PC is placed behind a NAT router (no real IP address), then you have exactly the same problem as everybody else here - you connect to nodes, then disconnect from them immediately. Read the last two pages for more information. This is known problem, devs are looking into it.

This is an issue that should be given prior importance than any other tasks. If the dev team issue a bounty to this, many people would come and try to find a solution to this.