White screen on iOS 18.4 [Fixed]

[Rsurect]

Since yesterday morning I only get a white page whenever trying to access Mangadex on mobile. Tried updating my phone (iOS 18.4), clearing my cache, different browsers and opening in incognito but nothing works. The site works fine on my laptop.

Is this a known issue or is it just me? Anything I can try?

 

[BraveDude8]

Disable your content blockers and check if you can access https://api.mangadex.org/docs/

 

[Rsurect]

They’re off and I can access the api but it still doesn’t work.

 

[CamoBrie]

I have exactly the same, it’s been happening for a couple days now already

 

[BraveDude8]

I don't have a modern iOS device to test with but my old iPad running 16.7.8 is working great, so it's not Safari as a whole.

 

[Furcube]

I have white screen on pc firefox and chrome. Not every time but more often in firefox.
No adblockers, tested using clean icognito
When I have this problem I have this error in console:
DOMException: Node.insertBefore: Child to insert before is not a child of this node NuxtJS 53 insert Le Le resolve O3 process m K run runIfDirty _n U0 promise callback*L0 tl scheduler trigger Ya Vt set i _n Ur registerDep promise callback*registerDep re Q m z O k m K run J re Q m z O k m z O k m z O k m K run J re mchunk-pg-auth-user-connections.NAMBibcL.js:14:2009

 

[kn4ll]

This happened to me to, the odd thing is that chrome on my iphone also doesn't work.

 

[vauneg]

Yes, I'm seeing the same error as Furcube. I think it's a failed request to https://uploads.mangadex.org/fools2025/banners.json
which breaks everything and leaves a blank page. I reloaded that json file a couple of times, most failed with 503 but some succeeded. For me the successful ones had http header

via: HTTP/2.0 EU-CENTRAL-N1x2

and the failed ones had

via: HTTP/2.0 EU-CENTRAL-N2x1

 

[HelperHand]

Well I don't suffer the issue (Android and from Latam), and not totally sure if this is the same issue from OP but is related to Vauneg comment, in the Mangadex reddit sub, there is a German user sharing screen captures of failed CORS request also from EU-CENTRAL-N2x1

 

[vauneg]

That looks like the same issue, I also see the CORS error. The actual cause is the 503 response from the server, it results in the CORS error as well, but it's not a CORS issue.

And to fill in the info asked of OP, I'm seeing this on desktop firefox and chromium. I've tried disabling adblock and clearing all cookies/cache/localstorage. As far as I can tell the requests that fail or succeed are identical, only difference is the server it's sent to and the response.

 

[BraveDude8]

Any further issues in the last hour? Should hopefully be fixed with a hard refresh/potentially cache clear on the affected devices.

 

[vauneg]

Seems to be fixed for me, thanks.