nertzy
nertzy

@help I am trying to migrate my WordPress site to micro.blog. I've successfully migrated my posts. I'm trying to point my custom domain to micro.blog and it keeps telling me I need to wait for DNS to propagate. I've already updated my DNS and now if I visit my blog, I get a "not found" message that I assume is coming from micro.blog servers. Is there anything I can do other than wait and try again?

Also, some feedback: It would be great if I could set my hostname even if the DNS hasn't propagated yet. That way, I can keep my previous site live and my site won't have downtime as various DNS servers update. There could also be some sort of UI element afterwards that lets me know whether the DNS propagation has succeeded.

|
Embed
nertzy
nertzy

@nertzy One more thing... I think the problem I’m running into is that I’m using Cloudflare for my DNS. They are proxying requests through their caching layer, and thus they provide a public-facing A record that points to them. So even though they are eventually sending requests along to micro.blog, the outside world can’t see the (internal-facing) CNAME record they use within the proxy. So naturally, y’all can’t detect my DNS setup.

|
Embed
nertzy
nertzy

@nertzy @help An update: I was able to get things working by temporarily disabling Cloudflare. I would just turn it off permanently, but there doesn't seem to be a way to disable Cloudflare for just one domain, unfortunately. I'm hoping the HTTPS certificate generation goes smoothly. If not, is there a way for me to upload my own certificate?

|
Embed
help
help

@nertzy Thanks, glad it's working now, and HTTPS should be working too. This is definitely an area that could use some improvement. If you notice any problems, let me know!

|
Embed