with warp vs without warp

my ping latency suddenly increases by a factor.

deployed a static pages site, idk why its not able to reach the page

not the right channel but yeah

What's the error you get / on custom domain or pages.dev? / What's the domain/url?

fnfal.pages.dev non sub directory static page, index.html inside the root path

deployment is successful

previous pages I have works fine

not receiving response on page request

hmm yea that pages.dev looks cursed, it's not resolving due to dns issues. How long ago did you create the project?

just moments ago

its a fresh project

It might just need a bit to straighten itself out. I've seen the issue with this before (the pages.dev is just horizontally referring to itself over and over), and I believe it wasn't a Pages issue but a CF DNS issue that resolved itself after a bit. If you need it going right now, I bet if you made a new project with a different name, it would instantly (well, besides propagation) start working

I'll try accessing the page again later if its really dns not resolving

It's not a typical propagation issue, but a literal DNS issue caused by the DNS not thinking its authoritive and referring you over and over again ex.

... 10 times before this
fnfal.pages.dev.        300     IN      NS      betty.ns.cloudflare.com.
fnfal.pages.dev.        300     IN      NS      yevgen.ns.cloudflare.com.
;; BAD (HORIZONTAL) REFERRAL
;; Received 102 bytes from 2a06:98c1:50::ac40:23df#53(yevgen.ns.cloudflare.com) in 0 ms

fnfal.pages.dev.        300     IN      NS      betty.ns.cloudflare.com.
fnfal.pages.dev.        300     IN      NS      yevgen.ns.cloudflare.com.
;; BAD (HORIZONTAL) REFERRAL
dig: too many lookups

Nothing on your end you can do. I've seen this once before, and I believe the root issue was just something to do with CF's DNS Internally needing time to update, but not sure if the same will happen. Since you just created it, I would give it a bit, and if it continues to be broken, could escalate the issue.

Just in case it's worth confirming, could you give the preview link of a deployment that worked (ex. .fnfal.pages.dev? You have a successful non-preview deployment as well?

none of them works but here:

@Chaika pinging you due to time, just got back

Thanks! Yea it's hard broken, just wanted to make sure I got the spelling of the domain right and it wasn't something silly like that. I will ask the Pages team when they're up at a more reasonable time for them (1 am here). If you need it working now, I would try to create new Pages Project with a different pages.dev.

No rush, I can wait for a while. Thank you!

fixed, re-added the project with same subdomain

If you only want them to add one thing to their DNS, then it would have to be a Worker, since even on your own Zone, it isn’t very easy to mount 3 different resources on a single record

Lo - can anyone answer a probably stupid question re: cloudflared tunnels?

Ask and someone might try 😉

I'm used to Traefik proxying with Docker (have various apps published behind Traefik and accessible on external URLs)

I've got the cloudflared tunnel docker image up and responding, and wanted to route one of my domains to an internal app via url (i.e. mydomain.com/myapp to http://192.168.10.10:8080/app etc)

however the cloudflared UI doesn't like any trailing URI after an IP/host or post - so baulks at /app

and when I access mydomain.com/myapp - I DO get to the tomcat host of my trial host, but it's 404'ing saying "/myapp" isn't valid - so it's passed the trailing URI through - which surprised me. Do they need to match? Is there a rewrite option?

or do I have set it up via "Pages"?

(edit : Can't that way - regex_replace is not available on the free or pro plans).