POST route not found at production server

[wtaiatella]

In my project I'm using express 4.18.1 and for some reason there are some routes that are not working when I deploy the project at the production server. At local host all the routes work perfectly.

The project has the the /user route with these methods:
router.post('/login', async (req, res) => {...}
router.post('/register', async (req, res, next) => {...}
router.put('/recoverypassword', async (req, res) => {...}
router.put('/update', async (req, res) => {...}
router.put('/updatepassword', async (req, res) => {...}

It's weird because at localhost, ALL the routes work perfectly and at the production server the POST method doesn't work and I got the following answer when testing with Insomnia:

NotFoundError: Route not Found
    at eval (webpack://mercado-do-malte-api/./src/routes/user.ts?:142:10)
    at Generator.next (<anonymous>)
    at /var/www/mdm-api/node_modules/tslib/tslib.js:118:75
    at new Promise (<anonymous>)
    at Object.__awaiter (/var/www/mdm-api/node_modules/tslib/tslib.js:114:16)
    at eval (webpack://mercado-do-malte-api/./src/routes/user.ts?:141:41)
    at Layer.handle [as handle_request] (/var/www/mdm-api/node_modules/express/lib/router/layer.js:95:5)
    at trim_prefix (/var/www/mdm-api/node_modules/express/lib/router/index.js:328:13)
    at /var/www/mdm-api/node_modules/express/lib/router/index.js:286:9
    at Function.process_params (/var/www/mdm-api/node_modules/express/lib/router/index.js:346:12)

My server is up and running at Linode and configures with Ubuntu and Nginx web server.
The API address is https://api.mercadodomalte.com.br/
This project is at my repo: https://github.com/wtaiatella/mercdomalte-backend

Can someone help me, why does the POST method only work at localhost?

[krzysdz]

Which route doesn't work? I can make POST requests to your API just fine.

[wtaiatella]

@krzysdz , just looking at your window I notice that my Production Enviroment variable of Insomnia is set to Http:// instead Https://.

Now it's working, thanks a lot, o loose a long time because of it....
But the strange thing is that it is the same enviroment variable that i use for the GET and PUT method.
Why only POST refused to answer?

[suman313]

Hi,
In your schema file, have you connected to the database which is hosted online (which you are using in production) ?
I think PrismaClient cannot connect to the database in production and that is the reason register and login method are not working.

[wtaiatella]

@suman313 , I changed the .env file to connect at the production database and Prisma is connecting to it correctly. I confirmed it using GET method.