[Record] Building a remote edge browser.

Aug 31, 2023431

AI Translation

This post is translated from Chinese into English through AI.View Original

AI-generated summary

The text discusses the similarities between remote desktop accessed through the web and HTTPS. It suggests setting up a remote edge browser accessed through the web to bypass IP detection by New Bing. The instructions include creating a directory, setting up a reverse proxy service, and specifying default account and authorization settings. The version and services are also specified, including the image used for the edge browser. The text mentions the need to intercept and add authentication to the header when using Nginx Proxy Manager. The text ends with a reference to the specific edge browser being used.

There are few differences between remote desktop accessed through web and HTTPS, so it is possible to set up a remote edge browser accessed through web to bypass New Bing's (mistaken) IP detection.

Setting up kasmweb-edge#

Setting up reverse proxy service

mkdir -p ~/app/edge && cd ~/app/edge && nano docker-compose.yml
sudo docker-compose up -d
# Default account: kasm_user
# proxy_set_header Authorization "Basic a2FzbV91c2VyOnBhc3N3b3Jk";

version: '3.3'
services:
  kasmweb-edge:
    restart: unless-stopped
    shm_size: "512m"
    environment:
      - VNC_PW=password
      - APP_ARGS=--start-maximized --no-sandbox
    image: kasmweb/edge:1.14.0

networks:
  default:
    external: true
    name: ngpm

Reverse proxy for edge#

Nginx Proxy Manager has an issue with passing Authorization, so you need to intercept the corresponding authentication in the browser and add it to the header. Then, set a new authentication in Nginx Proxy Manager.
msedge_8RtVW0Ncu6