This question is aimed at anyone who has used digital ocean to set up a Ghost droplet
Yesterday I set up a digital ocean ghost droplet, everything went well, however when I used ssh#root to complete the setup, I forgot to add my email to issue the SSL certificate and so the installation failed.
I then deleted the droplet and created a new one, only this time round it says to me that the IP address for me but this IP address is not working.
Am i doing something wrong, can you help me?
Thanks
Once you’ve selected a name for your droplet (this can be anything), Digital Ocean will take a couple minutes to create the droplet. Once the droplet is created, you should see an IP address (for example: 134.209.259.121).
If you navigate to that IP in your browser,{Copy ip address and paste it in browser} you’ll see the below view of the Ghost Installation page, which means the droplet is set up and hosted by Digital Ocean at that IP address. If you don’t see this page, the droplet has not been set up properly. If you do see this page, you’ve set up your droplet and can now connect it to a domain.
Related
I have two sites we'll call Site1.com and Site2.com.
I recently converted my VPS with another host to an image and imported the image into AWS. On the VPS, I was able to serve up both sites. Under AWS, whichever URL is accessed first, the second site will display the content and the URL will change to the first accessed site.
The setup is unique in that it is Windows running an apache web server (very old application). No changes to the conf files have been made since the conversion so I can only assume that it's something unique with the AWS setup.
Why is it doing this and more importantly how can I fix this so that I don't have to spin up a second instance.
Turns out the issue is with the instance type. When I bumped it up to medium (from small), the issue resolved itself. Go figure.
I used Django + nginx + uWSGI to deploy a website to example.com (this is also the hostname of my instance where I put the Django app on Google Cloud Platform) following the instructions here https://uwsgi-docs.readthedocs.io/en/latest/WSGIquickstart.html.
Now here's the strange thing. I found that all devices under my university's WiFi can access my website (http://example.com) but devices outside my network (for example, in another city) cannot access it. Does anyone know what is going on here?
Thank you very much in advance.
Found out where the problem was with the help of my friend.
Turned out I pointed my DNS to two ip addresses and this caused the problem. When people at other places visit my website, they were directed to the other ip which only showed them the nginx welcome page.
Learned a useful command 'ping www.example.com', this helps you identify the ip address associated with www.example.com
Quick overview:
Developed web app with Python and Django; developed and tested locally; adjusted settings to harden for deployment
Deployed app to Heroku for simple hosting platform; tested and worked successfully
Purchased hobby hosting on Heroku so deployed app would not sleep; I can still verify this to be true, the app loads instantly at myappname.herokuapp.com
Purchased domain name on GoDaddy
Used a free CloudFlare account to manage DNS
Entire chain of operation works successfully sometimes, but sometimes I get a website coming soon page:
So when I go to bed last night, everything works. I can load the app from the purchased domain name on all my computers and mobile devices. I wake up this morning, and I'm once again getting the coming soon page. No matter how many times I refresh, and with cache disabled in Chrome so I know it's not my browser.
Everything is working perfectly on the Heroku side, since I can load the app there every single time. Once I told GoDaddy to use Cloudflare's nameservers I think there can't be an issue on GoDaddy's side. There has to be something with Cloudflare.
The DNS settings on Cloudflare are super simple:
CNAME for my.url pointing to my.url.herokudns.com
CNAME for www as an alias of my.url
The hardest part is that it just sometimes works and sometimes doesn't. I can't nail this down.
The only option in DigitalOcean login page is Enter backup code.. which I didn't saved.
The hard thing is, trying to contact Digital Ocean support require me to login. Which is the whole problem.
That's why I ask this here. Or, am I totally shut here?
You should contact Digital Ocean support here: https://www.digitalocean.com/company/contact/
I have two separate rails apps. I'd like to connect them by simply linking them in the header. One is, for example, http://example.com and I'd like the other to be, for example http://different.example.com.
I added the relevant domain to the first heroku app and it's working. I created a subdomain with my domain host, setting the host CNAME to the previously referenced "different." I then attempted to add the subdomain to the heroku app by running the command:
$ heroku domains:add different.example.com
Despite that, it's not working. Any thoughts on what I've done wrong? I followed the instructions from my domain host and on heroku's documentation.
If you made a recent change, it's possible that your connection to the Internet or ISP might be serving you a cached, old version of where you want to go.
Try accessing the site from another entry point such as through a third party like https://crossbrowsertesting.com and then you can rule out this possibility.