I used BrowserLab all last night...worked great. Then it just stopped working and I keep getting the following message:
"We have experienced a problem connecting to our servers. Please check your Internet connection and try again."
The fact I'm sending this message is proof my internet connection is working. I've deleted my cookies...thought that might be the problem. No such luck. Any suggestions or are you just down because of a software upgrade?
I am experiencing this as well. It started yesterday after working fine for about an hour and continues today. I've tried logging in with three different browsers and through Dreamweaver CS5.5 as well. I've also tried rebooting and clearing the cache as has been suggested in other postings. But nothing has worked...
Are either of you still seeing this? I haven't and still don't, though it's possible some of the back end services we rely on may have had some intermittent issues that could cause this error message to be shown.
Yes I am still seeing it. I haven't been able to log on since I first encountered it on Friday. I've tried going through Firefox, Safari and Dreamweaver itself and every time it returns that message...
I'm having this issue too.
I try and load it and I get the laoding screen for a bit, then it is replaced with a message saying
"We have experienced an error with our servers, please try again. Code: 500"
Hmm, we are unable to repro it here any longer. At this point I think we're going to need a lot more information about your machine configuration and steps to reproduce it. I'd ask all of you who are seeing this issue to please respond with information to all the following questions:
I've been getting the error for a few hours. I was in the middle of testing a site, it was working, and then suddenly - "We have experienced an error with our servers, please try again. Code:500"
Thanks for the info and sorry that you're still having this issue. If anyone else who is having this issue can chime in with their information it could be helpful.
FYI, at this point we are completely unable to repro the issue on our side, so unfortunately we're no closer to having a solution. We are going to do a complete reboot of all our environments this afternoon, which may help, but additionally I'd like to work closely with one or more of you to dig deeper into the issue.
To start with, can anyone who is experiencing this issue please try it again and email me the following information so we can dig into our server logs:
If that doesn't help us, I'd like to call one or more of you directly so we can screenshare, repro the issue on your side and simultaneously look into the logs.
Glad to hear it. After quite a bit of investigation we discovered that a number of user accounts had gotten into a bad state and was the root cause of the 500 errors. None of our test accounts were in that bad state which is why we were unable to repro the issue. Apologies to the users who got hit by this and thanks to everyone who gave us the info we needed to be able to track this down. We are looking into making a fix to try to prevent this situation in the future.
I signed up for an Adobe membership about 3 weeks ago specifically so I could make use of Browserlab. I experienced the same problem described by others ("We have experienced an error with our servers, please try again. Code:500"), but waited to see if it would be resolved soon. Has a solution been found yet?
This sounds like an excellent service, but I have been encountering this problem from the very first time I tried to access Browserlab. I would be happy to provide data if you are still investigating.
Hmm, it may or may not be the same issue. Can you please send the AdobeID you're logging into BrowserLab with directly to me: mrausch (at) adobe (dot) com and we'll check to see what's going on. Also, try it again and let me know the time you received the error message and what time zone you're in so we can check the error logs around that time.
Europe, Middle East and Africa