I have deployed an Elixir/Phoenix web app on Heroku 2x instance, the backend is in Postgres. The app works fine most of the time but every now and then it returns no such app I am not able to figure out, why is it happening. I have checked the logs and metrics but nothing is helping. In fact, no logging happens when such errors are happening. It feels as if temporarily the DNS resolver on their side has crashed. I haven't added any custom domain and using the default domain name provided by Heroku.
Related
This is annoying I've deployed locally, all working well, when I deploy to Heroku I get a 400 error for my web hooks, I've checked the STRIPE_PUBLIC_KEY, STRIPE_SECRET_KEY,and STRIPE_WH_KEY all are correct, what am i missing?
Updated keys, deleted endpoint and recreated, restarted dynamos.
The Laravel latest app crashed once we hit Waterondoor APIs multiple times and then restart while running perfectly on local. On server side it is handled by Nginx.
Server side directory: it is residing in /wms-web
What we have tried:
On local it is running fine
When we are using only APIs call from the postman, it is running fine
We cleared the cache, and config on the production side
We tried to change many things on Nginx as well but didn’t workout
here is the complete demo of this error: https://www.loom.com/share/e2139fad9a6248d4a96126dd335ef4c2?focus_title=1&muted=1&from_recorder=1
My iOS app has suddenly started giving this error message when logging in or creating a new user in the app:
[Error]: {"code":1,"message":"Internal server error."} (Code: 1, Version: 1.15.4)
Here is the pickle. The app works fine on an earlier version (version 4.4.0) that I have on my iPad. Here I can log in and create a user, and I can add items and delete items while in sync with the server. In the new version of the app (4.4.1) nothing has changed with regards to the code on my login page. I can still fetch data from the server in the app as well, but logging in and creating a user gives the internal server error.
I got my server on Heroku and the database on MongoDB. The database is available and running. However, the server Heroku got several failed throughputs (5xx code) during a day. This says to me that something is going on with the server side of things.
Does anyone know where to turn to next? I can't seem to get my head around where the issue is rising from. I have already sent a mail to Heroku, so I'll make an update when I receive an answer.
But basically, I need help to know what would be my next step to figure out what is causing the error?
I deployed a web app to Heroku yesterday and it seemed to work if I access the URL from my machine. However I was not able to access from any other devices on the same AND different network.
I thought that maybe it's just my browser cached the website and in reality it's down.
Some of the web services that tell you if a specific URL is down or not report various results - some say it's down, some say it's up.
(Not sure if I can post links here!)
http://downforeveryoneorjustme.com/rock-paper-scissors-.herokuapp.com
https://currentlydown.com/rock-paper-scissors-.herokuapp.com
But then again - I am able to see it via https://browserling.com/
I thought that this might be due to cached DNS but 1 day is way too long and Android flushes DNS after every 10 minutes (as far as I know)
To see if your app on Heroku is running and responding to requests, use the Heroku Toolbelt command
heroku logs --tail
This command shows messages about the app status, i.e when it is up or if it crashes.
Having the logs running with the tail option show the requests as they happen.
If you are on the Heroku free plan, then your application will sleep after 30 minutes of activity.
Once sleeping, the next request to your Heroku app will automatically wake the app up. The time taken to wake your app is largely dependant on how quickly your app starts, but should be a matter of seconds hopefully.
If an application is a little slow in starting, this could lead to a timeout and making it seem like you app is down.
If you do not see real-time log entries when trying to access your Heroku app from a particular device or network, my only thought is that there is some network policy or device blocking access to certain IP ranges (ie. Amazon Web Services).
I have three mvc 3 web applications in a single web role on Azure Cloud Services. All of a sudden this morning both the single instance in production and in staging give "HTTP Error 503. The service is unavailable." when navigated to in a browser.
I rebooted the production instance but nothing changed. Then I deployed a remote desktop enabled version to the staging instance and logged in. However, strangely when I navigate to the web applications in a browser inside the remoted staging instance everything works.
Looking at IIS server logs it seems there are some issues starting the roles (warning level about the appPoolId being incorrect) but obviously the roles are starting as they are accessible from inside the staging server.
The World Wide Web Publishing service is also running and even after restarting this service the web application is not accessible externally.
Does anyone have an explaination for why the sites are accessible locally but not remotely that would help me debug this issue?
I found out where the issue came from, the bindings that were configured in IIS7 did not include bindings for the actual [abc].cloudapp.net host headers.
I assume that for some reason since some time last night or this weekend the requests seem to come with those headers instead of the original headers for the website. This is really strange but adding these bindings fixed both the staging and production instances and they were available again after this change.