Skip to Content

Internal browser error: Failed to launch the browser process!

352  Riya Francis January 17, 2023  Common Errors & Troubleshooting
Internal browser error: Failed to launch the browser process! on accessing web portal proxy 

 

Internal browser error: Failed to launch the browser process!
[0113/165322.629994:FATAL:zygote_host_impl_linux.cc(127)] No usable sandbox! Update your kernel or see https://chromium.googlesource.com/chromium/src/+/main/docs/linux/suid_sandbox_development.md for more information on developing with the SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
#0 0x5613f00b8382 base::debug::CollectStackTrace()
#1 0x5613f0025f23 base::debug::StackTrace::StackTrace()
#2 0x5613f0022f9f logging::LogMessage::~LogMessage()
#3 0x5613ee8bc3f6 content::ZygoteHostImpl::Init()
#4 0x5613efb65206 content::ContentMainRunnerImpl::Initialize()
#5 0x5613efb629ec content::RunContentProcess()
#6 0x5613efb62d9f content::ContentMain()
#7 0x5613efbb4a39 headless::(anonymous namespace)::RunContentMain()
#8 0x5613efbb46b5 headless::HeadlessShellMain()
#9 0x5613ebf4f1dc ChromeMain
#10 0x7f688d82b555 __libc_start_main
#11 0x5613ebf4f02a _start

 

TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

 

 

 

  • The above error occurs because it uses the old version of Kernel that does not support the latest updates of web portals. Make sure the kernel version is 4 and above in the gateway server for the web portals to work. You can check the kernel version using the below command.

[email protected] ~]# uname -r

  • You need to enable username spaces in the kernel. Run the following command in your Ezeelogin-installed server.

[email protected]:~# echo 'kernel.unprivileged_userns_clone=1' > /etc/sysctl.d/00-local-userns.conf

[email protected]:~# service procps restart

 

Internal browser error: Failed to launch the browser process! on accessing web portal proxy due to missing Libraries 

 

Internal browser error: Failed to launch the browser process!
/var/www/ezlogin/application/external/ezproxy/node_modules/puppeteer/.local-chromium/linux-756035/chrome-linux/chrome: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory
 
 
TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/master/docs/troubleshooting.md

 

  • If you're getting the above error, run the following command to fix the issue.

[email protected]:~# yum install nss -y

 

Internal browser error: Failed to launch the browser process!
/var/www/ezlogin/application/external/ezproxy/node_modules/puppeteer/.local-chromium/linux-756035/chrome-linux/chrome: error while loading shared libraries: libdrm.so.2: cannot open shared object file: No such file or directory
 
 
TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/master/docs/troubleshooting.md

 

  • If you're getting the above error, run the following command to fix the issue.

[email protected]:~# yum install libdrm -y

 

Internal browser error: Failed to launch the browser process!
/var/www/ezlogin/application/external/ezproxy/node_modules/puppeteer/.local-chromium/linux-756035/chrome-linux/chrome: error while loading shared libraries: libgbm.so.2: cannot open shared object file: No such file or directory
 
 
TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/master/docs/troubleshooting.md

 

  • If you're getting the above error, run the following command to fix the issue.

[email protected]:~# yum install libgbm -y

 

 
Rating: 3 (2 Votes)