New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Domain won't see project 1 #10

gjrett opened this Issue Feb 10, 2019 · 3 comments


None yet
3 participants
Copy link

gjrett commented Feb 10, 2019

Greg Retter - I went through all the homework and videos, and everything seems to have worked fine. I finished project 1, pushed it to GitHub, pulled it to my digital ocean server and saw the updated files in the /var/www/html directory, but my domain doesn't see them. The domain sees the digital ocean and shows the basic index.html page, but I can't seem to get it to see the project index.php. I've tried matching my droplet name to my domain, but that changed nothing. My droplet is configured as the default, but it looks like it is not pointing to /var/www/html, which is where my files are located. Is there a configuration file that need the /var/www/html path set, or did I somehow miss that part?



This comment has been minimized.

Copy link

susanBuck commented Feb 11, 2019

To help you debug, can you share the following:

  1. The full contents of your production server's virtual host file (/etc/apache2/sites-enabled/000-default.conf)
  2. A screenshot of your DNS settings
  3. The domain you're using

This comment has been minimized.

Copy link

llandau commented Feb 11, 2019

My understanding is that after following the instructions, the domain is expected to show the "basic index.html page" (or maybe the hello world page). The subdomain p1.domain is where the project will be. You should be able to check if domain/p1 is working to show the project 1 files. That should also work. Then if that's working you should be able to setup the subdomain per the instructions here


This comment has been minimized.

Copy link

susanBuck commented Feb 12, 2019

@gjrett noted in Slack that he re-did the process and it's working now, so closing this issue.

@susanBuck susanBuck closed this Feb 12, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment