What the Cloudflare block page on linkedin.com/login means, why it does not affect your automation, and how to get past it in one step.

You open a sender profile in the Cloud Browser and, instead of LinkedIn, you get a page reading "Sorry, you have been blocked — You are unable to access linkedin.com", with the browser tab titled "Attention Required! | Cloudflare".

This is a block served by Cloudflare, not by LinkedIn and not by GetSales. Your LinkedIn account has not been restricted, and nothing is wrong with the sender profile or its proxy.

Two things are worth knowing:

It only appears on the login page. The block is tied to the linkedin.com/login address specifically. Any other LinkedIn page opens normally.

It does not affect your automation. Connection requests, messages and all other tasks continue to run exactly as before. If your sender shows the status Working and tasks are completing, nothing is broken, and there is nothing to fix on the automation side.

Change the address in the browser's address bar from login to feed and press Enter:

Your LinkedIn feed opens and you can use the session as normal.

If the account is already signed in, which is the usual case for a connected sender, the feed loads straight away. If it is not, LinkedIn will show you its sign-in form from there.

You do not need to report this page on its own, since it is cosmetic and limited to one URL.

Get in touch if, after opening the feed, the session turns out to be signed out and signing in again does not hold, or if your sender profile shows an error status or has stopped completing tasks. Those are separate problems with their own causes.