Hi [subramanya.raj, I don’t have an option for global configuration under settings. Tried giving the custom configuration but the shows proxy server 127.0.0.1 is invalid. can you please help? My postman version is : Version 7.21.1
Hey, yes! So this was recent update in the app where the global configuration section was renamed to “Proxy configurations for sending requests”. It does show invalid when you enter “127.0.0.1” - click on port number and that warning should be gone once validated. If you’ve gone through the entire video, which shows settings based on various configurations done by the end-users.
Here is my configuration, do give a try and see if that works
Thanks for following up. Hopefully, the following suggestions may help troubleshoot further. Could you confirm if the local server is running and listening on port 3000 as mentioned in your initial post? ( I’d confirm by attempting to check on the browser to see if it can be accessed )
Also, could you try switching on the Use the system proxy and see if it helps? Screenshot attached for further guidance.
In addition to that, from the attached screenshot - we see you’ve used Port number as 443 - which isn’t your configuration (I believe). Your port number should be 3000 - could you give that a try? Also, retry sending request by selecting “Http” there.
Hi @SabriH, I have tried the above suggestion. Still it didn’t resolve the issue. My server is up and running with the port 3000. Please find the screenshot for the same along with the log and the proxy settings.
HI
I have encountered the same issue. Could you please let me know if you have solved it ?
Tried all the possibilites of the above steps but still the issue exists.
Hi Stephanie, let me tell you what I did :)…I just found another video about the same topic, it’s just more recent, about three weeks ago, it’s call “Build A RESTful Api With Node.js Express & MongoDB” it’s from Can Dev and it works
If you are using nodemon, try running your app with just node instead and see if it resolves it. After the last nodemon update (2.04) I noticed some course examples stopped working (POST/req.body), which was resolved by running the js file straight through node. I switched to npm/supervisor instead of nodemon and everything now works fine.
I too was having a problem following Dev Ed’s tutorial.
Here is what you code probably looks like, and what it SHOULD look like which fixed it (the commented out line)
try {
const savedUser = await user.save();
// The below line fixed it for me! In Dev Ed's tutorial he doesn't send a response!
res.json(savedUser);
} catch (err) {
res.status(400).send(err);
}
Request Headers
