POWBlock

[DunkmasterKyouko]

Is this new? I never saw this before but all of a sudden every pageload is getting a bot check. Even worse, more than half the time it doesn't actually work properly, so the page fails the load and gets stuck with part of the ui loaded and no pages loading until I refresh and then get a bot check. I had to try to load the next chapter of a manga five times before it actually successfully got there instead of failing to load and then going back to the previous chapter after the bot check. Also I had to try multiple times to post this thread because it kept running into an error which I can only assume was another failed bot check attempt.

 

[Angry_Panda]

On desktop, hard refresh the page (control-F5).

On mobile, try a long hold of the refresh button, and if that doesn't work, clear the cache and cookies for mangadex.org.

 

[Greenfrost]

I'm having the same issue. I know it's not my VPN because I turned it off. I'm also struggling just to make a post here.

 

[shinya78]

I'm only getting the initial check when first visiting the site, every other page loads perfectly fine with no additional checks.

This is on firefox, with no prior cache/cookies for mangadex.org before visiting the site.

 

[Angry_Panda]

I'm only getting the initial check when first visiting the site, every other page loads perfectly fine with no additional checks.

Right - you should only be seeing the check once, not repeatedly. If it keeps coming up, and the hard refresh doesn't work, clear your cache/cookies for mangadex.org .

 

[Mangamoz]

I get it everytime

 

[shinya78]

I get it everytime

Got any extensions that affects cookies?
Have you tried restarting the browser after clearing cache/cookies for mangadex.org?

---

After the initial check for the current browser session, I don't get another check even after clearing cache and cookies. I only get the initial check again when I close the browser and then start another session.

edit: After clearing cache and cookies "the normal way", while it doesn't give me a re-challenge upon refreshing a page, the contents that I can see are only up until the point I cleared them. (Example: New forum posts won't show up for me beyond the posts made by the time I cleared the cookies.)

However, deleting the cookies from Firefox's web dev tools, specifically Storage Inspector (Shift+F9), does give me a re-challenge upon refresh and it'll show me the latest posts without having to restart the browser.

 

[shago00]

Got any extensions that affects cookies?
Have you tried restarting the browser after clearing cache/cookies for mangadex.org?

After the initial check for the current browser session, I don't get another check even after clearing cache and cookies. I only get the initial check again when I close the browser and then start another session.

I did all of that and still have the problem.

 

[BlueRoguesDev]

I'm one of Powblock's developers. Nice to meet you. One of my people poked me that our program turned up here today.

I don't know how MD built their controller, but make sure you aren't using extreme privacy settings or plugins that do things like switch your user-agent or VPN IP per request. Powblock's loop is broadly very straightforward, and other than IP address changes 99% of all issues come from browser settings and privacy plugins. They might also have an abuse throttle set that POWs you again if you open too many tabs to the site or make too many requests at once.

"Enter site, see POWBlock once, browse freely for a long time" is exactly how it should go.

 

[shinya78]

I did all of that and still have the problem.

To be clear, your problem is that the bot check fails to complete, or that it gives the check a lot?

If check fails to complete:

• Check for privacy extensions
• Set privacy settings to standard protection
• Try a different browser if you're using Brave
• Test in Private Browsing
• Test in a fresh/clean profile

If getting the check repeatedly:

• Check your IP if it changes often, token could be bound to your IP
• Check/clear cookies

 

[shago00]

To be clear, your problem is that the bot check fails to complete, or that it gives the check a lot?

If check fails to complete:

• Check for privacy extensions
• Set privacy settings to standard protection
• Try a different browser if you're using Brave
• Test in Private Browsing
• Test in a fresh/clean profile

If getting the check repeatedly:

• Check your IP if it changes often, token could be bound to your IP
• Check/clear cookies

I think it's the IP because I noticed that when I use my phone's data I don't have any problems. Also how do I check the IP?

 

[Rockdrop]

Welcome to dynamic IP / CGNAT hell. I can imagine most filthy pirates like me don't have a static IP bound to their names.

 

[Claith]

... So having this issue too.

The site seems to work well in a private tab with stronger protections, but not in a general one...

Okay, it seems to have sorted itself out. This is after deleting all the cache and cookies, which did nothing aside trouble me with the login. Hard refreshes. Closed over 40 tabs (doubt they were loaded, but phone applications are notorious for not giving control to their user). The problem stayed; couldn't even post a message on the forum.

What seemed to help was restarting the Firefox browser. Was about to force stop it, because the phone didn't actually close it initially, but it did what I wanted eventually.

Edit: The problem isn't completely resolved. Get rechecked between reading chapters, but not immediately. So, my case goes:

Spoiler

1. Read a chapter, get to the end

2. expect the next chapter but get a page with non-loading elements

3. refresh the page

4. get checked again

5. get placed back at the last page of the prior chapter

6. Transition to next chapter works.

7. Read to the end, repeat.


Time frame issue? Haven't tried changing chapters quickly. Had to refresh to post this.

Don't think it matters as it didn't till yesterday, but on mobile data. No option otherwise for me for the foreseeable future.

 

[shinya78]

I think it's the IP because I noticed that when I use my phone's data I don't have any problems. Also how do I check the IP?

