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.
Related
I have installed LHCI(Light House CI) server on an AWS EC2 instance(or my own home-server). The server is up and running. I have the url
I can add projects to the CI server with #lhci/cli#0.3 wizard and the project I create through client wizard appears successfully on the LHCI server.
As successful result of wizard it gives me two token. Admin and upload token whih I use it in my client config(upload token)
However, when it runs the auto-run and generates the report, the next step which is pushing data to my LHCI instance, it says token is invalid. I installed it on my own Linux box in my home network.
I thought it could be something wrong with my network and something dodgy happening. Then I installed it on EC2 and still same issue.
One thing I didn't find in the documentation is about whether the server needs to be HTTPS? (if you know this it could be a great help as well)
How come the upload token generated by the wizard is not valid ? what am I missing ?
I had the same problem. First, make sure the lhci client and server version match. It is thought that additional authentication factors have been added as the master version of lhci has recently been upgraded. In my case, the following error occurred and I solved it by setting the version to the same version.
Error: Unexpected status code 403
{"message":"Invalid token"}
I loaded the EchoBot template from Microsoft here: https://marketplace.visualstudio.com/items?itemName=BotBuilder.botbuilderv4
I started a new project and try to run it locally. No MicrosoftAppID or MicrosoftAppPassword is provided.
Then I loaded the latest Bot Framework Emulator v4.7
I connect locally, again no App ID or App Password:
However when I try to send a message I get unauthorized error, why would I get unauthorized error when connecting locally?
The server is definitely running locally and the local URL is correct:
One question I want to ask is the login dependent on any 3rd party URL call? My company security policy is blocking all URL unless whitelisted, so if this is the case, maybe the authentication is blocked? What would be the URL for me to whitelist?
EDIT: I tried it a VM outside of the company network and it works! So something must be getting blocked. Any idea?
I got around it by using a VM outside the company network instead. It's not a solution, but it is a work around. I highly suspect some port are being blocked by company firewall but not sure what so I am not sure how to get it whitelisted.
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.
I'm trying to migrate from Parse.com service to a self-hosted Parse Server, and it's been a bit difficult.
Basically I set up my server like this:
Run $ npm install -g parse-server
Set env vars (PARSE_SERVER_DATABASE_URI, PARSE_SERVER_MASTER_KEY, PARSE_SERVER_APPLICATION_ID)
Run $ parse-server
Everything is up and running, and I also setup a machine running parse-dashboard in a very similar way.
I had already synced the database and had no problems with it.
The problem is that when I try to send a push notification, I get the message:
Missing push configuration
I believe that's connected to the APNS settings. In Parse.com dashboard we can add the APNS certificates, but on the self hosted dashboard there is no such option (or I couldn't find it).
What am I missing? How do I set theses things up?
I believe that running parse-server without the recommended Express wrapper does not give me full control of everything I needed to configure the application.
I created an Express app, started the serving using the guide #thailey01 suggested and now it works.
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/