WAN IP can not be detected suddenly

WAN IP can not be detected suddenly. I have tried version 1.4 and 1.43.

/monthly_11_2016/post-177151-0-63917700-1478792954.jpg" rel=“”>

WAN IP can not be detected suddenly.jpg

I have the same problem

WAN IP can not be detected suddenly.

Can you try to give a LOT more information, please? (This is like saying “Suddenly, my car won’t work…”)

I have the same problem

Please read the same post, right above this one… we need the same thing…information…

ok ok, here`s some more info; we log in to bitcomet, and then it says "Port Detction Failed# over and over again, allthoug I have made firewall exeption to Bitcomet. What more info do you need?

I made a post about this like 4 days ago. Still happening.

I feel I am not alone when I view these posts.

I also have the same problem on 6th Nov 16 until now. Run check again or remapping does not help.

(Normally it will go green within a minute after run open the Bitcomet).

After spent days to find out what went wrong on my machine then i gave up.

Anyway I notice that it goes green when I add new torrents and it starts downloading.

And it stays green all day.

Ooops sorry to give details information:

I used version 1.42 and it ran well until the problem is noticed.

Change to version 1.43 does not resolve the problem.

Then I continue to use v 1.43 until now and I found it goes green when I add new torrents and torrent items start running.

I feel I am not alone when I view these posts.

I also have the same problem on 6th Nov 16 until now. Run check again or remapping does not help.

(Normally it will go green within a minute after run open the Bitcomet).

After spent days to find out what went wrong on my machine then i gave up.

Anyway I notice that it goes green when I add new torrents and it starts downloading.

And it stays green all day.

I’ve explained the way port checking works many times and don’t have time to retype it tonight, so the short answer is just ignore it.