Callback URL problem in production when using oauth about authentication-oauth2 HOT 4 CLOSED

If you set NODE_ENV=production it will always load production.json. Are you sure the NODE_ENV environment variable is set to production?

from authentication-oauth2.

Yes, I am absolutely sure. To complete the technical information above I am using PM2 to run the node instance with the following ecosystem.json
{
"apps" : [{
"name" : "myapp",
"script" : "src/index.js",
"env": {
"NODE_ENV": "development"
},
"env_production" : {
"NODE_ENV": "production"
},
"env_staging" : {
"NODE_ENV" : "staging",
"TEST" : true
}
}]
}

The environment is set to production and the log says it is running at the host as defined in production.json. However, callback of github (and facebook) goes wrong if the host is not set in default.json too. Somehow the callback URL is generated from default.json. I am quite sure about this.

from authentication-oauth2.

What does the console output on the server look like when setting DEBUG=feathers:configuration?

from authentication-oauth2.

Ok, I had the same problem again with a new app. Ran in production mode, but the host was taken from default.json. Changed the default.json host to the production parameter. Then back to localhost. After that, it all worked. Debug output was also normal. Tried to reproduce it with a newly created test app. Wasn't able to reproduce the error with that. I have no clue what went wrong. Maybe close the issue. I will request a reopen if I ever find out what the problem was.

from authentication-oauth2.