Proxy - Stuck at "Waiting for <ip address>"

anon70349247 2018-04-26 09:21:48 UTC #1

I have built a few tests that shoot some messages from our front end to our midoffice.

The next step is to go into the midoffice and run some tests there. Unfortunately I can't seem to reach it. After Testcafe boots up, with the screen resizing bit the browser gets stuck at "Waiting for ". I've waited for a few minutes to see if it ever continues but it does not. I can reach the midoffice without trouble outside of Testcafe.

I am running Testcafe on my laptop connected to our network but our midoffice is a SaaS solution running in AWS. I am guessing something is wrong with certificates, proxies or authorizations of some kind. But all the information I have is that my browser keeps waiting. Where can I find more information what is going wrong and narrow it down? Does Hammerhead have a log that may contain something useful?

MarinaRukavitsyna 2018-04-26 13:37:50 UTC #2

Hello @BobBard,
At present, Hammerhead does not support logs. If you are using corporate proxy, I suggest you use the --proxy host command.
If this is not your case, please provide us with a link to the problematic page so that we can see the issue locally. If you do not want to share your web site with other users, you may send a private message to me.

anon70349247 2018-05-01 13:08:24 UTC #3

I am running Testcafe in Cmder and I have the proxy configured there. That proxy is working for our other internal application. Just to make sure I also added the proxy command but then the browser redirected to about:error with in the html just hammerhead scripts. I believe that that broke more things.

The website can only be reached from within our network, so sharing it isn't going to work out

I know this makes it a bit hard to help, but any ideas are appreciated!

MarinaRukavitsyna 2018-05-02 10:02:53 UTC #4

Bob,
I have no idea about the cause of the issue. Would you please localize the issue in a small project and send it to us for research?

anon70349247 2018-05-02 11:13:28 UTC #5

I'll see if I can reproduce it with a setup. But there is a lot of infrastructure between my computer and the application so maybe I won't be able to reproduce it.

anon70349247 2018-05-03 06:26:07 UTC #6

I checked it out with another dev at our company and we found out that the proxy was the issue. For this application we are using a different proxy than for the rest of the internet. When I specified the correct proxy everything worked perfectly well.