Domain now points to domain registrar - maybe it wasn't renewed?

[m-col]

Currently qtile.org looks like this:

So it looks like we need to re-register. To avoid being presumptuous I'll put it out there that I am more than happy to cover the cost of registration.

[tych0]

Yeah, I'm happy to fund it too. I emailed @cortesi, he's been paying since inception. We'll see what he says.

[cortesi]

Hey folks. Apologies for the disruption - I've just renewed the domain for 5 years, and resolution now works. Oddly, the domain was not due to expire for another 2 weeks - I'll dig a bit more to figure out what was going on.

[Lord-Valen]

Hey folks. Apologies for the disruption - I've just renewed the domain for 5 years, and resolution now works. Oddly, the domain was not due to expire for another 2 weeks - I'll dig a bit more to figure out what was going on.

That's odd, because qtile.org still points to Pair.

[tych0]

It does if you use https://qtile.org, but if you use http://qtile.org, you get the right thing. Seems bad that they're hijacking... but shouldn't happen unless people are using https-everywhere style extensions.

[ThatLurker]

The dns A record for qtile.org does not seem to be pointing to heroku, but to the registrar. www.qtile.org is pointing to heroku. Can the qtile.org A record be editet to point to heroku or make it point to the www. record.

[tych0]

Yep, we have plans to rework the DNS with the new website. I'll try to sort it all with cortesi then, thanks.

On Wed, May 10, 2023, at 1:35 PM, Kalle Laine wrote:

The dns A record for qtile.org does not seem top be pointing to heroku, but to the registrat. www.qtile.org is pointing to heroku. Can the qtile.org A record be editet to point to heroku or make it point to the www. record.

— Reply to this email directly, view it on GitHub https://github.com/qtile/qtile.org/issues/41#issuecomment-1542775593, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAF7VVYF3CFFUODOYFED5ZLXFP3ZJANCNFSM5XRKZ2AQ. You are receiving this because you commented.Message ID: @.***>

[elParaguayo]

@tych0 not sure the domain stuff is sorted yet, we're still not getting SSL on the website (people muttering on Reddit...)

[tych0]

Yeah, it's not. Been having a problem getting through @cortesi 's e-mail filters. Maybe someone can ping him on twitter?

[elParaguayo]

I'm not on Twitter. Could any of @ramnes @m-col or @jwijenbergh help here?

[ramnes]

Aldo is a hard man to reach

[cortesi]

Hey folks! Apologies, I dropped the ball here. I'm having a look at this now. @ramnes which app did you try to reach me on? Just want to make sure I don't have a communication issue other than my innate scattiness. :)

[ramnes]

That was a Twitter DM

[cortesi]

@ramnes Hmm - odd. My DMs are open, and I have recent messages from people. This may just be Twitter flakiness, as opposed to Cortesi flakiness.

[cortesi]

Folks, bear with me for a bit. I am transferring the qtile domain from Pair to AWS to make management easier. We should be back up and running shortly.

[elParaguayo]

Not sure if you've manage to make any changes but it doesn't seem to be working yet.

[cortesi]

Folks, the domain transfer completed about an hour ago. I've set up the Github pages domain and changed the name severs over to AWS. We're now waiting for everything to propagate so Github can validate the configuration, then we should be up and running. I'm keeping an eye on things, and will close this ticket once everything is up.

[elParaguayo]

Thanks @cortesi

From what I can see:

• The domain points correctly for http but https isn't working (presumably we need to configure that separately).
• https://docs.qtile.org is not pointing to readthedocs (same for plain http).

[tych0]

Seems like https is working for qtile.org now at least for me. Once the docs page is redirected I think we can finally close this!

[elParaguayo]

I'm still getting an insecure warning:

Firefox does not trust this site because it uses a certificate that is not valid for www.qtile.org.
The certificate is only valid for the following names:
*.github.io, github.io, *.github.com, github.com, www.github.com, *.githubusercontent.com, githubusercontent.com

I can't see any CNAME records on the domain which would explain why docs aren't working. Don't know if that's also needed for https on the main page.

[tych0]

Yeah, you're right. I probably saved github's cert, whoops. I don't see any cnames for qtile.org either:

~/packages/qtile in-line dig +short qtile.org A
185.199.108.153
185.199.111.153
185.199.109.153
185.199.110.153
~/packages/qtile in-line dig +short qtile.org CNAME
~/packages/qtile in-line

[ramnes]

@cortesi We have bunch of people reporting that the docs are down. If that's quicker and that you feel like it, feel free to add me to AWS and readthedocs so that I can fix it. :)

[elParaguayo]

I've got readthedocs access (you should too via your GitHub account) so can make any changes needed. Just need the domain pointing correctly.

[10leej]

So docs.qtile.org is still not resolving and it seems qtile.org is setup with github properly.

What can I do to help resolve this?

[ramnes]

Not much, we're waiting for Aldo, he's a SPOF here :(

[jwijenbergh]

https now works on qtile.org and is enforced (just had to re-apply for the DNS check). docs DNS entry still need to be set up.

Also https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site/verifying-your-custom-domain-for-github-pages should be followed.

Friendly ping @cortesi

[ramnes]

@jwijenbergh HTTPS is down again following the adventures with #49 and #50. What did you do to fix it exactly? Did you delete and create the CNAME again in GitHub settings? If so, I tried it already and it doesn't seem to help, maybe we need to wait a bit and try again in 24h or something.

[jwijenbergh]

@jwijenbergh HTTPS is down again following the adventures with #49 and #50. What did you do to fix it exactly? Did you delete and create the CNAME again in GitHub settings? If so, I tried it already and it doesn't seem to help, maybe we need to wait a bit and try again in 24h or something.

Indeed that's all I did. Just tried again and some weird error about not being able to obtain the cert. Maybe we should host it ourselves it's just a static webpage. But that would need us to be in control of the DNS as well ;)

[elParaguayo]

Hosting on GitHub pages really should work.

There must be something we're missing.

[tych0]

It does @ramnes just fixed it. See git HEAD

[jwijenbergh]

It does @ramnes just fixed it. See git HEAD

It's still broken for me (I'm talking about TLS)

[ramnes]

Yeah GitHub hosting works, but their cert management smells. Let's give GitHub a day or two before we try again, I did a lot of trials today and there's probably a rate limit somewhere.

[ramnes]

Bingo! We now have a valid certificate but for some reason I can't enforce HTTPS. I'll try again in a few minutes and if that still doesn't work, let's wait another 24h, lol.

Edit: that still doesn't work.

[ramnes]

Done, HTTPS is now enforced. We just need to setup the docs.qtile.org domain to point on RTD now. Gentle ping @cortesi :)

[jwijenbergh]

Ping @cortesi

[elParaguayo]

@cortesi Can you please help us address the docs.qtile.org issue?

Ideally, it would be great if you could give someone else in the team access to the domain records so we can move a bit quicker in the future.

Failing that: @m-col @ramnes @tych0 @jwijenbergh we could register a new domain name e.g. qtilewm.org

[ramnes]

Fixed apparently