open-next.js.org

[jayair]

• There is reasonable content on the page (see: No Content)
• I have read and accepted the Terms and Conditions

[MattIPv4]

Hi there!

❌ Before we can accept your domain request, you need to create a file named CNAME in the root of your github pages site (this may not be the root of your repository). 📝
This file should contain a single line with the full js.org domain you are requesting, in this instance open-next.js.org.

[jayair]

Oops! Fixed.

[indus]

I've already added your requested subdomain to JS.ORGs zonefile. But you have to (re-)add a file named CNAME to your branch with the single line alova.js.org to make it work. As you are using a workflow to deploy the page there may be other steps involved.

[jayair]

@indus Oh does changing it through the UI help btw?

[indus]

Doesn't seem so. I'm getting a too many redirects error?! We had these issues with workflows in the past a couple of times. But requesters usually solved them...Am 04.12.2022 01:04 schrieb Jay ***@***.***>: @indus Oh does changing it through the UI help btw? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[indus]

Just tested - no I'm getting 404 again: https://open-next.js.org
Maybe this is some help: #7666 (comment)

[jayair]

@indus yeah I tried that too and I think it works!

For anybody that comes across this. I think you need to do the default GitHub pages deployment with the custom domain set. That gets it setup. You can then flip it back to the GitHub actions deployment.

[indus]

Welcome https://open-next.js.org

Thanks for the hints on how to solve this.