At my company we had some proxy settings which restricted the installation of cypress via CMD->npm.
After some discussions with the network guys we added *.cypress.io and registry.npmjs.org to the proxy settings and after that "npm install cypress" worked perfectly. The message "Finished Installation" is shown and I could also open the Cypress GUI by typing "node_modules.bin\cypress open" in CMD.
But when the GUI was opened I tried to click on the LogIn button I get "Cannot connect to API server"
"We tried but failed to connect to the API server at https://api.cypress.io/"
Any idea why I cannot connect to the api server when I just did the whole installation without any problems?
I'm not sure why you're getting this error - my best guess is that the request for api.cypress.io is also hitting another server that isn't allowed through your firewall. Most likely this is Github, as the only option for logging in is by connecting your Github account.
That said, unless you're using the dashboard service, you don't actually need to log in to run tests. If the Log In button works properly, you'll get a message that looks like this:
Logging in gives you access to the Cypress Dashboard Service. You can set up projects to be recorded and see test data from your project.
This message is accompanied by a button prompting you to log in via Github.
Related
I am attempting to write an automation script for a process on a website using PhantomJS. I have done this same type of automation many times before, but I am having trouble with this one particular website that uses Oracle Access Manager.
When I log in with Chrome or any other desktop browser, I have no problems. However, when I try to log in with the headless browser I receive an OAM9 error which is very unspecific "for security reasons"
I have tried changing the user agent string and ignoring bad ssl certificates, I am running out of ideas and my higher ups promised this functionality to someone. Any help would be appreciated.
I have recorded a simple web test in VS 2013 Ultimate and im attempting to run it on a remote agent.
I get the following error:
Request failed: No connection could be made because the target machine actively refused it 127.0.0.1:23109
If i change my run settings to only run the test locally it succeeds.
When i view the "Manage Test Controller" dialog the agents are registered and in the ready state.
I have checked the Controller and agent LAN settings and none of them is configured (or required) to use a proxy.
Does anyone have any idea whats going on?
So the problem was the Internet Explorer security settings on the agents and also Internet explorer was configured to use a proxy on the agents.
I logged onto the server and checked this initially but as my own user account. I then checked by logging on as the user the agents run as and removed the configured proxy from IE, lowered the security settings and all was well.
I made a dashing app that queries the google api as part of its jobs. On my local everything works fine and I used git to clone the repo on a remote machine and ran bundle install there but when I try to run dashing start I get this error:
/home/mwerner/.rvm/gems/ruby-2.1.2/gems/signet-0.5.1/lib/signet/oauth_2/client.rb:941:in `fetch_access_token': Authorization failed. Server message: (Signet::AuthorizationError)
{
"error" : "invalid_grant"
}
I am using relative paths in the app so it can't be there is an authentication issue. I tried manually installing all the gems I use on the local machine on the remote machine via gem install ... but no luck. Hints?
I had the very same issue today. I got it resolved by checking back into my google developers account. In my case I had entered a wrong Mail address under service_account_email in the .rb file.
I inserted the data shown under "Client ID for Web Apps" where it had to be the one from "Service Account" out of my Google Developer API Account. Make sure you use Service Account Credentials for the widget!
Also I reassured that I had setup that very same address for read access in my google analytics account.
In short, getting that error means there is something wrong with the data you put in the analytics.rb file.
Once I did the above it resolved my issue and I was able to start dashing.
hej,
since march we got some troubles with our deployments on our windows azure server.
It seems that the deployments doesn't work and because sometimes it works sometimes not i don't get it.
Some kind of error i saw on my windows azure dashboard -> deployments:
"Response status code does not indicate success: 500 (Internal Server Error)."
or
"Host key verification failed. fatal: The remote end hung up unexpectedly"
i tried to restart the server or make new commits to github or simply redeploy or disconnect and reconnect to github. At the moment nothing works. There is a development server and a live server. Both contains the exact similiar version of the website (written in node.js). i've checked it a lot of times. Deployment with the development version works fine. live dont.
Do you have any suggestions? I have no idea where to start :-(
If it's a web role you can check the iisnode/ folder, should contain the log files. They can also be accessed with the emulator running, try
http://127.0.0.1:81/iisnode/
Scenario:
I set up successfully TFS2010 webdeploy task for solution. Everything worked fine until suddendly something went wrong in the deployment task.
Solution has 2 web projects..those are configured to deploy on build and publish it to the dev-server.
Does anybody have a knowledge what is wrong in build (information below)?
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\Web\Microsoft.Web.Publishing.targets
(3847): Web deployment task failed.
((4.8.2011 11:01:10) An error occurred when the request was processed on the remote computer.)
(4.8.2011 11:01:10) An error occurred when the request was processed on the remote computer. Unable to perform the operation. Please contact your server administrator to check authorization and delegation settings.
I can give more information if someone needs it.
I encountered the same issue when building via TFS. When I tried to manually import the website I got a more informative error: "not able to log on the user \WDeployConfigWriter".
Turns out that when you install web deploy it sets up two local accounts WDeployConfigWriter and WDeployAdmin. The passwords on these accounts are set to expire. So reset the passwords on the web server and set to "never expire". Then go to Management Service Delegation in IIS. Each of the presented rules has a UserName field. Where it is WDeployAdmin or WDeployConfigWriter right click and update the credentials to the new passwords.
A full explanation with screenshots can be found here: http://workinghardinit.wordpress.com/2011/07/18/wdeployconfigwriter-account-issues-trouble-shooting-web-deploy-2-0-with-lessons-learned/
All you have to do is re-run the script "AddDelegationRules.ps1" located in "C:\Program Files\IIS\Microsoft Web Deploy V3\Scripts\"
This is the script that is run when web deploy is first installed. It will re-create any missing delegations, re-set the passwords for both WebDeployAdmin and WebDeployConfigWriter, and add WebDeployAdmin back to the Administrators group.
You would still need to set the password on each account not to expire after re-running the script.
We had the same issue-- in our case we are only using MSDeploy (without TFS). Resetting the password for those 2 local accounts (WDeployConfigWriter and WDeployAdmin) solved the problem as their passwords had expired. We attempted to change the password policy to never expire, but only a local Administrator can do that.
run this command lusrmgr.msc
double click on user and
double click the account name, and tick "password never expires".
Done.
In my case it was a botched install of Web Deploy.
Uninstalling then re-installing Web Deploy fixed it for me -- Repairing didn't help.