Member IP addresses show as Digitalocean IP address?

  • Posted September 28, 2014

My members all have the same IP address when i view the logs, which is the same as my server’s IP address.

I set-up a forum on Ubuntu 14.04 x64 and installed apache, fail2ban, and a few other programs recommended in the tutorials. I also installed VestaCP.

I must have messed up some dns setting along the way because I’m unable to figure out HOW my members are all showing up as using the same IP address, which is conveniently the server’s IP address.

My domains both point towards the same droplet. I have the A record as @ and the droplet IP address The CNAMEs are WWW @ and * @ The NS records for both are

Both domains are hosted with godaddy and point at the nameservers listed for digitalocean.

I am a complete noob and need help because banning spammers isn’t going to work if everyone has the same IP address…

Thanks in advance for any help!


Are you running nginx as a reverse proxy by any chance? What’s the output of the following command?

sudo netstat -plutn | grep -E "nginx|apache|80" Imgur Image attached of the output!

Sorry, I do not believe I did but with me being new I would not doubt I could have done something like that? I mainly followed the basic installation tutorials and then installed VestaCP

Thanks for responding.

Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

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.


As mentioned before, this seems like Nginx is being used as a Reverse proxy. What you can do to confirm this is SSH in your Droplet and type in the following command:

netstat -tulpen | grep -E "nginx|apache|httpd|80"

It will show you what’s running on port 80 or if there are any Nginx or Apache services running. If you then want to see the IP addresses, I’ll recommend checking the Nginx access logs as the information would be relayed there.

Regards, KDSys

This comment has been deleted