Few months left

Thank you!

Same for miraheze.com so this is done.

miraheze.wiki renewed by me.

m.miraheze.org renewed per SAL by @Paladox

Any status? This has been here for 6 days

This was being tracked by icinga, which triggered me. So it should either 1. remove it from the icinga tracking or 2. tell them to move off Cloudflare.

Even more proof.

Fixed in https://github.com/miraheze/puppet/compare/5e391443f8ed...a24ef09373fc

No it's not. SAN exists.

Yes, of course. But as I said that puts double the work for renewing.

You can very easily generate a cert for both {domain} and www.{domain}

As I said before, I think that adding a www. for each new wiki is not doable, as that would mean that we'd have to renew twice the amount of certs. IMO this is blocked until T1849 is done.

@Wiki1776 Yes.

A doubt in the case of being done. If I were to request a wiki with the union.miraheze.com domain, wouldn't it conflict with union.miraheze.org? Github: unionwiki and unionwiki?

Yes.

@John Kind of late, but does this mean that if I create (for example a-b.miraheze.org as abwiki) and add it to wgServer, etc. it will work as a-b.miraheze.org?

There’s nothing to advertise. If someone wants a-b.miraheze.org or a.b.miraheze.org, it can be done. The latter is more annoying but nothing stops it happening.

Yes, we can do it technically, but I'm talking about if we should explicitly advertise it or not.

This is moot. You can do this by assuming it’s a custom domain.

I like this idea, but I've always wondered, why is it not possible to do this with the usual .miraheze.org wikis? It would be easier than having to use .wiki and .com

Another complaints with www. not available:

In T2496#47218, @revi wrote:

We should default to bundle www. when generating TLD domain cert, or any certification imo.
It should be done via SAN field.

But then the ticket is mostly aimed at all wikis. Which we can’t do that for.

We should default to bundle www. when generating TLD domain cert, or any certification imo.

Clearing yours wouldn’t, you’d have to clear cp*

Confirm it works now. Likely a cache issue, though at the time clearing my cache did not fix this error.

It’s woring for me.

Without logs all I can suggest is:
a) cache
b) not deployed correctly?

@John This is redirecting to Meta for some reason. I definitely made the mw-config changes after. I tried reloading NGINX, checked config but I can't figure out what is going wrong. (revi confirms that it also redirects to Meta for him)

Issues with redirecting.

@Reception123 Great, thanks! The name servers for our domain have been updated.

@Hamled The DNS records have been created.

Try clearing your cache

wiki.autocountsoft.com didn't resolve to autocount.miraheze.org, instead it resolved to meta.miraheze.org/wiki/Miraheze. After checking if I do wiki.autocountsoft.com/wiki it will resolve properly. Is it suppose to work like this?

@labster Sure thing. I think I'm going to make an "orain.org" section on redirects.yaml at this rate.

From robkelk:

https://github.com/miraheze/dns/pull/55 adds DNS

Not a DNS ticket + null ticket.

resolved with https://github.com/miraheze/puppet/commit/94ae474692de553b232ae9f980139e0f30f0a2ce

Sorry for the re-open the task, but it seems there should be something wrong with SSL, not pointing out wiki.besuccess.com, but previous 2nd domain startups.miraheze. Please re-check this!

I've just checked the new domain has been set properly.
Thank you so much for your help.

In T1609#29441, @John wrote:

The domain should start resolving to that wiki in the next 10 minutes.

The domain should start resolving to that wiki in the next 10 minutes.

In T1609#29438, @John wrote:

Please do not continue to change priority of this issue.

Please do not continue to change priority of this issue.

@alfster2012 Thank you. Your certificate and redirect should be set up soon.

Ill disable it for now

It seems proxied through CloudFlare. Which means the domain doesn't resolve and therefore the verification token can't verified.

Not exactly sure what the error is but I can't generate a cert

Lets encrypt will be absolutely fine (I'm using cloudflare anyways)

@alfster2012 Do you want a LetsEncrypt certificate (we generate it, you don't need to do anything)?. If you would like to generate a cert yourself issued by a different registrar please find a new CSR below: