IMAGES NOT LOADING

[shiho]

Is it just me or the images aren't loading properly? I always have to refresh the page just for them to load which doesn't happen before.

 

[Chaos_Knight]

< From SEA

< No problem reading recently uploaded chapters.

< Absolutely cannot read old chapters. How old? it starts from days old.

Is the server getting crowded or something?

 

[shiho]

@Chaos_Knight
It's for the recently uploaded chapters. They are there but I have to annoyingly refresh for each page to actually load.

 

[loknarj]

If a chapter is older than 12 hours, there is a very high chance of not being able to view any pages for me.
If it's within the 12 hour window, there is a low chance of not being able to view any pages.

This affects me on Windows/Android Chrome and Edge.

 

[schlo]

and the failure is quick, not taking time like the slow load problems.

 

[shiho]

@loknarj
I'm reading older series. I've tried it on Windows, Chrome, Mac, Safari and they give the same result.

 

[Holo]

Link these chapters so we can check

 

[shiho]

@Holo
I'm not linking chapters but series because basically all chapters are like that. Once the page finished loading, some photos aren't loading so I have to refresh for each image to load.

The Monster Duchess and Contract Princess
The Evil Lady Will Change
The Villainess Lives Twice
Lady Baby
The Youngest Princess

And many more. Basically they're all like that.

 

[burmn123]

For me, if Im logged no manga load, but if I try whithout login, I can read any series, new or old.

 

[fuzzyk]

All image load errors are reported to MangaDex, automatically.

The Problem is that the reader apparently cannot yet switch the MD@H node it tries to connect to on-the-fly. You need to reload the page.

 

[Holo]

@AbyssalMonkey

Thanks for letting us know. MD@H has been around for a few weeks only, it's still in its infancy. H@H has had years of development, so of course they are going to be ahead of us, lol.

Rest assured that the option to switch it off will remain until all of these problems have been ironed out.

 

[bysantti]

@AbyssalMonkey
thank you

 

[marumichin]

Is anyone still encountering this issue till now? For me, images dont load at all even if the chapters are recent. Sometimes I just wait for sites like mangakakalot to post them bc I dont have to wait for so long just for the images to load. I'd really like to stay with mangadex but this is really bothersome.

 

[comedyxtragedy]

I still have this problems.
I think the whole website becomes really slow for me.
I'm reading from phone.
Changing browser didn't work.
Is it server problem again? It is similar with the problems in the past.

Update: Apparently, this only happens during busy time since every morning, the website is fast as usual

 

[moel]

Same as comedyxtragedy
Mine are slow wheter using vpn or not, it not this slow yesterday.

 

[MrDraXuz]

I'm also having the same issue. I'm able to read 1 chapter, but when I go to the next one it doesn't load the images, and when I go back to the chapter that I just read, it won't load those images either. I've tried refreshing, and restarting my browser since I thought it might just be my browser, but neither seem to do anything to help the issue. This has happened for both old chapter and new chapters. It's been happening for a few days now, but it suddenly gotten much worse today. The weird thing is, it just kinda fixes itself after leaving it alone and coming back to it after awhile.

 

[uchiha_madao]

turning MDatHome doesn't help for me, the images still fail to load. any other workaround?

 

[Horolus]

It happens a lot lately, but on specific mangas as when I tried testing on others in the same time, it worked as it should have. I tried changing the options, switching to another image server and to compressed images. I feel like it improved a bit but that might be my imagination. If a page loads for a little too long (5+seconds), just skip it. I never had three pages not working in a row so far. Also, frequently refresh the page.

 

[Muckamuck]

turning on the legacy reader seems to be working for me

 

[mmerijn]

Same issue here.