Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
"Cannot GET" on reverse proxy via Nginx to socket.io Question Question
Move URL with redirects in Nginx Question Question

Question

Error on setup + Domain clarification

Posted July 11, 2015 2.6k views
NginxNode.js

Well, first and foremost, I’m new to this whole thing. I have no background on this type of thing, so if you are able to help me, give it to me like a 5th grader.

Moving on, I purchased a DO server yesterday and installed nodebb. It worked absolutely fine. Then I wanted to use my domain instead of the IP address. After Googling, I found out that I needed to use nginx. Without thinking, I installed nginx in the same directory as nodebb which just made everything blow up on my end. So I wiped the droplet to start over. Since then, I’ve had an issue on reinstalling nodebb as it continuously give me this error:

hwPa5PW.png

For reference, I used this guide for setup

I’ve read this thread in regards to the issue, the only thing is that his error is “sadd” and not “zadd” so I’m not sure of the difference it makes there.

Secondly, when installing nginx, I’m assuming I need to make a directory for it and install it into there correct? I’ve created an A Name on my domains end to point to the IP address, shown below:

JUZjSvQ.png

On top of that, I know nginx is used to listen for the command my domain is sending and then I’m supposed to create a DNS record (idr the reason why) but just making sure I’m going in the right direction.

Add a comment
Victoryoftheppl
By:
Victoryoftheppl

Related

Join the DigitalOcean Community Community

Join 1M+ other developers and:

  • Get help and share knowledge in Q&A
  • Subscribe to topics of interest
  • Get courses & tools that help you grow as a developer or small business owner
 Join Now
"Cannot GET" on reverse proxy via Nginx to socket.io Question Question
Move URL with redirects in Nginx Question Question

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
2 answers
ForYourIT July 11, 2015

Welcome to digital ocean and good to have you here even though you are new to this, learning is a good thing ;).

Now how you can find out what the problem could be, is to check what you did different this time. I understand you deleted your droplet, created a new droplet and then installed nodebb?

You have correctly created an A record in your DNS. Nginx will listen to this servername if you use the correct configuration in your vhost. Now you don’t need to create a directory for your nginx since this will all go automatically. When you use the sudo apt-get install nginx command, nginx will create its own directory in /etc and will create its default files.

If you are still running into problems after this, and some googling, give some more information about your droplet and what you did / error logs etc.

Reply Report
  • Victoryoftheppl July 11, 2015

    Well, I wasn’t sure (and still not sure) if I deleted the droplet, wouldn’t I be charged again to create a new one? What I did do was rebuild it, based off what the website said, I thought it’d essentially give me a clean slate. The only thing that was done differently was that I had used Ubuntu 12.04.5 x32 and not Ubuntu 12.04.5 x64. Which when I did do another rebuild, I switched back to what I had used the first time and there was still the same error. Other than that, everything was done the same.

    Reply Report
ForYourIT July 12, 2015

You won’t get charged with a $5 imediately, your bills get generated per month and per usage. So for example if you got your droplet running 24/7 it would cost more a month then wehn you run it 12/7. Anyway a rebuild should work, but I recommend x64. Most of the linux software gets made for x64 and if you chose a 32 bit one, certain packages could not work.

Did you install the base software stack? 

sudo apt-get install git nodejs nodejs-legacy npm redis-server imagemagick build-essential
Reply Report

Related

Looking for something else?

Ask a new question Search for more help