I’ve tried all the suggested steps — including uninstalling and reinstalling the app, resetting my router, and even switching devices — but the same issue still occurs.
Currently, the game only works on my iPad running iOS 18.5.
I also tested installing the game on my friend’s iPhone with iOS 18.6, and it redirected to Safari with the exact same problem, showing an error related to “hard_account_login” via the blizzard-anbs://localhost:0 link.
It seems this issue only affects devices running iOS 18.6. Please let me know if there’s a fix or upcoming update. Thanks again!
1 Like
Found a solution. Just hit refresh at the top right corner. Icons: Refresh | Share | Safari
8 Likes
I have the same issue iOS 26 beta 5,
I was able to login into the app by refreshing multiple time, but I can’t sign in from Diablo Immortal. I’m getting:
Safari:
“Not allowed to use restricted network port”. Error
chrome:
This site can’t be reached
The webpage at blizzard-anbs://localhost:0/?ST=AfKyCz4U8E8cP5t2lEzfBrULBPyGHWCEHXpWbCeERAWwxfOIvKKBlsvFhnTYDiuVZ0Ix7Au_2yhV89kmGXlkOwQ&STT=enc&accountId=837941394&flowTrackingId=&flow_type=hard_account_login might be temporarily down or it may have moved permanently to a new web address.
ERR_FAILED
Please help!
EDIT/UPDATE:
After trying several dozen of times, the webview with the error showed finally a refresh page icon, I pressed it and was able to sign in.
So, my solution was, waiting until the refresh icon appeared and hit refresh after the error page is shown.
1 Like
Hi tried your trick and it work too , i’m also using iso 18.6 . but i had to do it a couple of time but it worked ! thanks
At my phone the refresh symbol didnt appear at any time, am on iOS 26 beta 5 any recomendation?
I hit reload on the error screen in Safari, and it instantly logged me in to the game. Nice find, jlelz. Thanks!
1 Like
I found the answer. When it takes you to the safari browser and you get the error hit the reload button next to the address.
Ok, I figured it out on iOS 26. You need to refresh the error screen on safari. However, there is no refresh button on the iOS 26 screen. There is a back arrow. Push the back arrow to the previous screen then push the forward arrow. This serves as a refresh so to speak. Worked like a charm.
12 Likes
click refresh on ur page after it gives u this prompt and it will log u in.
1 Like
Updated to the latest iOS 26 beta last night and no matter what I try, I keep getting:
Safari can’t open the page.
The error was: “Not allowed to use restricted network port”
No refresh button and hitting back refers me to the login page. Grrrr.
Update: after several goes with the back and forward buttons and a crash, this workaround has done the trick.
2 Likes
The same, with the latest beta I also do not find a way to reload the page
Praise me guys. 
I figured it out. Here told me to press the refresh button, but no matter how many times I tried, it just wouldn’t appear, so I struggled for two hours…
Then I clicked the back button in the top left to go back to the login page, and “without logging in”, pressed the forward button again — and it connected.
Man, that was such a hassle. 100%. Fxxx
3 Likes
This just happened to me. I already had the IOS beta 26 version on my iPhone, but I was using the “developer beta.” Once I switched to the public beta, the error was gone. Now it’s working fine; I was able to use it to log in and reply to your post.
Switch to the public beta, it fixed this error for me.
The refresh worked for a while I’m also on 18.6 I get authenticator request and then hit the refresh button and it attempts to sign in and goes back to game screen and says you have been disconnected do u wanna reconnect and I hit ok and it’s the same Circle of death!! Blizzard pisses me off with no response or work around!!!
Using public beta still telling me disconnected after signing in and authenticating
You are a genius!!! It worked!
It actually worked thanks, figured out where tf the refresh button is xD
This helped! I had the same issue today. Thanks so much. 
After receiving this error repeatedly, all I had to do was refresh the webpage with the error and it logged me right in. I don’t understand how that resolved it but I got back into my battle.net account.