Connecting a LinkedIn profile to Grinfi is done step by step via the cloud browser. If you encounter any issues during the process, first identify the step where the error occurred. This will help you find a solution faster. Below you'll find detailed instructions for resolving common problems.
Difficulties Opening the Cloud Browser
Only one cloud browser session can be active within a workspace at a time. If you see the error "Failed to connect to Cloud Browser" or "You have reached the maximum number of simultaneously running cloud browsers" during startup, follow these steps:
Check your tabs: Make sure the cloud browser isn't accidentally left open in other tabs or browser windows.
Check team activity: Confirm whether other users in your workspace are currently using the cloud browser.
Close active sessions: Terminate all other cloud browser sessions and try connecting again.
Alternative solution: If you cannot wait, complete authorization via the GoLogin browser - this method does not have limitations on the number of simultaneous sessions.
You can find profile connection instructions in the article: [How to connect LinkedIn Account to Grinfi].
Unable to Set Up a Proxy
Error when connecting your own proxy
If you have selected your own proxy but the system does not allow you to proceed to the next step, the proxy server is likely experiencing temporary downtime. This is a normal occurrence for most providers.
Solution: Wait 5 minutes to 1 hour and try again. If the connection still doesn't work, contact your proxy provider to test or replace the address. Alternatively, you can always use Grinfi's built-in proxy.
Error "Something went wrong"
This error usually indicates an inactive session token for your Grinfi account or temporary maintenance on the platform.
Solution: First, sign out of your Grinfi account (click Log Out), clear your browser cache, and log in again. This will force a token refresh. If re-authorization does not help, we are likely deploying a platform update or performing scheduled maintenance at that moment. Such work usually takes up to 30-40 minutes. Please wait and try again. If the problem persists, contact support.
"Error: Proxy Error. Request timeout after ___ms"
This means the proxy lost connection exactly at the moment the browser was opening.
Solution: Click the Change Proxy button to assign a new IP address and try opening the cloud browser again. If the problem continues, try changing the proxy several times.
Unable to Pass LinkedIn Captcha During Login
Captcha issues most often arise due to technical flaws in the LinkedIn interface.
Captcha window is too small
The LinkedIn interface sometimes displays images so small they are difficult to see. Since this is a technical issue on LinkedIn's side, it is impossible to enlarge the window — try to pass the verification as is.
Infinite Captcha Loop
If the LinkedIn algorithm decides you entered the captcha incorrectly the first time, it may send you into an infinite loop of verifications.
Step 1 (Pause): Stop connection attempts and try again in 24 hours. Usually, LinkedIn "resets" the data after a day.
Step 2 (Reset Connection): Click the Start over button in Grinfi and begin the authorization process from scratch. This will create a new digital fingerprint and help break the captcha loop.
Error "Something went wrong" at the Final Stage
An update or scheduled maintenance is likely being deployed on the server at this moment.
Solution: Try again in 30-40 minutes. Your progress will not be lost — open the cloud browser and click I have logged in.
Hotkeys Not Working in Cloud Browser
If hotkeys are not working, it is usually related to your local browser's security restrictions or a conflict with extensions.
Step 1: Grant browser permission
Your browser (e.g., Google Chrome) must allow clipboard access for Grinfi.
In the browser address bar (where the website URL is shown), click the Settings icon.
Find the Clipboard item and set it to Allow.
Refresh the page to activate the changes.
Step 2: Check for conflicting extensions
Some browser extensions that affect text processing or translation can block hotkeys in the cloud browser (most commonly services like Grammarly, Google Translate, LanguageTool, etc).
Solution: Temporarily disable or remove these extensions.
If you prefer not to disable them, use alternative actions (e.g., copy-paste via right-click).
Issues Connecting via GoLogin
Session is not transferred to the profile ("User not found" error)
Solution: Check that the email used in GoLogin is correct (you can find it in the top-right corner of the GoLogin browser → Menu).
Grinfi session is not visible in GoLogin
Solution: Force refresh the session list. Press Cmd + R (Mac) or F5 / Ctrl + R (Windows). You can also click All Profiles in the top left corner of the GoLogin interface.
Unable to start GoLogin session
Browser update: Check for critical updates for the GoLogin app itself. Close the program completely, reopen it, and install updates.
Proxy temporarily unavailable: Wait 5 minutes to 1 hour and try again.
Error "This site cannot be reached"
You likely entered a search query (e.g., the word linkedin) in the URL bar. Proxy providers block the use of search engines (Google, Bing) to save traffic.
Solution: Always enter the direct address of the resource, for example: linkedin.com
Proxy in GoLogin does not match the one selected in Grinfi
Sometimes you may notice that the proxy country in GoLogin differs from the country selected in Grinfi.
External services (like GoLogin) use their own databases to determine IP geolocation. These algorithms often identify the nearest Point of Presence (PoP) or Autonomous System (ASN) rather than the proxy's initial routing point. In some cases, geolocation data may be outdated.
This is purely a visual inaccuracy that does not affect the security of your account.