You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes, the configuration is correct. I added to the end of the string &ssl=true and it's working.
Also in db.js there should be an output to let the user know that the server is running, a console.log at least because sometime, since there is no output, it seems that the connection to db goes in timeout
Great. Did you add it to the end of the mongodb connection String?. Today i tried running the backend server again, i am having the same issue right now.
@LuigiElleBalotta@SamuelOjes
i solved this problem by allowing node.js to communicate through windows defender firewall.
go to this address in control panel :
" Control Panel >> Windows Defender Firewall >> allow an app or feature communicate through windows defender firewall"
and check both private and public checkbox for "node.js:Server-side JavaScript" and run your command again.
Hey guys, I had the same problem and I followed what @LuigiElleBalotta said, I added &ssl=true at the end of the string and console logged hi, and it's working! thank you so much you saved my day.
Activity
SamuelOjes commentedon Aug 3, 2020
Make sure you check properly, your MONGODB connection string in your .env file to see if you entered your password, email and database name correctly
LuigiElleBalotta commentedon Aug 4, 2020
Yes, the configuration is correct. I added to the end of the string &ssl=true and it's working.
Also in db.js there should be an output to let the user know that the server is running, a console.log at least because sometime, since there is no output, it seems that the connection to db goes in timeout
SamuelOjes commentedon Aug 5, 2020
Great. Did you add it to the end of the mongodb connection String?. Today i tried running the backend server again, i am having the same issue right now.
LuigiElleBalotta commentedon Aug 5, 2020
Yes at the end!
And put a console log inside the db connection function inside db.js for making sure that the connection was successful
SamuelOjes commentedon Aug 5, 2020
Thanks. Think it has to do with some isp and mongodb err. Still having the issue, it worked yesterday though
SamuelOjes commentedon Aug 5, 2020
Thanks it working already, i used a different mongodb connection string, from mongodb and selected Nodejs Version 2.22.
mojtabamaslahatbin commentedon Aug 6, 2020
i have same problem to start the backend api :(
mojtabamaslahatbin commentedon Aug 6, 2020
@LuigiElleBalotta @SamuelOjes
i solved this problem by allowing node.js to communicate through windows defender firewall.
go to this address in control panel :
" Control Panel >> Windows Defender Firewall >> allow an app or feature communicate through windows defender firewall"
and check both private and public checkbox for "node.js:Server-side JavaScript" and run your command again.
Zainab98Azzam commentedon Aug 9, 2021
Hey guys, I had the same problem and I followed what @LuigiElleBalotta said, I added &ssl=true at the end of the string and console logged hi, and it's working! thank you so much you saved my day.