Len-goo-uh
Application Failed To Respond 503 Error
Turns out it was an issue with the front end. It was pointing to a recently expired domain, after removing it and redeploying the front end code everything started working again. Turned out to be a simple fix thankfully. Thanks for all your help
36 replies
Application Failed To Respond 503 Error
Sure, it looks like most of the variables i showed you aren't used in the project itself. Here is my config.ts file showing some of the key ENV vars declared. I can also show my server.ts file if you want too.
export const PORT = process.env.PORT ?? 3000;
export const NODE_ENV = process.env.NODE_ENV as string;
export const DOMAIN_SERVER =
${NODE_ENV === 'production' ?
${process.env.DOMAIN_SERVER as string} : 'http://localhost:3000'}
;
export const DOMAIN_CLIENT = ${NODE_ENV === 'production' ?
${process.env.DOMAIN_CLIENT as string} : 'http://localhost:3001'}
;
export const MONGODB_URI = process.env.MONGODB_URI as string;
export const REDIS_HOST_URI = process.env.REDIS_HOST_URI as string;
export const EXPESS_SESSION_SECRET = process.env.EXPESS_SESSION_SECRET as string;
export const JWT_SECRET = process.env.EXPESS_SESSION_SECRET as string;
export const OAUTH_CALLBACK_URL = ${NODE_ENV === 'production' ?
${process.env.DOMAIN_SERVER as string} : 'http://localhost:3000'}
;
export const PATH_LOG_ERROR_FILE = process.env.PATH_LOG_ERROR_FILE ?? 'request.log';
export const PATH_LOG_REQUEST_FILE = process.env.PATH_LOG_REQUEST_FILE ?? 'error.log';
export const FB_PIXEL_ID = process.env.FB_PIXEL_ID as string;
export const FB_CONVERSIONS_API_ACCESS_TOKEN = process.env.FB_CONVERSIONS_API_ACCESS_TOKEN as string;
export const GRAPH_API_VERSION = process.env.GRAPH_API_VERSION as string;36 replies
Application Failed To Respond 503 Error
wdym? Like this? Here is a portion of the ENV, this is how some things are declared, everything else is sensitive information.
MONGOHOST=${{prod-MongoDB.MONGOHOST}}
MONGOPASSWORD=${{prod-MongoDB.MONGOPASSWORD}}
MONGOPORT=${{prod-MongoDB.MONGOPORT}}
MONGOUSER=${{prod-MongoDB.MONGOUSER}}
MONGO_URL=${{prod-MongoDB.MONGO_URL}}
NODE_ENV=${{shared.NODE_ENV}}
NODE_OPTIONS=${{shared.NODE_OPTIONS}}
PATH_LOG_ERROR_FILE=request.log
PATH_LOG_REQUEST_FILE=request.log
REDISHOST=${{prod-Redis.REDISHOST}}
REDISPASSWORD=${{prod-Redis.REDISPASSWORD}}
REDISPORT=${{prod-Redis.REDISPORT}}
REDISUSER=${{prod-Redis.REDISUSER}}
REDIS_HOST_URI=${{prod-Redis.REDIS_URL}}
REDIS_URL=${{prod-Redis.REDIS_URL}}
36 replies
Application Failed To Respond 503 Error
I'm at a loss here. Like i said earlier, everything was migrated over just fine and my project has been up and running the past few months without issue. This issue im seeing is recent. I guess i'll have to just poke around more.
36 replies
Application Failed To Respond 503 Error
I made sure to note down my old database variables and there doesn't seem to be any of those referenced anywhere in the project to my knowledge.
Because last week the project was up just fine, i found out today that it was down so something happened.
36 replies
Application Failed To Respond 503 Error
oh that's strange, I thought that had already been updated. I had it automatically done a few months ago when i got the warning about the databases.
What connection details should I be looking at? It looks like the mongo details are all up-to-date.
36 replies
Application Failed To Respond 503 Error
Yeah, so I updated my server to follow the host and port example for node/express and merged it into may main branch and all I see in the deploy logs is:
Start on port: 5705
Error: connect ECONNREFUSED 34.82.27.207:5876
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16) {
errno: -111,
code: 'ECONNREFUSED',
syscall: 'connect',
address: '34.82.27.207',
port: 5876
}
Connect to mongoDB
I'm still seeing the "Application failed to respond" page when going to my site. And the inspector still shows the 503 error. I tried re-deploying and it and no luck with that either.
36 replies