This question already has answers here:
Heroku and GitHub: "Items could not be retrieved, Internal server error"
(12 answers)
Closed 9 months ago.
When I try to add GitHub as my deployment method, it just pops up ands says one of these two things. Error1(image)
Error 2(image)
But the really odd part is that when I look on GitHub it shows Heroku as a OAuth application that is added but says it was never used. And then, in logs it says things like this:
Error logs
Does anyone know what's going on? I'm using Heroku to host a discord bot and ever since I logged out of GitHub on Heroku because it was acting up I cant get back in.
deploy from github is currently unavailable due to some hacker attack
reference: https://status.heroku.com/incidents/2413
We are dedicated to ensuring the security of our customers, and as
such, continue to pursue all potential leads as part of our
investigation. As part of that commitment, we want to let you know
about two additional findings that may impact a small number of our
customers.
As reported on status.heroku.com, on April 7, 2022, a threat actor
obtained access to a Heroku database and downloaded stored customer
GitHub integration OAuth tokens. On that same day, the threat actor
downloaded data from another database that stores pipeline-level
config vars for Review Apps and Heroku CI. Additionally, another small
subset of Heroku users had their Heroku tokens exposed in a config var
for a pipeline. This was identified on May 16, 2022, after further
forensic investigation. We have no evidence of any unauthorized access
to Heroku systems since April 14, 2022.
Any users affected by these issues were notified directly and provided
with additional guidance. If you did not receive an email directly
from us, we have no evidence that you were impacted by either of these
recently identified issues. If you received an email from Salesforce
(techcomms#mail.salesforce.com) and have identified suspicious
activity, please contact security#salesforce.com.
For an update on our current progress with regards to the GitHub
integration, please see this blog post.
so you can deploy manually through heroku CLI
as #MarcoWriteCode has mentioned the basis of the error that you are facing.
I would suggest that you go through the Heroku CLI documentation and continue your deployment from here. https://devcenter.heroku.com/articles/getting-started-with-nodejs
Use heroku CLI for a bit, then switch back to github deploys
Related
I am sending my data from firestore to algolia. Before sending that I have to set that data from firestore to google cloud platform. For that I ran following commands on google cloud shell terminal:
firebase login
Then it gave me this messsage:
Firebase optionally collects CLI usage and error reporting information to help improve our products. Data is collected in accordance with Google's privacy policy (https://policies.google.com/privacy) and is not used to identify you.
Then it asked for Allow Firebase to collect CLI usage and error reporting information?. I replied yes. Then it gave me a link to authenticate the account. After clicking on that link, it gave an error message.
This is the error message which I recieved
How to resolve this error? I tried many tutorials but could not find any solution. i tried this link.
https://developers.google.com/identity/protocols/oauth2/web-server#handlingtheresponse
Well, This is happened on my side as well.
When the link has been displayed in console part of it wasn't detected by the terminal application. As the result it opened in web browser just as a part of the link. If analyze whole link you will see that near the end of the link there is something like response_type=. If this part is missing this error massage is shown.
I hope it will help!
I got the error when trying to get an access key for one of our APIs.
"AADSTS65001: The user or administrator has not consented to use the application with ID '{GUID}'
First, I was trying to prompt=consent during login, thinking that I had new consents that weren't prompted during login. And I got the following error.
"AADSTS65005: The application '{GUID}' asked for permissions to access a resource that has been removed or is no longer available. Contact the app vendor."
I removed prompt=consent and started fiddling with the permissions in Azure, and now I was stuck on the same error.
I changed everything as it was, but I still get the error. However, this only happens to my user. Everyone else can still log in without problems.
So my problem is actually in two parts:
The first error when trying to get an access token for the API.
Somehow I need to prompt the user with consent, but I am using adal.js which uses a silent retrieval of the keys using an invisible iframe. I want the support to be when the user logs into the web app.
Is this possible?
My user can't log in to our web app anymore. Everyone else can. Did anyone encounter this before?
The product is a SPA Web App written in React, and we use adal.js (adal-vanilla) as a library for authentication to Azure AD.
Update
I finally got some stuff working. Not all the way, but at least it's a start.
The problem with this is that users registered on other tenants (this is a multi-tenant app) don't get consent to use the API. These users get the error. However, I registered a user on the same tenant, and everything worked as intended.
Problem two was solved by removing all the permissions, adding them one by one, and testing in between. Somehow this worked after two-three tries.
The problem is that users from other tenants don't get a consent prompt to access the API.
Somehow the issue got fixed, I'm not 100% sure how or why but here are the steps I performed to fix it if someone finds themselves in a similar situation:
Ensure that all permissions are correct (APIs are added as delegated permissions to the client)
All services (web app & apis) are multitenant
Update manifest with:
"availableToOtherTenants": true,
"knownClientApplications": [
"{client app application id}"
],
(availableToOtherTenants was false for the API even though it was marked as multitenant in the settings)
The consent might be possible to fix with prompt=admin_consent.
As for the second problem, you can add your web app as a known client application of the API. This will allow simultaneous consent when the user authenticates to the web app.
To do that, find the API app registration in Azure Portal's Azure AD blade. Then open its manifest (there is a Manifest button on the app blade). In there should be a "knownClientApplications" property. Add the client id of the web app in the array and save the manifest.
E.g.:
"knownClientApplications": [
"bda6ffff-ffff-ffff-ffff-ffff8bf8c57f"
],
My friend and I have run into two different sets of issues while attempting to add licensing to an Office 365 Excel addin, and have so far not been able to resolve it through any docs or forums.
We followed the instructions here: https://dev.office.com/officestore/docs/add-license-checks-to-office-and-sharepoint-add-ins to the letter, and have created a node/express server to host the app, and are using the REST verification service to determine the token's authenticity.
We've been testing on 2 different machines, and the issues we've ran into are as follows:
1) We cannot get the test license to return isTest: true
2) (on the other machine) The token never gets appended to the initial get call, at all.
The closest we've come to finding a solution so far was this SO post: Nodejs - Office App License token verification service does not validate the token, who seems to have this issue, but whose question is unanswered. Or this one, Apps for Office: my task pane app doesn't get the licensing '?et=' license token, whose answer suggest appending a sample one to the xml file.
We've also replicated this issue on other tester's machines as well, but have not been able to find a solution for this anywhere.
Anyone is having problems retrieving Likendin connections with new apps?
With old apps my hybridauth app is retrieving connections just fine. While with new apps (I created 3 different apps) I keep getting Access to connections denied
When authenticating I got the correct scopes on likedin login screen(r_basic_profile, r_network, w_messages, r_emailaddresses)
Im using free plugin http://wordpress.org/plugins/wp-social-invitations/ which uses hybridauth
This is a recent problem with the linked. They have stopped providing member connection in their recent API change. Now you have to obtain a partner certificate in order to access member connection information. Even my production application has stopped this functionality to work. We might be removing linked from our application as it is of no use now with so much of restrictions.
Linkedin api changed recently, that's the reason scopes are not longer working
The get connections API in linked in has been deprecated follow this link to get the API' that are allowed as part of developers program right now.
I am working on a Azure Web application. The code compiles and runs fine on my local machine. But when I upload the package in Azure Platform, the webrole wouldn't start and gives Busy status with the message: "Waiting for role to start... System is initializing. [2012-04-30T09:19:08Z]"
Both Onstart() and Run() don't contain any code. I am not blocking the return of OnStart.
However I am using window.setInterval in javascript. The javascript function retrieves the values from Database every 10 seconds.
What can be done to resolve this?
In most of the situation when a Role (Web or Worker) is stuck, I have found the following steps very useful:
Always add RDP access to your role because in some cases when role is stuck you still have ability to RDP your instance and investigate the problem by yourself. In some cases you could not RDP to your instance because dependency services are not ready yet to let you in. So if you have RDP enabled or could RDP to your instance please try to log you in.
Once you have RDP to your instance. Get the local machine IP address and launch directly in browser. In internal IP address starts from 10.x.x.x so you can open the browser based on your endpoint configuration i.e. http://10.x.x.x:80 or https://10.x.x.x:443
If you could not get into the instance over RDP then your best bet are to get the diagnostics info to understand where the problem could be. The diagnostics info is collected in your instance and sent to Azure Storage, configured by you in your WebRole.cs (in Web Role) or WorkerRole.cs (in Worker Role) code. Once diagnostics is working in your role, you can collect the Diagnostics data at your configured Azure Blob/Table storage to understand the issue.
If you don't have RDP access and don't have any Azure Diagnostics configured (or could not get any diagnostics data to understand the problem) your best bet is to contact Azure Support team (24x7 via web or phone) at the link below and they will have ability to access your instance (with your permission) and provide you root cause.
https://support.microsoft.com/oas/default.aspx?gprid=14928&st=1&wfxredirect=1&sd=gn
When contacting Azure Support, please provide your Subscription ID, Deployment ID, your Azure Live Account ID and a small description of your problem.
Two things to check:
Make sure your diagnostics connection string is pointing to a real account, and not dev storage
Check the session state provider in web.config. By default, it points to SQL Express LocalDB, which won't exist in Windows Azure.
The reason for this I run into the most is a missing or invalid assembly. But there are several great posts that can help disanosis this so I won't dive into the matter too deeply myself.
http://social.msdn.microsoft.com/Forums/en-US/windowsazuretroubleshooting/thread/6c739db9-4f6a-4203-bbec-eba70733ec16
http://blogs.msdn.com/b/tom/archive/2011/02/25/help-with-windows-azure-role-stuck-in-initializing-busy-stopped-state.aspx
http://blogs.staykov.net/2009/12/windows-azure-role-stuck-in.html