Embedded browser initialization failed
I am having an issue with the Response/Render feature of the embedded browser.
When I click on "Render" in the "Response" tab I receive the following message "Embedded browser initialization failed"
I also ran the Embedded browser health check and I get the following messages.
Checking Platform Support - Success
Checking Browser Binaries - Success
Creating embbeded browser documenation window - Error
Aborting checks due to errors.
Burp Pro v2.0.22beta
Kali Linux with all updates as of 2019-05-28
I have also attempted to update the installation and this did not resolve the issue.
Thanks for the info, Dan.
We’re hoping to release a workaround for this issue in the next update of Burp 2.×.
We expect this issue to have been fixed in the latest release: v2.0.24beta.
Let us know if you’re still experiencing issues.
OS: Kali Linux with latest updates
Burp Suite: Pro v2.0.24beta
"Creating embedded browser documentation window Error"
"Aborting checks due to errors.
Shubham – sorry to hear you’re still having difficulty. Can you please email firstname.lastname@example.org with your Diagnostics and Embedded browser health check – which are both on the Help menu.
I've just updated to v2.1 and I'm having the same error as above. Could you advise?
Pepita– sorry to hear you’re still having difficulty. Can you please email email@example.com with your Diagnostics and Embedded browser health check – which are both on the Help menu.
[0726/153651.016897:FATAL:setuid_sandbox_host.cc(157)] The SUID sandbox helper b
inary was found, but is not configured correctly. Rather than run without sandbo
xing I'm aborting now. You need to make sure that /home/.../.BurpSuite/burpbrowser/0.122/lib/chrome-sandbox is owned by root and has mode 4755.
I did the change and everything is working.
Thanks, Louis. When running as root, the embedded browser sandbox is switched off. Another workaround for this is to Disable the embedded browser sandbox when running as a non-root user (User options > Display > HTML Rendering > Enable embedded browser sandbox).
Our development team are looking into a fix for this.
If I disable the browser sandbox (eek) the health check then fails at:
"Unable to created headless browser."
See same debug message as Louis above, although needing to grant root privilege in order to run a browser feels very wrong, now if you'd said send corrupt IP packets I'd have understood.
Changing the ownership and permissions to those in the debug log and enabling the sandbox works. All tests pass. I can read the Help pages again.
sudo sysctl -w kernel.unprivileged_userns_clone=1
fixed it for me.