On Windows?
Open Command Prompt, it DOES NOT need to be run as admin, and type:

ipconfig /all

Look for "DHCP Enabled", if it says "Yes", you're on dynamic IP.

---

On Linux?
Open Terminal, and type:

ip a

Look for "static" or "dynamic"

---

Even with dynamic IP, you really shouldn't be getting the checks/challenges every now and again unless your IP changes every 5 minutes or something. If you're running with a dynamic IP, then maybe your current IP is the issue.

 

[77BLc9JwJGpLVARkamJx]

You need to check your external ip using "whatsyourip" site, you can google for them. The ipconfig /all command is just your local network most of the time and wont show you your real ip mangadex server is seeing.

 

[BlueRoguesDev]

A couple options MD could use in their controller if too many people have an issue, would be to regex off the last IP section before hashing, and enable -loose mode. Then only big IP swings would trigger rechallenges. They might also try a fingerprint instead of IP. As a last resort they can also hash something static like UserAgent, and configure the cookie with a signature and short expiry time using the Unix Epoch or parsed timestamp method. Whatever is easiest for their server config. Powblock is completely adjustable just based on whatever your server software lets you do.

 

[Samhill]

On Windows?
Open Command Prompt, it DOES NOT need to be run as admin, and type:

ipconfig /all

Look for "DHCP Enabled", if it says "Yes", you're on dynamic IP.

---

On Linux?
Open Terminal, and type:

ip a

Look for "static" or "dynamic"

---

Even with dynamic IP, you really shouldn't be getting the checks/challenges every now and again unless your IP changes every 5 minutes or something. If you're running with a dynamic IP, then maybe your current IP is the issue.

Under Unbuntu/Mint it's

inxi -i

From my machine I get:

inxi -i
Network:
  Device-1: Intel Wi-Fi 6 AX201 driver: iwlwifi
  IF: [redacted] state: up mac: [redacted]
  IP v4: [redacted] type: dynamic noprefixroute scope: global
  IP v6: [redacted] type: noprefixroute scope: link
  WAN IP: [redacted]

Minus all of the redacted of course. The WAN IP is my external IP address and the IPv4 is my router address. I don't know what IF is, but I redacted it out of caution.

 

[Angry_Panda]

Summary of where we're at now, with a couple updates from what I've seen on the Discord this morning (US time):

1. You need cookies enabled. The one in use for this specific utility is 'MD-Edge-ID'. If you don't have cookies enabled, expect weirdness. If you clear browser data every time you close the browser, expect to see this every time you start your browser.

2. Each browser on each device needs its copy of the cookie, so if you use two different browsers to get to MD on your desktop and also access MD on your phone, that's three places to see this.

3. Dynamic IP ranges should be reasonably accommodated at this point. No information has been given as to exactly how open these ranges are, but the settings on MD's side were changed to help people whose ISPs dynamically assign IP addresses within a block. If you're on a VPN (particularly if you move your 'location' around), or if your ISP hates you, this may still be an issue. Also, on phone/laptop, this can mean a new check every time you move locations. For mobile in particular this may be an issue.

4. The cookie will still reset once a week, as well as any time changes get made on MD's side to get this dialed in. The latter should settle out fairly quickly.

5. If it gets weird, try a hard refresh (ctrl-F5) or flush your cache/cookies and see if this helps.

(Usual 'not a staff member' disclaimer.)

 

[Samhill]

Summary of where we're at now, with a couple updates from what I've seen on the Discord this morning (US time):

1. You need cookies enabled. The one in use for this specific utility is 'MD-Edge-ID'. If you don't have cookies enabled, expect weirdness. If you clear browser data every time you close the browser, expect to see this every time you start your browser.

2. Each browser on each device needs its copy of the cookie, so if you use two different browsers to get to MD on your desktop and also access MD on your phone, that's three places to see this.

3. Dynamic IP ranges should be reasonably accommodated at this point. No information has been given as to exactly how open these ranges are, but the settings on MD's side were changed to help people whose ISPs dynamically assign IP addresses within a block. If you're on a VPN (particularly if you move your 'location' around), or if your ISP hates you, this may still be an issue. Also, on phone/laptop, this can mean a new check every time you move locations. For mobile in particular this may be an issue.

4. The cookie will still reset once a week, as well as any time changes get made on MD's side to get this dialed in. The latter should settle out fairly quickly.

5. If it gets weird, try a hard refresh (ctrl-F5) or flush your cache/cookies and see if this helps.

(Usual 'not a staff member' disclaimer.)

Information shouldn't be locked away somewhere else.

 

[Angry_Panda]

Information shouldn't be locked away somewhere else.

Agreed, though I get the feeling the staff member heading this project up is primarily trying to work out what's still playing into the problem 'edge cases' at this point, so personally I'm going to cut them some slack. YMMV.

It does appear there are some extensions/add-ons that are causing issues in Firefox (and possibly other browsers), so for anyone who's still having problems, check to see what you have enabled. It may help to turn all extensions off, confirm the check works as expected in a 'stock' configuration, and then bring the extensions back in one at a time to identify the conflicting extension.