Closed dead-claudia closed 2 years ago
cc @nodejs/tsc I don't know if this is configuration issue in this repo or in my dns config...
According to GitHub, it's a DNS issue:
Thanks! Changed the config. Hopefully it will help.
@indutny Still showing 404. Been 5 days, so I'm pretty sure DNS changes should have already propagated by now.
Weird! This is how DNS records look like on my end:
Note that I couldn't do CNAME for llparse.org
(dnsimple doesn't let me), so I used ALIAS. Strangely the same ALIAS appears to be working for llhttp.org
I tried to force-push main (without changes), but nothing happened. Then I merged https://github.com/nodejs/llparse/pull/47. Now the site is back up.
Okay, can confirm it's up now.
Awesome. Thanks y’all!
On Wed, Feb 2, 2022 at 09:54 Claudia Meadows @.***> wrote:
Closed #48 https://github.com/nodejs/llparse/issues/48.
— Reply to this email directly, view it on GitHub https://github.com/nodejs/llparse/issues/48#event-5997649758, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAB2HQ6OIBDNINJD5JMBNL3UZFVVJANCNFSM5M2B47RA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>
https://llparse.org/ currently returns a 404.