How would you feel if you can't solve your code? I'm almost a week stuck on a server problem. I applied for frontend dev position, it's okay for me to do this kind of stuff but the fact that I can't solve it for so long it makes me feel down :(

I would ask for help before i've been stuck for that long.

Apart from asking around, keep a detailed log of everything you have tried and observed, what work as it should, and what doesn't.

By keeping a detailed log, you force yourself to be exhaustive, and often find yourself having questions, which leads to more questions, and after a while, the root cause of your problem.

It's also very handy to discuss the problem with peers, as you can show you didn't sit around and correctly explain the problem with examples.

@nahson this is my stackoverflow question https://stackoverflow.com/questions.... First time to configure nginx, I'm not sure if I'm doing it right. Thank you in advance for your help!

Thank you guys on your advice's, all of you are much appreciated!

This reminds me of the first time I set up Apache server and I kept wondering why I was getting a 403 or 500 error and then finally realized my permissions were off for the /var/www directory. Simple chmod and it was solved. Of course I had no idea how to do this when I started and searching on the internet mainly lead to archives of listserves but the same methodology works. Look at logs, find errors, search for errors and then try to figure out if someone else had fixed that sort of problem already. It seems like you are stuck at the white screen of empty that happens before you find the errors. Find the logs or create the errors that show you what isn't working. Also double check your syntax, I always find I am missing some random character when these types of no error errors occur.