Page MenuHomeMiraheze

Requesting custom domain for openhatch wiki
Closed, ResolvedPublic

Description

Wiki URL: openhatch.miraheze.org

Your custom domain: wiki.openhatch.org

Do you want Let's Encrypt: Yes

P.S. <3 you folks are amazing

Related Objects

Event Timeline

I've now pointed it! Cheers.

paulproteus@slittingmill:~$ dig wiki.openhatch.org

; <<>> DiG 9.10.3-P4-Debian <<>> wiki.openhatch.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41277
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;wiki.openhatch.org.		IN	A

;; ANSWER SECTION:
wiki.openhatch.org.	299	IN	CNAME	mw-lb.miraheze.org.
mw-lb.miraheze.org.	149	IN	A	107.191.126.23

;; Query time: 348 msec
;; SERVER: 192.168.86.1#53(192.168.86.1)
;; WHEN: Sat Aug 11 23:29:51 PDT 2018
;; MSG SIZE  rcvd: 92

For now, there's a HTTPS error, and also it redirects to meta.miraheze.org:

paulproteus@slittingmill:~$ wget --no-check-certificate -O/dev/null https://wiki.openhatch.org 
--2018-08-11 23:32:50--  https://wiki.openhatch.org/
Resolving wiki.openhatch.org (wiki.openhatch.org)... 107.191.126.23, 2604:180:0:33b::2
Connecting to wiki.openhatch.org (wiki.openhatch.org)|107.191.126.23|:443... connected.
The certificate's owner does not match hostname ‘wiki.openhatch.org’
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://meta.miraheze.org/wiki/ [following]
--2018-08-11 23:32:50--  https://meta.miraheze.org/wiki/
Resolving meta.miraheze.org (meta.miraheze.org)... 107.191.126.23, 2604:180:0:33b::2
Connecting to meta.miraheze.org (meta.miraheze.org)|107.191.126.23|:443... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://meta.miraheze.org/wiki/Miraheze [following]
--2018-08-11 23:32:52--  https://meta.miraheze.org/wiki/Miraheze
Reusing existing connection to meta.miraheze.org:443.
HTTP request sent, awaiting response... 200 OK
Length: 28981 (28K) [text/html]
Saving to: ‘/dev/null’

/dev/null                  100%[======================================>]  28.30K  --.-KB/s    in 0.06s   

2018-08-11 23:32:52 (468 KB/s) - ‘/dev/null’ saved [28981/28981]

Perhaps this will self-heal once your Let's Encrypt infrastructure verifies the domain? If so, awesome.

Reception123 claimed this task.

Done :)