Age Verification Succeeded—Then Pornhub Turned Into a Black Screen

The age-check page congratulated me before Pornhub went completely black. I had followed the verification prompts and watched a green confirmation appear. The browser redirected me to the video saved in my library. Its controls flashed for half a second, then vanished. No error message. No retry button. Just a black rectangle where the player should have been. I refreshed, completed the check again, and reached the same empty screen.

I was in a hotel outside Birmingham, packing for an early train.

The item in my account was not important enough to justify an hour of troubleshooting. That was precisely why the failure became irritating so quickly. I was an adult. The site had asked me to prove it. I had done so.

I expected the player to open.

Instead, verification succeeded while the thing it was supposed to unlock remained unusable.

My first assumption was simple: the age check must have failed without admitting it.

So I did it again.

Repeating the check repeated the black screen

The second attempt looked cleaner than the first.

I closed every other tab, reopened the site, and started from the home page. The age-verification service loaded, completed its checks, and sent me back.

Black screen.

I tried another video.

Black screen.

I signed out, opened a private window, and verified again.

The library appeared, but every player remained empty.

By then, I had proved that the verification page could load and that I could complete it. Repeating the process was no longer testing anything new.

Still, the timing made the wrong explanation feel convincing. When the screen turns black immediately after an age check, it is natural to assume the site has rejected the result. (Reddit)

That frustration matched mine.

But the verification itself was not the part failing.

The check ended before the player began

Age verification has become a real access step in the United Kingdom. Since July 25, 2025, services that allow pornography have been required to use highly effective age checks to prevent children from reaching the content. (Ofcom)

For the user, the process looks like one action.

Behind the screen, it has two parts.

First, the age-check service confirms eligibility. Then the browser returns to Pornhub, where that result must unlock the existing session and player.

My confirmation appeared.

The black screen arrived after the return.

That sequence suggested a broken handoff rather than a failed check. (Arxiv)

Once I saw the problem that way, repeating the camera or identity step made less sense. I needed to find out what changed between the green confirmation and the empty player.

The browser was the next suspect

I disabled the browser’s content blocker.

I allowed pop-ups.

I relaxed its cookie restrictions.

Then I cleared Pornhub’s site data and started again.

The verification completed.

The player stayed black.

I switched from Safari to Chrome.

The pages looked slightly different, but the ending was identical.

Two browsers could open the check, complete it, and return to a player that never started.

Then the hotel Wi-Fi dropped for several seconds.

The VPN icon disappeared and returned.

A moment later, Pornhub asked me to verify again.

That interruption connected the two halves of the problem.

My VPN recovered by changing the session

I had kept my regular VPN active because I was using hotel Wi-Fi.

It was a large, established provider with polished applications, years of public history, and more locations than I would ever need. Its automatic mode had chosen a fast London server.

When the hotel connection weakened, the VPN reconnected quickly.

For ordinary browsing, that looked like good recovery.

During the age-check handoff, it created a fresh route at exactly the wrong moment.

I could begin verification through one exit address, return through another, and then ask the player to accept a session that no longer looked continuous.

I disabled automatic selection and chose a London server manually.

The check completed.

The player displayed a loading circle, then went black.

I tried a second London server.

This time Pornhub returned me to the verification page before the player appeared.

A third server reached the video page, but another brief Wi-Fi interruption erased the controls again.

The provider’s large network gave it plenty of replacements.

That was also the problem.

Every replacement risked separating the verified page from the session that needed to use the result.

Speed was answering the wrong question

I ran a speed test.

The result was excellent.

It did not move the player by a single frame.

The video did not need more bandwidth yet. It needed the verification, redirect, and player request to remain part of the same usable session.

A fast route that changed halfway through the process was less useful than a steadier route with an ordinary speed result.

I briefly installed a free browser VPN because it promised a quick connection without another subscription.

The age-check page opened through it.

The final redirect returned to another black player.

The extension added one more moving part without protecting the entire connection, so I removed it.

I had now completed the age check five times.

The problem was not proving my age more convincingly.

It was preserving the proof long enough for the player to use it.

The smaller app started with the situation

OnlydogVPN was installed from an earlier test.

It had fewer locations, a shorter public history, and fewer independent reviews than the major provider. Those were the reasons I had kept it as a backup rather than making it my default.

That evening, its smaller interface made more sense.

I did not need another map or another “fastest server” button. I needed one connection suited to private browsing on unstable hotel Wi-Fi.

The app organized its options around situations. I selected the preset for private browsing on a weak or changing network.

It also let me begin without creating a conventional email-and-password account. After repeatedly moving through an age-verification flow, avoiding another registration form removed a small but welcome friction.

I tapped Connect.

The app selected the route.

Then I reopened Pornhub.

Because I had cleared the previous session, the site requested age verification once more.

I completed it.

The green confirmation appeared.

The browser redirected.

For a second, the player was black.

Then the controls appeared.

The thumbnail sharpened.

The progress bar filled.

I pressed play.

The video started.

The useful result appeared inside Pornhub

I did not return to the VPN app to inspect the server.

I moved the playback slider two minutes forward.

The video resumed.

I returned to my library, opened a second saved item, and watched its player load without another verification request.

Then the hotel Wi-Fi weakened again.

The image softened for a moment, but the player did not disappear. The page did not send me back to the age check. When the connection recovered, playback continued.

That was the result the first provider had never produced.

The check, redirect, and player remained one continuous session.

The smaller app uses an HTTP/3-based connection designed to recover when the network underneath it becomes unstable. In practical terms, the hotel Wi-Fi faltered without forcing the browser to start the whole journey again. (IETF)

That was all the technical explanation I needed.

The route stayed together.

The player worked.

The age check had succeeded all along

Once playback began, the previous failures made sense.

The verification service had accepted me.

The black screen appeared because the return to Pornhub was not surviving long enough to become usable playback.

That explained why completing the check again and again achieved nothing. Each attempt created another chance for the route to change between confirmation and player load.

It also explained why switching browsers did not help. The browsers were completing the visible steps. The unstable connection underneath them was breaking the result afterward.

I could not inspect Pornhub’s internal verification rules or every routing decision made by either VPN. I could see the outcome: the established provider repeatedly reached the confirmation but lost the usable session, while the smaller app carried the same browser through to playback.

The black screen was not asking me to prove my age again.

It was showing that the journey back had not finished.

Moving through the hotel did not restart everything

A few minutes later, I closed the laptop and carried it downstairs while the hotel arranged a taxi.

The device left the room’s access point and joined the lobby network.

When I reopened the browser, I expected the black rectangle to return.

The player paused briefly.

Then it resumed.

I was still signed in.

The age check remained accepted.

That smaller success mattered because hotel Wi-Fi rarely fails once in a neat, predictable way. It weakens in lifts, corridors, lobbies, and rooms far from the nearest access point.

A VPN that opens the player but loses the session during the next network change only postpones the problem.

This connection carried it through.

Continuity mattered more than another verification attempt

The major provider had the longer history, the larger server network, and more locations close to Birmingham.

It also kept treating a weak connection as a reason to establish a fresh route.

That was reasonable for casual browsing. It was the wrong behavior for an age-check process that needed to return to the same player session.

The smaller app made fewer decisions visible to me and preserved the result that mattered. Verification completed, the browser returned, the controls appeared, and the video played.

When Pornhub shows a black screen after confirming the age check, repeating the check may only repeat the broken handoff.

In that hotel room, proving I was over eighteen was never the difficult part.

Keeping the same connection alive long enough for Pornhub to use that proof was.