Can't Log In "Not allowed to use restricted network port "

When I select > guest > log in > " Immortal " wants to use “battle.net” to sign in > continue > gmail account > Then it says " Safari can;t open the page " " The error was " Not allowed to use restricted network port. " When I hit refresh as suggested by a user it says " Unable to authenticate with Battle.net "
I’ve tried the trouble shoots suggested by other players, none of them have worked
Was hoping to play this evening, guess not
In addition to a description of the bug you are reporting, please provide:

Device Type: Iphone
Device Model: 13 Pro
Device Operating System: IOS 18.6
Diablo Immortal App Version: Most Recent

1 Like

Apparently it’s because you’re on a beta release of iOS…

1 Like

i got this a couple of times maybe. tapping the refresh button did it for me.

2 Likes

Refresh button where?

1 Like

There’s a pinned, bannered announcement from Blizzard which appears at the top of every single forum until you’ve visited / dismissed it…

1 Like

Good! Resolve by this shooting.

Refresh button in safari browser

https://imgur.com/a/4uFgP1h

Embedding so folks can see easily…

thanks. i don’t know how to embed :slight_smile:

Whether players can embed pictures or clickable hyperlinks is based on their Trust Level within the Discourse software back-end the forums run on…

…the reason I can do it is that I’m at Trust Level 3.

I use it when I see helpful stuff like yours that needs to be more easily seen.

Me pasa lo mismo como se puede arreglar

Why I couldn’t see the refresh button on my ios 26

This isn’t a beta problem. I’m running this on a GA release; iPad OS 18.6 build 22G86 and I get this error. IOS 18 was released in 2024, it’s definitely NOT BETA.

This looks like someone implemented, either by mistake or on purpose, a cross protocol scripting attack. See the cert knowledge base for vulnerability #476267 for further details as I can’t post the link directly.

Blizzard: please examine your site and determine if this on purpose or malicious. If purposefully implemented then you should update your code and fix your vulnerability scanners to catch this in your CD pipeline before you roll releases out the door.

Yes you can, and the instructions for how to do so were already provided in Post 10 of this thread.

Refresh worked for me