Talk:Custom domains

Wording
In the second number 4:

"4. Put in the comments field that you have changed added the CNAME record,"

I think the word changed should be removed. I would do it myself, but... (By the way, why is this page full protected?) Wynter (talk) 03:03, 26 September 2015 (UTC)


 * Fixed it myself. Wynter (talk) 19:14, 26 September 2015 (UTC)

Turkish first line
Miraheze sitesinde talebiniz üzerine özel alan adınızı (wiki.yourdomain.org gibi) kullanılabilir hale getirebilirsiniz. İhtiyacınız olan tek şey aşağıdaki adımları takip etmeniz ve vikiniz için bir SSL sertifikası almanızdır (SSL sertifikasız, özel alan adsız - https://www.startssl.com/ ve https://letsencrypt.org/ sitelerinden ücretsiz SSL sertifikası alabilirsiniz):

Error. I could not save. --Hersitede (talk) 19:19, 27 October 2015 (UTC)

Wise disclaimer
I haven't got very far yet, but it would be wise to include a disclaimer explaining that D4rkB0t isn't going to support custom domains. D4rkst4r (talk) 21:31, 10 December 2015 (UTC)

I'm not going to make unproductive edits over this...
...But please ask for CNAMEs only. D4rkst4r (talk) 01:30, 13 December 2015 (UTC)
 * If people want to host their DNS with us, they should feel free to.
 * But DigitalOcean just terminated our third DNS server, so yay. Southparkfan (talk) 21:17, 13 December 2015 (UTC)
 * There's no reason to and it's only going to make things harder for the user. This is a reason why it's not a good idea.  D4rkst4r (talk) 23:59, 16 December 2015 (UTC)

Precise instructions for Let's Encrypt (LE)
Now LE is in public beta - anyone can use it - quite likely miraheze users who want to use certificate will use LE.

My issue: and the requested CSR will be emailed to you - the problem is - https://letsencrypt.org/getting-started/ - I have no idea how it relates to LE process...

Potentially miraheze admins can generate the certificate on their own - is that an option at all?

If that's not a feasible option - can you please provide detailed instructions how to use your CSR with LE process?

Thank you
 * Hi, CSR and LetsEncrypt don't jive from what I know. We will prefer to handle LetsEncrypt certificates our side (and we can generate them our side as the domain we are wanting to encrypt is pointed to our servers, which is seemingly the only requirement by LE) as the expiration dates are fairly awkward as they're 90 days as opposed to industry standard 365. I'll work on writing the LetsEncrypt caveats into the page later today but in short, tell us the domain you want for the wiki, tell us it's LE and then we'll do the rest. The CSR part is only relevant for standard certificate authorities who generate their own private and public key and then share them with users, the CSR just means only Miraheze has the private key which restricts the number of people who are able to decrypt traffic to 3 at most. Thanks John (talk) 10:53, 9 March 2016 (UTC)


 * So here is what I want to do... I have a domain genesis.re - it is hosted via GitHub Pages. I also use CloudFlare to enable https:// - I'm pointing my DNS to CloudFlare so the traffic appears encrypted (I know it isn't, connection between CloudFlare and GitHub is not). Wiki is hosted on miraheze - https://gen.miraheze.org/wiki/Main_Page - and I'm using very basic redirect so the https://genesis.re/wiki goes directly to wiki. This is the current state. Ideally I would like to have https://wiki.genesis.re that is pointing to miraheze... That would be ideal. Not sure it if it much work, I'm keen to try. Previous instructions were rather unclear - in the rise of Let's Encrypt there is no need to mention StartSSL so my suggestion was to update the docs. 	--Stefek99 (talk) 16:26, 16 April 2016 (UTC)

Custom subdomain for my wiki
Hi good folks of miraheze!

Done. I have added the CNAME record, and I have sent a mail to csr at miraheze.org Domain: wiki.aenasan.com Wiki page: https://aenasan.miraheze.org/wiki/Main_Page

thanks!