parse.com: parse deploy not working - parse-platform

I have running project on parse.
Suddenly it stops deploying files on server.
When I run parse deploy command then it throws error as
Unable to authenticate app. Please make sure your applicationId and masterKey in "config/global.json" is correct
I have tried to do same with new account from my desktop but same error.
I am using windows 7 and Js Sdk v2.1.0(parse).
Please help to get sort out this issue.
I done with google no resolution found.

Related

Protocol Error in TDS Stream on Laravel App on Azure

I'm trying to deploy a Laravel Application to Azure using the App Service.
Things are working pretty ok, I set the PHP version to 7.1, added the Composer extention, and added a web.config file in the public folder of my repo for supporting rewrites in IIS. After that I deployed through Git. I also set the correct environmental variables:
The only problem is, I can't connect to the Azure SQL Database. It gives me this strange Protocol Error, which I can't solve. Google only shows old answers... I hope someone can help me?
SQLSTATE[HY000]: [Microsoft][ODBC Driver 13 for SQL Server]Protocol error in TDS stream (SQL: select * from [settings]) (View: D:\home\site\wwwroot\........\resources\views\login.blade.php)
Alright, it turned out to be a corrupted instance of the Azure Web App. After deleting the App, and deploying a new clean version, it started working perfectly.

tns appstore upload: Unable to connect to iTunes Connect (1268)

Unable to upload .ipa file using NativeScript cmd
I'm running the following command:
tns appstore upload my-appstore-id my-appstore-pass --ipa /var/www/app.ipa
See the following error message:
Unable to connect to iTunes Connect
An error occurred while processing the json request. (1268)
no other messages or logs are provided.
Have no idea where to search for solution.
This was a known issue on the nativescript end. https://github.com/NativeScript/nativescript-cli/issues/2874
I had ran into this a few weeks ago and after upgrading to nativescript#next the issue went away.
To answer #BrianDilley you need to supply your itunes password, it's not app specific.

Visual Studio webdeploy fail even when connection is validated?

I am trying to deploy my webapp VS2015 RC1 DNX 451. Even when I validate connection and run publish I get error
Severity Code Description Project File
Error Error Code: ERROR_USER_UNAUTHORIZED
Error More Information: Connected to the remote computer ("crocus.arvixe.com") using the Web Management Service, but could not authorize. Make sure that you are using the correct user name and password, that the site you are connecting to exists, and that the credentials represent a user who has permissions to access the site. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_USER_UNAUTHORIZED.
Error Error: The remote server returned an error: (401) Unauthorized.
Googling the issue and even trying to view host forum just says make sure username and password is correct. I am getting nowhere trying various settings. Any ideas how to debug the issue?
I am using Arvixe.com as host.
You should contact Arvixe.com. They likely have some odd configuration on their servers but I would suspect they can help you resolve the issue.
Arvixe does not support Web Deploy anymore. Once they move you to their new servers Web Deploy won't be available to you. In Visual Studio you can set up a Publish with FTP instead of Web Deploy. If you're used to Web Deploy publishing your database changes, then you'll need to do those yourself with SQL scripts. Entity Frameworks has an option to produce a SQL script for a migration, so you can use that to publish your EF database changes.

gem error on remote machine

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.

Error on Github deploy on windows azure

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/

Resources