proxy-memoize.js.org

[dai-shi]

Add proxy-memoize

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

[indus]

I've already added your requested subdomain to JS.ORGs zonefile. But I'm getting a redirect error. This may be result of a incorrect workflow. Could you try to remove and re-add the CANME (maybe by using the repo settings).

It lookssimilar to #8284 where we had the same error for a page that used a workflow to deploy (@MattIPv4 🤷‍♂️)

[dai-shi]

I'm trying but still no luck yet.

[MattIPv4]

Yeah -- I wonder if something has changed on GitHub's end. I imagine someone just needs to reach out to support to see what they say.

[indus]

@dai-shi would you mind to open a support ticket?

[dai-shi]

Done!

[dai-shi]

Here's a response from GitHub support.

It looks like you've set up your domain's DNS with Cloudflare. Cloudflare enables their HTTP/DNS proxy feature by default, meaning GitHub isn't able to see the DNS records required to generate an HTTPS certificate. You'll need to disable this for any DNS records that point towards GitHub.

Disclaimer: Disabling the HTTP/DNS proxy may interfere with other Cloudflare services. If you use other Cloudflare services with your site, we aren't able to guarantee that these will continue working. For more help with this, I'd recommend reaching out to Cloudflare's support team.

If you'd still like to continue, you can follow the instructions below:
...

[MattIPv4]

Yikes, why are they suddenly requiring the proxy be disabled... that seems wrong.

I would push back and say that the Cloudflare proxy normally works just fine for GitHub Pages, and it seems like an issue on their end that it isn't working now suddenly -- we don't expect/need them to generate an HTTPS certificate, Cloudflare handles that.

[MattIPv4]

Feel free to CC me in if you want: [email protected] should work

[indus]

@dai-shi just one question besides the gh support thing: Have you checked the "Enforce HTTPS" option in you repo settings?

By default it is unchecked but enabling it could be a reason for the issue as well I guess...

[dai-shi]

It is checked by default, and can't be unchecked.

[indus]

Is it possible to remove the custom domain - uncheck it and re-add the domain afterwards?Am 10.06.2023 23:51 schrieb Daishi Kato ***@***.***>: It is checked by default, and can't be unchecked. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[dai-shi]

Well, without custom domain I still can't uncheck it...

[dai-shi]

Good news. I was able to uncheck "Enforce SSL" with changing the source to Deploy from a branch. And, then changing it back to GitHub Actions while keeping the option unchecked. Now, the infinite redirect is gone.

[indus]

Perfect. I will merge your request tomorrow...Am 11.06.2023 00:31 schrieb Daishi Kato ***@***.***>: Good news. I was able to uncheck "Enforce SSL" with changing the source to Deploy from a branch. And, then changing it back to GitHub Actions while keeping the option unchecked. Now, the infinite redirect is gone. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[indus]

Welcome https://proxy-memoize.js.org