page.goto freezes on Google Cloud Functions for some websiteshow to debug puppeteer in headless modeCloud functions timeout on page.goto()Firebase cloud functions is very slowEnabling CORS in Cloud Functions for FirebaseCloud Functions for Firebase trigger on time?How to deploy some functions to Cloud Functions for Firebase without affecting some other functions?Google Cloud Functions not workingLocalhost connection refused when accessing headless chrome instance from docker container using puppeteer (run locally)Google Cloud Functions Slow StartupPuppeteer name resolution error on Firebase Cloud Functionsignore-certificate-errors + headless puppeteer+google cloudCloud Functions puppeteer Error: net::ERR_NAME_RESOLUTION_FAILED at http://www.google.com
Prince of Darkness goes cryptic
What is the limit to a Glyph of Warding's trigger?
Moons and messages
Could a rotating ring space station have a bolo-like extension?
Why A=2 and B=1 in the call signs for Spirit and Opportunity?
Is a world with one country feeding everyone possible?
How does Dreadhorde Arcanist interact with split cards?
ifconfig shows UP while ip link shows DOWN
Writing "hahaha" versus describing the laugh
Is keeping the forking link on a true fork necessary (Github/GPL)?
Is it normal to "extract a paper" from a master thesis?
Did "hundreds of birds" fall out of the sky in the Netherlands due to a 5G test?
How to teach an undergraduate course without having taken that course formally before?
Set outline first and fill colors later
Alexandrov's generalization of Cauchy's rigidity theorem
What could be my risk mitigation strategies if my client wants to contract UAT?
Why is std::ssize() introduced in C++20
Comparison of bool data types in C++
How can I minimize the damage of an unstable nuclear reactor to the surrounding area?
Why'd a rational buyer offer to buy with no conditions precedent?
How can I get a refund from a seller who only accepts Zelle?
Can a UK national work as a paid shop assistant in the USA?
Merge pdfs sequentially
How to deceive the MC
page.goto freezes on Google Cloud Functions for some websites
how to debug puppeteer in headless modeCloud functions timeout on page.goto()Firebase cloud functions is very slowEnabling CORS in Cloud Functions for FirebaseCloud Functions for Firebase trigger on time?How to deploy some functions to Cloud Functions for Firebase without affecting some other functions?Google Cloud Functions not workingLocalhost connection refused when accessing headless chrome instance from docker container using puppeteer (run locally)Google Cloud Functions Slow StartupPuppeteer name resolution error on Firebase Cloud Functionsignore-certificate-errors + headless puppeteer+google cloudCloud Functions puppeteer Error: net::ERR_NAME_RESOLUTION_FAILED at http://www.google.com
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I am using:
Puppeteer version: 1.13.0
Platform / OS version: Google Cloud
Node.js version: 8
await.page.goto("https://somewebsite.com") freezes when I deploy it on Google Cloud functions.
I receive timeout error.Navigation Timeout Exceeded
const browser = await puppeteer.launch(
headless: true,
ignoreHTTPSErrors: true,
args: [
'--disable-gpu',
'--disable-dev-shm-usage',
'--disable-setuid-sandbox',
'--no-first-run',
'--no-sandbox',
'--no-zygote',
'--single-process', // <- this one doesn't works in Windows
]
);
const page = await browser.newPage();
try
await page.goto('https://somewebsite.com',
waitUntil: 'networkidle2' );
catch (error)
console.log('page.goto ERROR: ', error);
I can see it working in different environments:
- AWS
- Locally
It works for all except Google Cloud Functions. However, if I try google.com it works.
The problem is that the error is not helpful at all, the page.goto is just timing out.
I was wondering if there is a proper way to debug this?
Could it be OS issue?
but then again, AWS and Google cloud are both Linux based?
firebase google-cloud-functions chromium
puppeteer edited Apr 4 at 16:39
Jofre
1,8701216
asked Mar 23 at 21:49
Alexandr ZavaliiAlexandr Zavalii
1,030923
|
show 6 more comments
I am using:
Puppeteer version: 1.13.0
Platform / OS version: Google Cloud
Node.js version: 8
await.page.goto("https://somewebsite.com") freezes when I deploy it on Google Cloud functions.
I receive timeout error.Navigation Timeout Exceeded
const browser = await puppeteer.launch(
headless: true,
ignoreHTTPSErrors: true,
args: [
'--disable-gpu',
'--disable-dev-shm-usage',
'--disable-setuid-sandbox',
'--no-first-run',
'--no-sandbox',
'--no-zygote',
'--single-process', // <- this one doesn't works in Windows
]
);
const page = await browser.newPage();
try
await page.goto('https://somewebsite.com',
waitUntil: 'networkidle2' );
catch (error)
console.log('page.goto ERROR: ', error);
I can see it working in different environments:
- AWS
- Locally
It works for all except Google Cloud Functions. However, if I try google.com it works.
The problem is that the error is not helpful at all, the page.goto is just timing out.
I was wondering if there is a proper way to debug this?
Could it be OS issue?
but then again, AWS and Google cloud are both Linux based?
firebase google-cloud-functions chromium
puppeteer edited Apr 4 at 16:39
Jofre
1,8701216
asked Mar 23 at 21:49
Alexandr ZavaliiAlexandr Zavalii
1,030923
Is your Google Cloud project on a payment plan?
– Doug Stevenson
Mar 23 at 22:19
Yes I am using it for several projects. Its on paid plan.
– Alexandr Zavalii
Mar 23 at 22:20
I suggest you share a MCVE anyway, even if you don't think there's a point to it. You could still be making a mistake somewhere that just isn't showing up elsewhere. Without code, we'll never know.
– Doug Stevenson
Mar 24 at 0:05
1
Same problem, the timeout seems totally random on our side (same site sometimes works, sometimes don't, happens with google sites AND random sites).
– kursus
Mar 25 at 9:30
1
You can enable verbose logging by setting the environment variableDEBUG="puppeteer:*". Check out debugging tips for more information.
– Thomas Dondorf
Mar 25 at 19:53
|
show 6 more comments
I am using:
Puppeteer version: 1.13.0
Platform / OS version: Google Cloud
Node.js version: 8
await.page.goto("https://somewebsite.com") freezes when I deploy it on Google Cloud functions.
I receive timeout error.Navigation Timeout Exceeded
const browser = await puppeteer.launch(
headless: true,
ignoreHTTPSErrors: true,
args: [
'--disable-gpu',
'--disable-dev-shm-usage',
'--disable-setuid-sandbox',
'--no-first-run',
'--no-sandbox',
'--no-zygote',
'--single-process', // <- this one doesn't works in Windows
]
);
const page = await browser.newPage();
try
await page.goto('https://somewebsite.com',
waitUntil: 'networkidle2' );
catch (error)
console.log('page.goto ERROR: ', error);
I can see it working in different environments:
- AWS
- Locally
It works for all except Google Cloud Functions. However, if I try google.com it works.
The problem is that the error is not helpful at all, the page.goto is just timing out.
I was wondering if there is a proper way to debug this?
Could it be OS issue?
but then again, AWS and Google cloud are both Linux based?
firebase google-cloud-functions chromium
puppeteer edited Apr 4 at 16:39
Jofre
1,8701216
asked Mar 23 at 21:49
Alexandr ZavaliiAlexandr Zavalii
1,030923
I am using:
Puppeteer version: 1.13.0
Platform / OS version: Google Cloud
Node.js version: 8
await.page.goto("https://somewebsite.com") freezes when I deploy it on Google Cloud functions.
I receive timeout error.Navigation Timeout Exceeded
const browser = await puppeteer.launch(
headless: true,
ignoreHTTPSErrors: true,
args: [
'--disable-gpu',
'--disable-dev-shm-usage',
'--disable-setuid-sandbox',
'--no-first-run',
'--no-sandbox',
'--no-zygote',
'--single-process', // <- this one doesn't works in Windows
]
);
const page = await browser.newPage();
try
await page.goto('https://somewebsite.com',
waitUntil: 'networkidle2' );
catch (error)
console.log('page.goto ERROR: ', error);
I can see it working in different environments:
- AWS
- Locally
It works for all except Google Cloud Functions. However, if I try google.com it works.
The problem is that the error is not helpful at all, the page.goto is just timing out.
I was wondering if there is a proper way to debug this?
Could it be OS issue?
but then again, AWS and Google cloud are both Linux based?
firebase google-cloud-functions chromium
puppeteer firebase google-cloud-functions chromium
puppeteer edited Apr 4 at 16:39
Jofre
1,8701216
asked Mar 23 at 21:49
Alexandr ZavaliiAlexandr Zavalii
1,030923
edited Apr 4 at 16:39
Jofre
1,8701216
asked Mar 23 at 21:49
Alexandr ZavaliiAlexandr Zavalii
1,030923
edited Apr 4 at 16:39
Jofre
1,8701216
edited Apr 4 at 16:39
Jofre
1,8701216
edited Apr 4 at 16:39
Jofre
1,8701216
1,8701216
asked Mar 23 at 21:49
Alexandr ZavaliiAlexandr Zavalii
1,030923
asked Mar 23 at 21:49
Alexandr ZavaliiAlexandr Zavalii
1,030923
asked Mar 23 at 21:49
Alexandr ZavaliiAlexandr Zavalii
1,030923
1,030923
Is your Google Cloud project on a payment plan?
– Doug Stevenson
Mar 23 at 22:19
Yes I am using it for several projects. Its on paid plan.
– Alexandr Zavalii
Mar 23 at 22:20
I suggest you share a MCVE anyway, even if you don't think there's a point to it. You could still be making a mistake somewhere that just isn't showing up elsewhere. Without code, we'll never know.
– Doug Stevenson
Mar 24 at 0:05
1
Same problem, the timeout seems totally random on our side (same site sometimes works, sometimes don't, happens with google sites AND random sites).
– kursus
Mar 25 at 9:30
1
You can enable verbose logging by setting the environment variableDEBUG="puppeteer:*". Check out debugging tips for more information.
– Thomas Dondorf
Mar 25 at 19:53
|
show 6 more comments
Is your Google Cloud project on a payment plan?
– Doug Stevenson
Mar 23 at 22:19
Yes I am using it for several projects. Its on paid plan.
– Alexandr Zavalii
Mar 23 at 22:20
I suggest you share a MCVE anyway, even if you don't think there's a point to it. You could still be making a mistake somewhere that just isn't showing up elsewhere. Without code, we'll never know.
– Doug Stevenson
Mar 24 at 0:05
1
Same problem, the timeout seems totally random on our side (same site sometimes works, sometimes don't, happens with google sites AND random sites).
– kursus
Mar 25 at 9:30
1
You can enable verbose logging by setting the environment variableDEBUG="puppeteer:*". Check out debugging tips for more information.
– Thomas Dondorf
Mar 25 at 19:53
Is your Google Cloud project on a payment plan?
– Doug Stevenson
Mar 23 at 22:19
Is your Google Cloud project on a payment plan?
– Doug Stevenson
Mar 23 at 22:19
Yes I am using it for several projects. Its on paid plan.
– Alexandr Zavalii
Mar 23 at 22:20
Yes I am using it for several projects. Its on paid plan.
– Alexandr Zavalii
Mar 23 at 22:20
I suggest you share a MCVE anyway, even if you don't think there's a point to it. You could still be making a mistake somewhere that just isn't showing up elsewhere. Without code, we'll never know.
– Doug Stevenson
Mar 24 at 0:05
I suggest you share a MCVE anyway, even if you don't think there's a point to it. You could still be making a mistake somewhere that just isn't showing up elsewhere. Without code, we'll never know.
– Doug Stevenson
Mar 24 at 0:05
1
1
Same problem, the timeout seems totally random on our side (same site sometimes works, sometimes don't, happens with google sites AND random sites).
– kursus
Mar 25 at 9:30
Same problem, the timeout seems totally random on our side (same site sometimes works, sometimes don't, happens with google sites AND random sites).
– kursus
Mar 25 at 9:30
1
1
You can enable verbose logging by setting the environment variable
DEBUG="puppeteer:*". Check out debugging tips for more information.– Thomas Dondorf
Mar 25 at 19:53
You can enable verbose logging by setting the environment variable
DEBUG="puppeteer:*". Check out debugging tips for more information.– Thomas Dondorf
Mar 25 at 19:53
|
show 6 more comments
1 Answer
1
active
oldest
votes
Apparently there is an issue with timing in Puppeteer version 1.13.0. Try downgrading to 1.11.0 and it should work fine.
A similar question was answered in this Stackoverflow question. It points to this discussion.
answered Mar 26 at 11:40
Andrei CusnirAndrei Cusnir
1,0931715
I tried that, didn't work.page.gotofreezes, I am not even able to navigate to the page.
– Alexandr Zavalii
Mar 26 at 19:13
I had the same issue. I added 4 web pages to load using page.goto method. 3 executed without error, 4th had 30000ms timeout. Then I changed my GCF set up and it executed properly. My GCF is set up like, Nodejs 8 environment, Puppeteer 1.11.0 version, Memory allocated 1 GB, Timeout 300 seconds. Try this set up and let me know if it works for you.
– Andrei Cusnir
Mar 27 at 10:01
That's exactly the setup that I have :( the problem is that only this specific website does not load at all. I guess it has some error (maybe ssl error, really not sure), which is not handled correctly on Google cloud Linux in Chromium, but Its working anywhere else, like AWS, or my local MAC machine
– Alexandr Zavalii
Mar 27 at 10:04
Can you share the website that you are getting this issue at? I want to try to replicate the issue.
– Andrei Cusnir
Mar 27 at 10:06
1
I am working for Google Cloud Platform Support, but in order to provide further assistance you will have to create a private issue tracker > For Google Cloud Functions component, that so we could have access to your project and investigate further.
– Andrei Cusnir
Mar 27 at 11:56
|
show 1 more comment
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55318724%2fpage-goto-freezes-on-google-cloud-functions-for-some-websites%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Apparently there is an issue with timing in Puppeteer version 1.13.0. Try downgrading to 1.11.0 and it should work fine.
A similar question was answered in this Stackoverflow question. It points to this discussion.
answered Mar 26 at 11:40
Andrei CusnirAndrei Cusnir
1,0931715
I tried that, didn't work.page.gotofreezes, I am not even able to navigate to the page.
– Alexandr Zavalii
Mar 26 at 19:13
I had the same issue. I added 4 web pages to load using page.goto method. 3 executed without error, 4th had 30000ms timeout. Then I changed my GCF set up and it executed properly. My GCF is set up like, Nodejs 8 environment, Puppeteer 1.11.0 version, Memory allocated 1 GB, Timeout 300 seconds. Try this set up and let me know if it works for you.
– Andrei Cusnir
Mar 27 at 10:01
That's exactly the setup that I have :( the problem is that only this specific website does not load at all. I guess it has some error (maybe ssl error, really not sure), which is not handled correctly on Google cloud Linux in Chromium, but Its working anywhere else, like AWS, or my local MAC machine
– Alexandr Zavalii
Mar 27 at 10:04
Can you share the website that you are getting this issue at? I want to try to replicate the issue.
– Andrei Cusnir
Mar 27 at 10:06
1
I am working for Google Cloud Platform Support, but in order to provide further assistance you will have to create a private issue tracker > For Google Cloud Functions component, that so we could have access to your project and investigate further.
– Andrei Cusnir
Mar 27 at 11:56
|
show 1 more comment
Apparently there is an issue with timing in Puppeteer version 1.13.0. Try downgrading to 1.11.0 and it should work fine.
A similar question was answered in this Stackoverflow question. It points to this discussion.
answered Mar 26 at 11:40
Andrei CusnirAndrei Cusnir
1,0931715
I tried that, didn't work.page.gotofreezes, I am not even able to navigate to the page.
– Alexandr Zavalii
Mar 26 at 19:13
I had the same issue. I added 4 web pages to load using page.goto method. 3 executed without error, 4th had 30000ms timeout. Then I changed my GCF set up and it executed properly. My GCF is set up like, Nodejs 8 environment, Puppeteer 1.11.0 version, Memory allocated 1 GB, Timeout 300 seconds. Try this set up and let me know if it works for you.
– Andrei Cusnir
Mar 27 at 10:01
That's exactly the setup that I have :( the problem is that only this specific website does not load at all. I guess it has some error (maybe ssl error, really not sure), which is not handled correctly on Google cloud Linux in Chromium, but Its working anywhere else, like AWS, or my local MAC machine
– Alexandr Zavalii
Mar 27 at 10:04
Can you share the website that you are getting this issue at? I want to try to replicate the issue.
– Andrei Cusnir
Mar 27 at 10:06
1
I am working for Google Cloud Platform Support, but in order to provide further assistance you will have to create a private issue tracker > For Google Cloud Functions component, that so we could have access to your project and investigate further.
– Andrei Cusnir
Mar 27 at 11:56
|
show 1 more comment
Apparently there is an issue with timing in Puppeteer version 1.13.0. Try downgrading to 1.11.0 and it should work fine.
A similar question was answered in this Stackoverflow question. It points to this discussion.
answered Mar 26 at 11:40
Andrei CusnirAndrei Cusnir
1,0931715
Apparently there is an issue with timing in Puppeteer version 1.13.0. Try downgrading to 1.11.0 and it should work fine.
A similar question was answered in this Stackoverflow question. It points to this discussion.
answered Mar 26 at 11:40
Andrei CusnirAndrei Cusnir
1,0931715
answered Mar 26 at 11:40
Andrei CusnirAndrei Cusnir
1,0931715
answered Mar 26 at 11:40
Andrei CusnirAndrei Cusnir
1,0931715
answered Mar 26 at 11:40
Andrei CusnirAndrei Cusnir
1,0931715
1,0931715
I tried that, didn't work.page.gotofreezes, I am not even able to navigate to the page.
– Alexandr Zavalii
Mar 26 at 19:13
I had the same issue. I added 4 web pages to load using page.goto method. 3 executed without error, 4th had 30000ms timeout. Then I changed my GCF set up and it executed properly. My GCF is set up like, Nodejs 8 environment, Puppeteer 1.11.0 version, Memory allocated 1 GB, Timeout 300 seconds. Try this set up and let me know if it works for you.
– Andrei Cusnir
Mar 27 at 10:01
That's exactly the setup that I have :( the problem is that only this specific website does not load at all. I guess it has some error (maybe ssl error, really not sure), which is not handled correctly on Google cloud Linux in Chromium, but Its working anywhere else, like AWS, or my local MAC machine
– Alexandr Zavalii
Mar 27 at 10:04
Can you share the website that you are getting this issue at? I want to try to replicate the issue.
– Andrei Cusnir
Mar 27 at 10:06
1
I am working for Google Cloud Platform Support, but in order to provide further assistance you will have to create a private issue tracker > For Google Cloud Functions component, that so we could have access to your project and investigate further.
– Andrei Cusnir
Mar 27 at 11:56
|
show 1 more comment
I tried that, didn't work.page.gotofreezes, I am not even able to navigate to the page.
– Alexandr Zavalii
Mar 26 at 19:13
I had the same issue. I added 4 web pages to load using page.goto method. 3 executed without error, 4th had 30000ms timeout. Then I changed my GCF set up and it executed properly. My GCF is set up like, Nodejs 8 environment, Puppeteer 1.11.0 version, Memory allocated 1 GB, Timeout 300 seconds. Try this set up and let me know if it works for you.
– Andrei Cusnir
Mar 27 at 10:01
That's exactly the setup that I have :( the problem is that only this specific website does not load at all. I guess it has some error (maybe ssl error, really not sure), which is not handled correctly on Google cloud Linux in Chromium, but Its working anywhere else, like AWS, or my local MAC machine
– Alexandr Zavalii
Mar 27 at 10:04
Can you share the website that you are getting this issue at? I want to try to replicate the issue.
– Andrei Cusnir
Mar 27 at 10:06
1
I am working for Google Cloud Platform Support, but in order to provide further assistance you will have to create a private issue tracker > For Google Cloud Functions component, that so we could have access to your project and investigate further.
– Andrei Cusnir
Mar 27 at 11:56
I tried that, didn't work.
page.goto freezes, I am not even able to navigate to the page.– Alexandr Zavalii
Mar 26 at 19:13
I tried that, didn't work.
page.goto freezes, I am not even able to navigate to the page.– Alexandr Zavalii
Mar 26 at 19:13
I had the same issue. I added 4 web pages to load using page.goto method. 3 executed without error, 4th had 30000ms timeout. Then I changed my GCF set up and it executed properly. My GCF is set up like, Nodejs 8 environment, Puppeteer 1.11.0 version, Memory allocated 1 GB, Timeout 300 seconds. Try this set up and let me know if it works for you.
– Andrei Cusnir
Mar 27 at 10:01
I had the same issue. I added 4 web pages to load using page.goto method. 3 executed without error, 4th had 30000ms timeout. Then I changed my GCF set up and it executed properly. My GCF is set up like, Nodejs 8 environment, Puppeteer 1.11.0 version, Memory allocated 1 GB, Timeout 300 seconds. Try this set up and let me know if it works for you.
– Andrei Cusnir
Mar 27 at 10:01
That's exactly the setup that I have :( the problem is that only this specific website does not load at all. I guess it has some error (maybe ssl error, really not sure), which is not handled correctly on Google cloud Linux in Chromium, but Its working anywhere else, like AWS, or my local MAC machine
– Alexandr Zavalii
Mar 27 at 10:04
That's exactly the setup that I have :( the problem is that only this specific website does not load at all. I guess it has some error (maybe ssl error, really not sure), which is not handled correctly on Google cloud Linux in Chromium, but Its working anywhere else, like AWS, or my local MAC machine
– Alexandr Zavalii
Mar 27 at 10:04
Can you share the website that you are getting this issue at? I want to try to replicate the issue.
– Andrei Cusnir
Mar 27 at 10:06
Can you share the website that you are getting this issue at? I want to try to replicate the issue.
– Andrei Cusnir
Mar 27 at 10:06
1
1
I am working for Google Cloud Platform Support, but in order to provide further assistance you will have to create a private issue tracker > For Google Cloud Functions component, that so we could have access to your project and investigate further.
– Andrei Cusnir
Mar 27 at 11:56
I am working for Google Cloud Platform Support, but in order to provide further assistance you will have to create a private issue tracker > For Google Cloud Functions component, that so we could have access to your project and investigate further.
– Andrei Cusnir
Mar 27 at 11:56
|
show 1 more comment
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55318724%2fpage-goto-freezes-on-google-cloud-functions-for-some-websites%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Is your Google Cloud project on a payment plan?
– Doug Stevenson
Mar 23 at 22:19
Yes I am using it for several projects. Its on paid plan.
– Alexandr Zavalii
Mar 23 at 22:20
I suggest you share a MCVE anyway, even if you don't think there's a point to it. You could still be making a mistake somewhere that just isn't showing up elsewhere. Without code, we'll never know.
– Doug Stevenson
Mar 24 at 0:05
1
Same problem, the timeout seems totally random on our side (same site sometimes works, sometimes don't, happens with google sites AND random sites).
– kursus
Mar 25 at 9:30
1
You can enable verbose logging by setting the environment variable
DEBUG="puppeteer:*". Check out debugging tips for more information.– Thomas Dondorf
Mar 25 at 19:53