tidyairports
tidyairports
CDCloudflare Developers
Created by Jack Shelton on 8/20/2023 in #pages-help
Not deploying
No description
13 replies
CDCloudflare Developers
Created by Jack Shelton on 8/20/2023 in #pages-help
Not deploying
In your repo, go to settings, and then 'Github Apps', you should then see the Cloudflare app if its still connected properly, from there you click on configure and you can verify the connection still has access to the repo
13 replies
CDCloudflare Developers
Created by Jack Shelton on 8/20/2023 in #pages-help
Not deploying
Can you elaborate on "it isn't deploying". When you go into the Pages overview screen, it will show the deployments, and any builds that have failed. You should look there first for further insight.
13 replies
CDCloudflare Developers
Created by tidyairports on 8/20/2023 in #pages-help
Pages+custom domain+access: public on main, private on preview
yeh we want the preview urls to be privately accessible, but wait @HardAtWork I managed to solve it. example.com > changed from EVERYONE ALLOW to EVERYONE BYPASS example.pages.dev > also changed from EVERYONE ALLOW to EVERYONE BYPASS *.example.pages.dev > added private access rules (i.e. Allowed IP only) Then, critically, I left it half an hour, then it all started working. The combination of 'allow' to 'bypass' and then giving it time to actually apply made the difference. I noted the lag when I deleted the application but the domain kept trying to redirect to the access login page for like 20 minutes then suddenly started working as expected. Still think cloudflare just needs to add a 'make preview urls private' button to avoid having to setup this casserole of nonsense. Thanks again for all your input.
19 replies
CDCloudflare Developers
Created by tidyairports on 8/20/2023 in #pages-help
Pages+custom domain+access: public on main, private on preview
the previews get the custom domain, there's no way to change this. the custom domain basically replaces pages.dev with your domain, so the preview subdomains are still there. Yeh I can redirect them but we still want the preview domains. It's surprising it's this hard, as I thought preview domains being private, and the production domain being public is a really basic use case. Nobody wants their preview domains to be public.
19 replies
CDCloudflare Developers
Created by tidyairports on 8/20/2023 in #pages-help
Pages+custom domain+access: public on main, private on preview
Yeh if I remove the rules/apps it does work and become accessible, but then the preview domains are also publicly accessible which isn't acceptable for us. Pages publishes every git commit and branch as a subdomain so it's trivial to guess them. I also can't setup the same repo with two different pages projects. Anyway @HardAtWork I appreciate your input this sunday!
19 replies
CDCloudflare Developers
Created by tidyairports on 8/20/2023 in #pages-help
Pages+custom domain+access: public on main, private on preview
I don't see an optition to disable them, only delete the entire thing. I've now set rules for custom domain, the pages.dev etc so EVERYONE BYPASS and now the redirect to the custom domain works, but the custom domain itself still shows the cloudflare access login page. At this point I've spent 4 hours on this so will reach out to Cloudflare support. Their product doesn't appear to be functioning correctly.
19 replies
CDCloudflare Developers
Created by tidyairports on 8/20/2023 in #pages-help
Pages+custom domain+access: public on main, private on preview
Thanks for the input. I created an account level redirect, but still, requesting the custom domain, or the pages.dev url just redirects to Cloudflare Access login page. It seems to want to do this before doing any redirect work.
19 replies