Page MenuHomeMiraheze

Cornetto Online
Closed, ResolvedPublic

Description

Wiki URL: cornetto.miraheze.org

Your custom domain: cornetto.online

Do you want Let's Encrypt: Yes

Event Timeline

Hi folks,

The wiki is created, the DNS did propagate as required, please do what is still needed to activate our custom domain with SSL :-)

Thanks, your volunteer work is great!

@Crepitus Sorry for the delay!

@John I checked and the domain is pointing to us, I added the zone but the cert does not want to generate.

Generating SSL certificate with LetsEncrypt
Parsing account key...
Parsing CSR...
Registering account...
Already registered!
Verifying cornetto.online...
Traceback (most recent call last):
  File "/root/acme-tiny/acme_tiny.py", line 201, in <module>
    main(sys.argv[1:])
  File "/root/acme-tiny/acme_tiny.py", line 197, in main
    signed_crt = get_crt(args.account_key, args.csr, args.acme_dir, log=LOGGER, CA=args.ca)
  File "/root/acme-tiny/acme_tiny.py", line 126, in get_crt
    wellknown_path, wellknown_url))
ValueError: Wrote file to /var/www/challenges/aCPBd0eswe3PzWsvXHOzoejyiWz7mm5migtCgHdNUyI, but couldn't download http://cornetto.online/.well-known/acme-challenge/aCPBd0eswe3PzWsvXHOzoejyiWz7mm5migtCgHdNUyI

URL works for me. Might want to do a host lookup on the domain from mw1 and just keep trying

I tried again; unsuccessful.

And there seems to be no issue to ping from mw1.

I said host on the domain. mw1 might not be having it locate corrrctly. It works my end so the issue is mw1

Reception123 claimed this task.

@John Even after I repooled mw1 twice on cp* apparently it was still marked as down until a few minutes ago. The issue is now fixed.

@Crepitus Done!

Reception123 mentioned this in Unknown Object (Diffusion Commit).Mar 24 2018, 14:12

Hi guys sorry I have to reopen this task ; Most of my request at https://cornetto.online end up redirected to https://meta.miraheze.org/wiki/Miraheze ; It seems maybe one of the servers is aware of our custom domain, but not the others.

Thanks for your help!

@Crepitus Yes, you are right. One of the servers was experiencing a minor issue, and therefore the change didn't go through. I've fixed the issue now, and the domain should now be working as expected. Sorry for the inconvenience!