Chromium ARM64 'Request has timed out' #3897
Comments
|
Going to need more information as this isn't reproducible given what's been shared. Did you pull the appropriate platform? What size machine? Where is it hosted? Logs? |
OS: Oracle Linux Server release 8.9, ARM64 I have successfully installed and run browserless using I receive a "Request has timed out" error. In the logs of the browserless container, the following messages are displayed: |
|
Looks like Chrome isn't starting properly for some reason. Could you run with an env variable of |
|
ok |
|
I am seeing something very similar. I am running on two machines: one Intel AMD64, one arm/v8 I then pass a script to the REST api: This returns the page correctly on the Intel machine, and times out on the arm one (seems like the log-on button is never clicked. Weirdly enough -- if I add -e 'DEBUG=*' to the docker command line, the arm machine completes the script and returns the correct output. I have another, very similar script which works fine on the arm machine, so it's not all scripts. It's something quite particular here. I believe that the script doesn't get past the initial login. The script is the following -- unfortunately I can't get it to return anything without providing an actual login, but maybe it will help. export default async ({ page }) => {
await page.goto("https://portal.merenionline.cz/isge/app_client_login/");
await page.type("input[name=\"login\"]", "<redacted>");
await page.type("input[name=\"pswd\"]", "<redacted>");
await Promise.all([
// Wait for navigation to complete
page.waitForNavigation(),
// select the button with a distinct class
page.evaluate(()=>document.querySelector("body > section.register-photo > div > form > div:nth-child(19) > div > div:nth-child(1) > input").click()),
page.waitForSelector("iframe[name=\"init_tab\"]"),
]);
const f = await page.$("iframe[name=\"init_tab\"]");
const iframe = await f.contentFrame();
await Promise.all([
iframe.waitForNavigation(),
//iframe.click("#id_sc_field_obj_products_1"),
iframe.evaluate(()=>document.querySelector("#id_sc_field_obj_products_1").click()),
iframe.waitForSelector("#id_sc_field_r_meter_value_act_1"),
]);
const html = iframe.content()
return html
}; |
|
Yeah sadly I don't have a lot of expertise in this. The fact that there isn't a lot of logs from Puppeteer is interesting to me. |
|
I'm guessing that the arm/v8 isn't the same thing as |
|
I don't think that can be the answer: The problem script sometimes works. And if fact I have scripts which basically work fine always. This particular one -- times out only on the arm machine. I did mean arm64 -- I always get confused with the architecture names. TO be precise, my docker info says aarch64 and docker downloads the arm64 container. |
I have the exact same issue on arm64. However, the occurrence seems to be super random. But good to know that it's working on amd64, will switch to this arch for now. |
|
The problem still exists on amd64. Now switched to browserless v1 on amd64 and everything works fine. |
Hey, can you tell me how did you "switch" to v1? Download other version of the image? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I'm using Oracle Cloud ARM64
Installed Chromium using the command:
Ran the following command:
Received a 'Request has timed out' error
There are no issues on AMD64 systems
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: