heroku-buildpack-google-chrome | Run Google Chrome on Heroku | Platform As A Service library
kandi X-RAY | heroku-buildpack-google-chrome Summary
kandi X-RAY | heroku-buildpack-google-chrome Summary
This buildpack downloads and installs (headless) Google Chrome from your choice of release channels.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of heroku-buildpack-google-chrome
heroku-buildpack-google-chrome Key Features
heroku-buildpack-google-chrome Examples and Code Snippets
Community Discussions
Trending Discussions on heroku-buildpack-google-chrome
QUESTION
I wrote a web scraper using python.
To deploy it on heroku, I took this article as reference. https://www.andressevilla.com/running-chromedriver-with-python-selenium-on-heroku/
And added these buildpacks. https://github.com/heroku/heroku-buildpack-google-chrome https://github.com/heroku/heroku-buildpack-chromedriver
But when I run the code on heroku, this error occurs.
selenium.common.exceptions.SessionNotCreatedException: Message: session not created: This version of ChromeDriver only supports Chrome version 90 Current browser version is 89.0.4389.114 with binary path /app/.apt/opt/google/chrome/chrome
It looks like the chromedriver buildpack doesn't support chrome buildpack.
Does any other buildpack work? Or I can try any other way to deal with it?
Thanks!
...ANSWER
Answered 2021-Apr-14 at 06:55Heroku Chrome Driver Buildpack allows you to choose version of chrome driver but by default it should have installed latest version of it available. You can set config var(Environment variable) CHROMEDRIVER_VERSION
=89.0.4389.23
to download a chromedriver version compatible for chrome 89. After adding the variable, you'd want to redeploy for the changes to take effect.
QUESTION
For whatever reason, I am unable to deploy puppeteer correctly on to heroku. It builds, but when I run it, I get the application error page. When I check the logs, I get:
...ANSWER
Answered 2020-Sep-10 at 00:01Okay, first I had a typo. It's --no-sandbox
.
Second, I had to download a new webpack onto Heroku called heroku-buildpack-chrome-headless.
QUESTION
I am using heroku with selenium with heroku/google-chrome and heroku/chromedriver buildpacks. There was a recent update to google chrome and the google-chrome buildpack was updated.
EDIT: I am seeing on my dev instance that
...ANSWER
Answered 2020-Apr-12 at 17:06I figured out the fix, you need to reset your cache
QUESTION
This runs locally (without specifying driver_path
), but not on Heroku.
Code:
...ANSWER
Answered 2017-Nov-19 at 18:01I am quoting Ilya Vassilevsky from this post
ChromeDriver is just a driver for Chrome. It needs the actual Chrome browser installed on the same machine to actually work.
Heroku doesn't have Chrome installed on its dynos by default. You need to use a buildpack that installs Chrome. For example:
https://github.com/dwayhs/heroku-buildpack-chrome
You can see how it fetches Chrome:
https://github.com/dwayhs/heroku-buildpack-chrome/blob/master/bin/compile#L36-38
Then I read their discussion in the comments:
Petr Gazarov says
I tried this buildpack and it didn't work. I'm suspecting installing google chrome (or any browser) on heroku might be more involved.
Ilya Vassilevsky replies
Yes, Heroku is a very opinionated and closed platform. It should be much easier to set up Chrome with ChromeDriver on your own VM on AWS, Linode, or DigitalOcean.
Petr Gazarov replies
Thanks for your answer Ilya. I ended up re-writing with Watir with phantomjs because I couldn't get Heroku to install Chrome.
You can read more info in that question. If something comes to my mind, I will post it.
QUESTION
I'm using apparition together with heroku-buildpack-google-chrome configured as unstable
and I'm trying to specify a custom chrome binary path: /app/.apt/usr/bin/google-chrome-unstable
.
Is there a way to do this in apparition?
...ANSWER
Answered 2020-Feb-29 at 06:10If you set the environment variable BROWSER_PATH
it will be used as the location of the Chrome binary.
QUESTION
I have a website made using Django, click a button on the website triggers a scraper to start. This scraper uses selenium. I have added the following two build packs needed for selenium to my heroku app:
...ANSWER
Answered 2019-Jun-18 at 12:20I wanted to comment you the link, where I previously answered this question, but I don't have enough rep to comment, so anywho here you go..
Set the following path using heroku congfig:set
command
heroku config:set CHROMEDRIVER_PATH=/app/.chromedriver/bin/chromedriver
and
heroku config:set GOOGLE_CHROME_BIN=/app/.apt/usr/bin/google-chrome
Verify the paths using heroku config
command
You can use this snippet to configure your definition
QUESTION
I have a Ruby code that does this:
...ANSWER
Answered 2018-Jun-04 at 22:05I can't assure this is sufficient for everything you need, but if you add webdrivers
to your gemfile and require it, it will automatically download chromedriver for you.
QUESTION
I am currently working with the: Heroku Build Pack for headless chrome. https://github.com/heroku/heroku-buildpack-google-chrome/
I'm encountering this infuriating error where my node script (show below) cannot connect to the chrome instance. I get a pretty definitive error being:
...ANSWER
Answered 2017-Aug-16 at 21:36Alright I figured it out. When deploying to heroku, I was using two different Procs in the Procfile. One for web
which was launching the Node script. And another for launching the headless chrome daemon.
On heroku, those two different procs don't even share the same dyno. Meaning they we're on totally separate "boxes" - at least in theory. This resulted in them having different ports set in the ENVs (not that it even mattered at that point - they might as well be in different continents)
Solution:
Have the node script start the actual headless chrome, then ultimately connect to that child process using the CDP
interface.
Also - if you're here and also curious about documentation for the CDP
interface for node - it doesnt exist at the moment. Your best option, which is actually pretty good, is: https://chromedevtools.github.io/debugger-protocol-viewer/
Happy hunting.
Edit:
Example of how we handled launching the chrome child process from the application source
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install heroku-buildpack-google-chrome
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page