Login verification flagged security protection

Support Technical Support
1

Upon trying to boot up battle.net, it tried to log me in. FireFox created a new web page with the url of:

://localhost:0/?ST%3DUS-31f36519056b635ba418ca1a9fczf231-82519733&accountId=42649284&flow_type=login_challenge
(I have changed some of the letters and numbers just in case there is any self-identifying information here)

with the message of:
This address is restricted

This address uses a network port which is normally used for purposes other than Web browsing. Firefox has canceled the request for your protection.

I have never had such a thing pop up before. This seems shady. What’s going on here?

EDIT: Closing everything out and trying to boot battle.net up again makes it say my login has expired. Logging in this way, with my password, seems to work and solves the problem. Still though, whatever caused the first issue (which was just an automatic login - I only have to put in my password like once every several months) I think it needs to be addressed because any time a user’s security is exploited, it comes across as very alarming. Not good for the playerbase.

1 Like
2

Sounds like a firewall setting.

3

Less firewall setting and more a Firefox setting.

The launcher pushed an agreement yesterday and it linked to the website; but for Firefox users (not all), it did it accessing the same port as the launcher uses - which isn’t normally used for web-browsing, and it flagged it as a security risk as a precaution.

It did the same thing to me, the agreement popped up and clicking on it took me to the restricted page OP saw, I saw at that point I was logged out of the launcher during the process, reopened the launcher - relogged in for the first time in 6 months, and all was well.

But it’s not a security risk at all, nor anything really on Blizzard’s end. It’s a setting on your internet browser that did it.

4 Likes
4

I logged in without issue at 6:00 am. Just now I tried to log in and got a window asking me to review something (TOS update?) and sent me to that dead page you found.

I had to type in my password to actually log in.

1 Like
5

Yes the agreement was better , but worse overall.
It called a string to the localhost.
I was not aware that blizzard was running a web server on my computer.

Maybe they are looking for botters…
I saved the string…

6

The link to the EULA was messed up.

This happened to me in Chrome, as well.

For anyone having issues, just close the browser. If Bnet won’t load, exit and restart it. You may have to log in again. But everything is fine.

5 Likes
7

Yes, this happened to me as well. Also using Firefox. Closed the tab and the battle.net launcher, and had to re-login when the launcher started up again. I was having the issue a few weeks ago with the launcher logging me out over and over and over, and I wondered if this was related in any way.

8

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.