[Bug] - edge browser not running on Microsoft Azure VPC

[mailbyms]

Existing Resources

• Please search the existing issues for related problems
• Consult the product documentation : Docs
• Consult the FAQ : FAQ
• Consult the Troubleshooting Guide : Guide
• Reviewed existing training videos: Youtube

Describe the bug
After start docker container, there is no "Connect" button （没有“连接”按钮）

To Reproduce
Steps to reproduce the behavior:

1. create a vpc on Microsoft Azure VPC, select ubuntu 20.04.6, with 8GB memory, 2 cpu cores
2. install docker enviroment
3. run docker run --rm -it --shm-size=512m -p 6901:6901 -e VNC_PW=password kasmweb/edge:1.12.0
4. use edge to browse "https://ip:6901"

Expected behavior
edge browser show be running

Screenshots
There is no "Connect" button （没有“连接”按钮）

Workspaces Version
Version 1.12

Workspaces Installation Method
Single Server, Azure VPC, Ubuntu 20.04.6

Client Browser (please complete the following information):

• OS: ubuntu 20.0.4.6， provided by microsoft azure vpc, with 2 cpu cores and 8GB memory
• Browser: edge
• Version: latest

Workspace Server Information (please provide the output of the following commands):

• uname -a:
  Linux gpt 5.15.0-1034-azure Cloudflared and KASM? I have tried proxy config workspaces-issues#41~20.04.1-Ubuntu SMP Sat Feb 11 17:02:42 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

• cat /etc/os-release
  NAME="Ubuntu"
  VERSION="20.04.6 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.6 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/"
  SUPPORT_URL="https://help.ubuntu.com/"
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
  PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal

• sudo docker info

Client:
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.10.2
Path: /usr/libexec/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.16.0
Path: /usr/libexec/docker/cli-plugins/docker-compose
scan: Docker Scan (Docker Inc.)
Version: v0.23.0
Path: /usr/libexec/docker/cli-plugins/docker-scan

Server:
Containers: 5
Running: 1
Paused: 0
Stopped: 4
Images: 8
Server Version: 23.0.1
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Using metacopy: false
Native Overlay Diff: false
userxattr: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 1
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 2456e983eb9e37e47538f59ea18f2043c9a73640
runc version: v1.1.4-0-g5fd4c4d
init version: de40ad0
Security Options:
apparmor
seccomp
Profile: builtin
Kernel Version: 5.15.0-1034-azure
Operating System: Ubuntu 20.04.6 LTS
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 7.765GiB
Name: gpt
ID: 6d9d6657-1d2a-425b-a123-fc8486c87b55
Docker Root Dir: /var/lib/docker
Debug Mode: false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false

• sudo docker ps | grep kasm
  1feb404082a7 kasmweb/edge:1.12.0 "/dockerstartup/kasm…" 51 minutes ago Up 51 minutes 4901/tcp, 5901/tcp, 0.0.0.0:6901->6901/tcp, :::6901->6901/tcp interesting_leakey

Additional context
Please checkout log output of docker logs -f container_id:
a.txt
I thinks the following log would be the problem:

[195:413:0328/083819.723341:ERROR:cert_issuer_source_aia.cc(34)] Error parsing cert retrieved from AIA (as DER):
ERROR: Couldn't read tbsCertificate as SEQUENCE
ERROR: Failed parsing Certificate
[195:413:0328/083819.827998:ERROR:cert_verify_proc_builtin.cc(677)] CertVerifyProcBuiltin for code.yengo.com failed:
----- Certificate i=0 (CN=code.yengo.com) -----
ERROR: Time is after notAfter
[298:302:0328/083819.830826:ERROR:ssl_client_socket_impl.cc(1153)] handshake failed; returned -1, SSL error code 1, net_error -201
[195:286:0328/083819.940491:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: U

[haonit]

I have a similar problem when I run a chrome container.
The chrome worked well at beginning, After a few hours, it cannot open any website. There is a suspected log from console.

Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")

I also capture network traffic. According to the network packets, Chrome starts the TCP 3-ways handshake, and the TCP connection is established, but chrome doesn't send any HTTP requests. This is wired.