abcd_z
By:
abcd_z

Created Wordpress application droplet. Can't access wordpress from IP address.

September 26, 2014 3.6k views

I created a Ubuntu 14.04 droplet with Wordpress preinstalled. I don't have it connected to any domain name yet. The one-click tutorial indicates that you can access wp-admin by typing in the IP address, but when I try to access http://IP_address, my browser just says, "403 Forbidden. You don't have permission to access / on this server."

When I try http://IP_address/wp-admin/, I get a 404 not found.

1 comment
  • Okay, I created a new droplet with a different IP address and that fixed it. Not sure what the problem was, but it's not my problem now.

1 Answer

have you gone through the wordpress set up yet? or is this right after the one click install?

  • This is right after the one click install. I can't access anything Wordpress-related. Where it should ask me for my password and login (I think?) it just says 403: Forbidden.

    I also created a ticket about this and the person who responded to me is unable to duplicate the problem. I'll follow his advice and create a new droplet to see if that solves the problem.

    EDIT: That did not solve the problem.

    EDIT2: Okay, the second droplet had the same IP Address as the first one. I created a third droplet without destroying the second one to force a different IP address and that solved it.

  • it looks like you are blacklisted to access that ip address of the first droplet, that's why when you create that second with different ip you had no issues.

  • The support staff saw the same thing I did on that droplet. He just couldn't replicate it with another droplet. I originally thought he couldn't see the problem, but that was a misunderstanding on my part.

    Since the official Digital Ocean staff member saw the same thing I did, didn't mention a blacklist, and couldn't immediately fix the problem at that IP address, it seems unlikely that there was a blacklist in play.

    Not impossible, just unlikely.

  • "Okay, the second droplet had the same IP Address as the first one. I created a third droplet without destroying the second one to force a different IP address and that solved it."

    This one was the solution to my problem, thanks :D

Have another answer? Share your knowledge.