Rhubarb Posted September 28, 2016 Share Posted September 28, 2016 Ity looks like the hamsters have gone on strike again. No doubt we'll get the usual sobs, wailing and gnashing of teeth because scores aren't being upgraded. As before, bitcomet points don't pay for the beer (or give you super abilities in any of the online games) so it's not a big deal really. You can still upload and download (which is what the app is for really). It will be back when it's back. 2 Link to comment Share on other sites More sharing options...
The UnUsual Suspect Posted September 29, 2016 Share Posted September 29, 2016 Thank you, we get so many posts every time the website is down and no every time we have to post the same replies. I also tend to get my inbox filled with messages even though support isn't offered in private messages. 1 Link to comment Share on other sites More sharing options...
Rhubarb Posted October 23, 2016 Author Share Posted October 23, 2016 Stand by for another load - it looks like it went down round 0600 GMT again I'll get sovereign yet - it's rigged bigly by corrupt media, opinion polls, emmys and that wall :blink: :rolleyes: ^_^ :o Link to comment Share on other sites More sharing options...
The UnUsual Suspect Posted October 23, 2016 Share Posted October 23, 2016 You win the internet for a day... thanks for making me laugh Link to comment Share on other sites More sharing options...
Spec-V Posted October 24, 2016 Share Posted October 24, 2016 Yes server down again, unable to log in. Link to comment Share on other sites More sharing options...
Rhubarb Posted November 6, 2016 Author Share Posted November 6, 2016 And once more on to the breach: Internal Server Error SoapClient::SoapClient(http://member.bitcomet.com/webservice/wsdl): failed to open stream: Connection refused An internal error occurred while the Web server was processing your request. Please contact the webmaster to report this problem. Thank you. Link to comment Share on other sites More sharing options...
Rhubarb Posted November 6, 2016 Author Share Posted November 6, 2016 the seb server might be down but points are still accumulating (no panicing please_ 1 Link to comment Share on other sites More sharing options...
czechmate12 Posted November 7, 2016 Share Posted November 7, 2016 Can log in, but displays "Port Detection Failed". Uploading, Downloading and points mysteriously unaffected. Recommend using the Ninja Hamster Squad. 1 Link to comment Share on other sites More sharing options...
gawdfather Posted November 8, 2016 Share Posted November 8, 2016 Showing "Port Detection Failed" Some Torrents are dead slow, even though they have a very good health Link to comment Share on other sites More sharing options...
Rhubarb Posted November 8, 2016 Author Share Posted November 8, 2016 (edited) Port detection failure is normally down to your computer setup and not the server. It could also be your ISP blocking that port Check that: (a) your firewall isn't blocking it and (b ) that you have port forwarding setup correctly on your router. That usually means allocating a fixed ip on the computer with the router defined as a gateway (manual settings in network properties). The router has to be set to allow the appropriate port through to the computer with the specified IP address. Pick a random port somewhere in the 14,000 series which isn't normally used Edited November 8, 2016 by Rhubarbfian (see edit history) Link to comment Share on other sites More sharing options...
nanfangbuddha Posted November 9, 2016 Share Posted November 9, 2016 my port has also failed Link to comment Share on other sites More sharing options...
gawdfather Posted November 9, 2016 Share Posted November 9, 2016 Been using Bitcomet for years even before i made an ID on it Bitcomet is not blocked by my Firewall Port Forwarding is done properly Every other torrent client is working just fine Still there is a Port Detection Failed message on Bitcomet I guess its a problem from Bitcomet's side Link to comment Share on other sites More sharing options...
qweerwf Posted November 9, 2016 Share Posted November 9, 2016 I, too, after you upgrade to Version 1.43 was the show "Port Detection Failed" Link to comment Share on other sites More sharing options...
Rhubarb Posted November 10, 2016 Author Share Posted November 10, 2016 Ports are nothing to do with the server errors though. It could be a bug in 1.43. Did you try rolling back to 1.42? Link to comment Share on other sites More sharing options...
gawdfather Posted November 10, 2016 Share Posted November 10, 2016 Rolled back Bitcomet to 1.42, still getting the same problem. Link to comment Share on other sites More sharing options...
Rhubarb Posted November 10, 2016 Author Share Posted November 10, 2016 As I said, this thread was on server problems. Bugs are in a different forum (and there is a thread on the port problem here: http://www.cometforums.com/topic/12799826-port-detection-constantly-fails/ ) Link to comment Share on other sites More sharing options...
Rhubarb Posted November 10, 2016 Author Share Posted November 10, 2016 This thing is going crazy - my points go up but my ranking goes backwards - it's all a consipracy I tell ya :ph34r: :lol: :rolleyes: :unsure: 1 Link to comment Share on other sites More sharing options...
The UnUsual Suspect Posted November 11, 2016 Share Posted November 11, 2016 If the light is yellow, that means you contacted our server but were blocked from receiving an unrelated connection back from the server to test your port and that means you are blocked, if the light is grey, it means it could not connect our server to request the test so it could have nothing to do with you, nor any problem, just a down or busy server. Coding was added to bitcomet so that when an active torrent receives a remote connection, the light will change to green in case there was something preventing the active test. Try running a popular torrent and see if it turns green, and you can also manually retest the port using the context menu with a "right click". Link to comment Share on other sites More sharing options...
mehrdadmms Posted November 14, 2016 Share Posted November 14, 2016 Since 2 days ago when i use the client it says port detection failed. Is the server down at this time?? Link to comment Share on other sites More sharing options...
The UnUsual Suspect Posted November 14, 2016 Share Posted November 14, 2016 I just confirmed it's working perfectly for me, active port detection changed light from grey to green in a few seconds and comet ID login also completed quickly. If your router's uPnP is slow, sometimes that causes the test to time out or fail, you can try to "right click" and select "test again", or once bitcomet detects remote connections on an active torrent the secondary passive test should turn the light to green. Link to comment Share on other sites More sharing options...
nanfangbuddha Posted November 30, 2016 Share Posted November 30, 2016 it looks like the hamster is tired Link to comment Share on other sites More sharing options...
The UnUsual Suspect Posted November 30, 2016 Share Posted November 30, 2016 Yes, I noticed the outage too, if it's not fixed by tomorrow I'll try to contact someone to fix it. Link to comment Share on other sites More sharing options...
AaronT69 Posted December 8, 2016 Share Posted December 8, 2016 i am unable to sign in today, do you know if there is an outage again? Link to comment Share on other sites More sharing options...
Rhubarb Posted December 8, 2016 Author Share Posted December 8, 2016 Looks that way - I think they need fresh hamsters. I also noticed that the 'personal score' on the main website is conspicuous by its absence ;) On a slightly different topic - for a while some reason I wasn't connect to the forum via the client and have to manually open it in the browser. (the client kept giving a '404' error). I'm assuming somebody has been working on the servers Link to comment Share on other sites More sharing options...
Rhubarb Posted December 8, 2016 Author Share Posted December 8, 2016 (edited) .Actually it's not the usual unresponsive servber message but an inability to sign in. It keeps changing to 'sign in now' where p[revious failures said that it couldn't connect and would retry. The 'retry' message is missing this time. Edited December 8, 2016 by Rhubarbfian replacement for double post (see edit history) Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now