Question

custom domain shows wrong page( 1 click ghost blogging)

Associated domain mapped : meliodus.org

My domain is suppose to show ghost blogging( 1 click app), instead it shows me an page saying :

Please log into your droplet via SSH to configure your Ghost installation. Ghost on DigitalOcean Documentation

As far as i know all my configurations are ok. I logged into droplet using ssh, changed /etc/nginx/site-default/ghost server_name to meliodus.org

added a new block

server {
    listen 80;
    server_name www.meliodus.org;

    return 301 $scheme://meliodus.org$request_uri;
}

changed my ghost config /var/www/ghost/config.js

production url to meliodus.org

added A record @ pointing to droplet floating ip added A record www pointing to droplet foating ip

all pages, admin panels etc works fine under the domain meliodus.org.

example : meliodus.org/sample , meliodus.org/author/sample, meliodus.org/ghost works

but meliodus.org page show an error page or you might say wrong page as described above.

I have tried from different computer, cleared all caches etc. Nothing work. Please help me guys.

Submit an answer
Answer a question...

This textbox defaults to using Markdown to format your answer.

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

Sign In or Sign Up to Answer

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.

meliodus • November 1, 2016
Accepted Answer

Problem auto resolved with ctrl+shift+r and all the other devices started showing the correct page. I don’t know how and why. Previously it didn’t worked.

    Ryan Quinn
    DigitalOcean Employee
    DigitalOcean Employee badge
    • November 1, 2016

    It appears your domain is no longer showing the “please log in” page. Can you share your solution in case others encounter the same problem?

    In general, logging in via ssh the first time should make that page go away unless it was cached locally (if you’re still seeing it, this is likely the case). If you had to take other steps, let us know so we can get this addressed in the image.