[atlantajon]

Is there some issue with bbo? I have been having issues logging on for the past few days. I haven't changed anything on my MACBook... but can't seem to log in. The left hand ad window seems to load fine, but when I enter my login info...all I get is the rotating lines telling me that it is trying to log on...then after about a minute... I get a connection lost message. Anyone know what is up??

[atlantajon]

I am using a MACbook, and using Google chrome as the browser....it has always worked before.

[diana_eva]

Try this link:

http://www.bridgebas...t.php?port=3336

And if that one doesn't work, this:

http://www.bridgebas...ent.php?port=80

I don't know the technicalities, one of the programmers will probably post later to explain what's going on - but meanwhile see if any of those links helps.

[atlantajon]

thanks, first link didn't work.... but second one did.

[barmar]

We haven't changed anything on our end, it sounds like a change in your firewall.
Last week we tried changing the default port to 80, but that caused problems for many people so we changed it back. An upcoming revision will automatically try port 80 if port 3336 doesn't work.

[kayin801]

I am having the same issues. I am able to log in via my friend's computer (nearly identical to mine, MacBook) on the same wifi network using the same browser (Chrome). Other browsers (Safari) don't work, and neither of the links provided above works. At least I'm glad this is a known issue.

FWIW I can also successfully log in on the app using the wifi network available as well.

[barmar]

kayin801, on 2014-June-29, 09:23, said:

I am having the same issues. I am able to log in via my friend's computer (nearly identical to mine, MacBook) on the same wifi network using the same browser (Chrome). Other browsers (Safari) don't work, and neither of the links provided above works. At least I'm glad this is a known issue.

Yours is not a known issue. If neither of the links works, then it's something completely different, and the upcoming change won't help you (it just automates trying both links).

It sounds like something on your MacBook is blocking you, but I'm not sure what it would be. Could you provide more details about what happens when you try to login?

[kayin801]

barmar, on 2014-June-30, 10:17, said:

Yours is not a known issue. If neither of the links works, then it's something completely different, and the upcoming change won't help you (it just automates trying both links).

It sounds like something on your MacBook is blocking you, but I'm not sure what it would be. Could you provide more details about what happens when you try to login?

I go to bridgebase.com, click on the "Click to Play or Watch Bridge" link, the normal page pops up, I enter my user name and password, and click "Log In." The page thinks for maybe 10 seconds, and then returns me to the login page and displays a message that says "Connection lost."

This started only a few days ago, I'd guess? I also tried an old user name and I couldn't login on that either.

[barmar]

I don't see a login by kayin801 in almost a year and a half. Are you using a different username?

[kayin801]

barmar, on 2014-July-01, 09:04, said:

I don't see a login by kayin801 in almost a year and a half. Are you using a different username?

Yes, I'm using East4Evil.

I'm able to log in on another computer I own, so for now I have access, but it'd be nice to be able to log in on my primary computer. I assume it's an issue with this computer specifically but I don't have the slightest idea what the problem is.

[barmar]

It's a Mac, right? Open the Console application, and see if there are any messages added when you try to login.

[kayin801]

The following two lines showed up in Console upon the "Connection lost" message appearing:

7/1/14 11:25:03.364 AM com.apple.SecurityServer[24]: Killing auth hosts
7/1/14 11:25:03.364 AM com.apple.SecurityServer[24]: Session 100020 destroyed

Though if I try to log in repeatedly it doesn't repeat those lines.

[barmar]

I'm not sure what those messages mean. I've tried googling them, but the problem is that they often show up in the middle of logs that people post related to other things, so there are lots of false hits.

But it seems to me like it's related to the OS X firewall. Try turning it off and see if that helps. If you're behind a router that performs NAT (i.e. any home broadband router), you're generally pretty safe, as the only incoming connections that will occur are those that are configured in the router's port forwarding.

[kayin801]

Firewall is off and has been. I'm scanning through my router settings too to see if there's anything I can find there, but given other computers work I suspect that's not it.

[kayin801]

I'll also mention that I can't think of any change that I made to my computer when this became an issue. I was able to log on perfectly normally before this. It just seems like it coincided with the original poster's problems.

[barmar]

Open a Terminal window, and try telnet v2proxysl1.bridgebase.com 3336. Does it say Connected to v2proxysl1.bridgebase.com or does it just hang on the Trying... line?

If it connect, you can get out of it by typing Control-] followed by quit and Enter.

[kayin801]

me:~ melaptop$ telnet v2proxysl1.bridgebase.com 3336
Trying 192.155.229.163...
Connected to v2proxysl1.bridgebase.com.
Escape character is '^]'.

So it looks like it connected

[barmar]

Sorry, I'm running out of ideas. Your Mac is able to connect to our server, so I can't think of why the application would be failing.

[kayin801]

Thanks for trying

Is there a way to clear all recognition that my computer has ever interacted with BBO or is that only through cookies?

[kayin801]

So this is going to sound stupid, but I just managed to get my computer to log on. I think it had to do with my Sophos Antivirus software using the ports (It was spamming port 80 and had two hits on 3336). I disabled all its functions and tried to log on and... voila. The weird part to this is that I'd had the software for ages and it was never a problem before. I have no idea why it suddenly became an issue. An update on their end, perhaps?