I have a java script code in git hub and I was deploying it many many times on heroku during the last month and I had no problem.Today, when I wanted to deploy the exact same code on heroku, I've got the following error:
The requested API endpoint was not found. Are you using the right HTTP verb (i.e. `GET` vs. `POST`), and did you specify your intended version with the `Accept` header?
Does anybody know why I encountered this error and what should I do to solve it?
I'm having the exact same error since today, even though I've been able to deploy my java app before.
There might be something wrong on heroku's end.
I made a ticket and I'll try to update you on the answer.
I had the same problem and when I was looking for to create a ticket I found this support notification about this issue now, it's an internal error in Heroku.
Check this link
We are investigating reports of increased API errors. This affects a number of actions on the platform, including deploys, for users without a credit card associated with their account. We will update here shortly.
Related
My organization is currently trying to move away from Heroku and we just migrated our React.js app to Nextjs. Originally I had considered going with AWS but Vercel seems to have a lot of benefits that would help us in the long term.
Currently our Laravel backend is still hosted in Heroku with a Postgres database. When I try to deploy, it appears that I cannot make a GET call.
This Next.js code works as expected on a Heroku dyno, but not when I attempt to deploy to Vercel.
Are there any gotchas, or considerations I should be aware of? Has anyone else ran into this issue?
Figured out what it was. Hope this helps somebody else! We had the .next build in our .gitignore folder because we had to switch back and forth between a legacy project and the .next folder caused some big issues. We just removed it and everything is building as expected. Still curious as to why it worked in Heroku and not Vercel though.
I hope somebody can help me with this issue.
I recently moved my azure pipeline approval release process from slack web hook to Azure pipeline App for slack, because I found that having the approve and reject button directly in slack chat was something really nice to have to make approvals easier.
This is the process I follow:
Install Azure pipeline App in slack workspace
Create a private channel and /invite #azpipelines
I signed in /azpipelines signing
Once those steps has been completed, I started to subscribe my release pipelines selecting the stages I was interesting in. Everything worked just fine for a couple of days, I was receiving the notifications and I was able to approve and reject them without any problem, which is great, but today, out of nowhere I realised that I was receiving the emails from azpipelines that a release has been issued but no notification in channel.
The documentation about azure pipeline is really poor and I have no idea what is going wrong with the configuration.
Did this happen to anyone before and can direct me on the right path of what could be the issue behind it?
Thank you very much for any help you can provide
Sometimes, I also could encounter the similar problems.
And many times, I can fix the issue via the following ways:
Unsubscribe and re-subscribe the notifications.
Log out and then log in again.
Uninstall and re-install the Azure Pipelines App.
May be you also can try this steps to see if the issue can be resolved.
I made a Reaction Role Bot (Discord.py) a week ago, and when I'm hosting the Bot on my own PC everything is working perfectly fine. But when I#m pushing the File in Heroku and try to run it there, there are many Errors like this: https://gyazo.com/d40c7051aa7037a31101d51443314c90
I really don't know why there is an Error, because i changed absolutely nothing on the File.
Is there someone who maybe know why this happens and how i can get rid of this error?
It is likely Heroku pulled discord.py 1.5, and you are running an older version on your local machine. v1.5 introduced support for gateway intents, see this page on how to update your bot code to work with them.
Last night after I pushed my latest release to the heroku git master branch the site was available via the https://appname.herokuapp.com address. This morning when I made one small change to a CSS file and pushed it again I discovered that the site is not available over https but is available over http (and everything looks right). I can't believe that a simple change to a static file could cause this. Has anyone else had this problem? I'm using the free account (planning to upgrade to hobby soon) so I can't get Heroku support. Is this just a temporary outage on their part or do I need to fix something? Thanks!
OK, this turned out to be a local issue with the computer I was using that cleared up as suddenly as it had appeared. Thanks for the comments and I now have logging to boot!
I'm following the instructions in the Heroku Postgres docs for creating an external application that connects to Heroku Postgres for its data layer. The instructions mention that the credentials are automatically rotated and I must handle this myself.
I read more docs to learn about webhooks existing to help notify the rest of your system that changes have happened in your Heroku services. This made sense to me to be an area where the Heroku devs would have implemented this. There must be a webhook that exists that I could use to be notified when the credential rotation happens. I found that there was the api:addon webhook which had the update event. I tested this webhook, expecting this to be what I was looking for, but I found that it was not fired upon credential rotation. It was only fired when I provisioned or deleted more Heroku Postgres add-ons.
Since the webhook I need doesn't exist, I coded a workaround where I expect a PostgreSQL library auth error to be thrown while my AWS Lambda executes. If an error is thrown, I assume it's from the rotation and I have the still running Lambda function fetch new credentials using the Heroku API and try the PostgreSQL query again, at which point it works unless there are other errors. I tested this while manually rotating my credentials and it worked okay, but it's kind of ugly code. See here for a detailed example.
So at this point, I'm wondering if the webhook I'm looking for does exist and I just wasn't able to find it. Or, if it doesn't exist, I would like to request it as a new feature. I understand that the Heroku team may not want people picking their add-ons a la carte, and they want people to use the entire Heroku platform, but I think it would add a lot of value to the Heroku platform. Personally, I've enjoyed getting into more and more cloud services as I learn since I'm usually able to choose them a la carte. For example, AWS doesn't forbid me from only using S3 and nothing else from them. They do as much as they can to make it easy for me to link my applications to it, no matter what other cloud services I use.
I contacted Heroku directly to ask if this type of webhook existed and I received a useful response from them:
There isn't a webhook specifically for credential rotations, although
with a bit of logic you can sort of recreate the same thing. Whenever
you Postgres credentials rotate, it will trigger a new release, which
does trigger a webhook. You can use that to inspect the release via
the API to determine if the values changed.