VNC manual login works, but LinkedIn logs out after a few navigation hops

[webdude999]

I am testing the VNC login flow from camofox-browser. My broader goal is to use this as part of a personal AI assistant workflow for managing my personal LinkedIn conversations, but I am currently testing the browser behaviour manually first.

Setup:

• Cloned the repo locally on my laptop
• Added the VNC config according to https://github.com/jo-inc/camofox-browser/tree/master/plugins/vnc
• Built the container image locally via 'make build' and then created a docker-compes with the configuration
• Successfully logged into the container via VNC
• Logged in manually to my personal LinkedIn account through VNC connection
• Browsed LinkedIn manually inside the VNC session

The login itself works, but after a few navigation hops inside LinkedIn, I get logged out again.

I am trying to understand whether this is expected behaviour with LinkedIn, a known limitation, or whether I am missing an important configuration detail. A pointer or blunt reality check would be appreciated.

camofox.config.json

{
  "id": "camofox-browser",
  "name": "Camofox Browser",
  "version": "1.6.0",
  "plugins": {
    "youtube": { "enabled": true },
    "persistence": {
      "enabled": true,
      "profileDir": "/data/profiles"
    },
    "vnc": {
      "enabled": true,
      "resolution": "1920x1080",
      "password": "optional-secret",
      "viewOnly": false,
      "novncPort": 6080
    }
  }
}

docker-compose.yaml

services:
  camofox-browser:
    image: camofox-browser:135.0.1-x86_64
    environment:
      - PROXY_HOST=xx
      - PROXY_PORT=xx
      - PROXY_USERNAME=xx
      - PROXY_PASSWORD=xxx
      - CAMOFOX_API_KEY=xx
      - ENABLE_VNC=1
      - VNC_PASSWORD=xx
      - VNC_BIND=0.0.0.0
      - NOVNC_PORT=6080
      - HOST=0.0.0.0
      - BIND=0.0.0.0
      - CAMOFOX_HOST=0.0.0.0
    ports:
      - 127.0.0.1:5900:5900
      - 127.0.0.1:9377:9377
    volumes:
      - camofox-browser-data:/data/profiles
    container_name: camofox-browser
    restart: unless-stopped
    networks:
      - hermes-net


volumes:
  camofox-browser-data:

networks:
  hermes-net:
    external: true
    name: hermes-net

requests-opentab.sh

#!/bin/bash
curl -X POST http://localhost:9377/tabs \
  -H 'Content-Type: application/json' \
  -d '{"userId": "shared-camofox", "sessionKey": "visible-tab", "url": "https://linkedin.com"}'

requests-download-cookie.sh

#!/bin/bash
curl http://localhost:9377/sessions/shared-camofox/storage_state \
  -H 'Authorization: Bearer XXXXXX' \
  -o storage_state.json

[skyfallsin]

Can't comment on LinkedIn specifically but you may want to try doing the same thing on other automated browser stacks. If it's very sophisticated anti-bot then you might be out of luck even with camofox.

[webdude999]

I tested a similar flow with Puppeteer where I only changed the browser user-agent to match my laptop and routed traffic through a proxy running on my laptop. That setup seems to stay stable.

I also tested this directly with the original Camoufox Python code by matching all CreepJS-reported values from my laptop’s Chrome browser, but then I lose the agentic interface and VNC workflow, which your project solves.

Would it make sense to expose a small config surface for browser/fingerprint options, either via env vars or a config file? Happy to test it if useful.