Is the same domain, but one is the website and the other URL is the admin access
Is the same domain, but one is the website and the other URL is the admin access
EI can access the website but not the admin, how can that happen?
Dai.moda
ai.moda provides AI consulting services to help companies integrate artificial intelligence into their products, services, processes and platforms. Our experts can customize AI solutions to meet your unique business needs.
Ddo you actually need a non-free plan for the admin access?
EI have been using this same settings cloudflare>>AWS>>EC2 linux instance for over 5 years already and about a month ago this same issue happened for the first time, today is the 2nd time I 'm experiencing the same issue
EJust now, suddenly started working. So weird
Eai.moda
ai.moda provides AI consulting services to help companies integrate artificial intelligence into their products, services, processes and platforms. Our experts can customize AI solutions to meet your unique business needs.
ai.moda
ai.moda provides AI consulting services to help companies integrate artificial intelligence into their products, services, processes and platforms. Our experts can customize AI solutions to meet your unique business needs.
EThanks guys anyways for you trying to help. Is working now and I'll insist with AWS support for them to find out. I need to take care of business. Have a nice day .
Dthere's a middle redirect, you can see the first redirect is to
location: https://www.ai.moda/anything1
YI have a question about my website with cloudflare. The nameservers seem updated when I check, the website is still offline in the US. What's going on?
JI'm not quite understanding step 1 of the setup https://developers.cloudflare.com/cloudflare-for-platforms/cloudflare-for-saas/start/getting-started/#step-1--create-fallback-origin .. what's the IP address if I'm wanting to point a custom subdomain at a worker?
Cit gives you an example right there,
192.0.2.1or you can do
AAAA100::doesn't matter too much, your route will take over anyway
JIt's just a "dummy" ip address?
Cyup
Cjust something to be proxied so CF responds with their Proxy IPs on Edge and traffic flows in
C100:: is IPv6 Discard (don't go anywhere)
C192.0.2.1 is just a private ip, no nice Ipv4 discard to use
JI'm guessing I have to set a rule somewhere
Cif you want to use workers, then you can just use routes
CCloudflare Docs
Learn how to use a Worker as the fallback origin for your SaaS zone.
Cone wildcard to catch all, or specific ones for each custom hostname
Jhmm, so if I have domain
created fallback origin
then made a CNAME
then set up CNAME from
would the workers route then look something like
foo.xyzcreated fallback origin
fallback.foo.xyzthen made a CNAME
proxy.foo.xyzfallback.foo.xyzthen set up CNAME from
foo.otherdomain.exampleproxy.foo.xyzfoo.otherdomain.examplewould the workers route then look something like
foo.otherdomain.example.com/*then made a CNAME proxy.foo.xyz pointing at fallback.foo.xyzThat's unnecessary, they can just cname to fallback or any proxied record on your domain
J"they" being me 
Crest of that makes sense yea. Having CF for SaaS on a zone enables you to make routes that don't match your zone/match externals
Jawesome
JI'm not sure why the docs recommend having that intermediate CNAME proxy
Jthere must a good reason
Coh, looks like they just wanted you to do
*.customers.saasprovider.comhmm, what advantage would that have? that I could route based on that domain so they could change their own domain if they want and not break the routing?
Cthat I could route based on that domain so they could change their own domain if they want and not break the routingNo, how would CF know what CNAME each request used if they're using ext dns? The only thing they get is the host header and the ip requested
CI think advantage is just more pretty
provides a friendly and more flexible place for customers to route their traffic.and you could always point them to some other unproxied origin them if needed I guess for a specific customer
Jthat makes sense, my dns understanding is a bit thin. so then what's the advantage of them CNAMEing google.customer.saasprovider.com instead of just everyone CNAMEing customer.saasprovider.com?
Jah that makes sense
Jaesthetics and then flexibility of switching up the routing for just that customer outside of the SaaS functionality
Jwell, I'm hitting my hello world worker through my custom domain with SSL, thanks for the help 
Vyou could also do some shard scaling by pointing them at different IPs so that every node doesn’t know how to route every single request
![[ ⚡ ] ElBretxa](https://cdn.discordapp.com/avatars/874736822704545903/4bd917a099515f562096bd68170bd2c7.webp?size=40)
[Hey, my team and I have a website for a project, but when trying to go in the website, we get an error saying
I managed to load into the website today once, we might think it is an issue with cache, but we did the purge cache in cloudflare website and nothing changed.
The website is
https://kenabot.xyz/en
I managed to load into the website today once, we might think it is an issue with cache, but we did the purge cache in cloudflare website and nothing changed.
The website is
https://kenabot.xyz/en
Pfrom what I can tell it has something to do with RSC I think?
[We do not use RSC
![[ ⚡ ] ElBretxa](https://cdn.discordapp.com/avatars/874736822704545903/4bd917a099515f562096bd68170bd2c7.webp?size=16)
Phm your page's response does seem to indicate RSC is being used
[we only use client components, with next v14 you must have enabled RSC by default
Pprobably best to create a help thread in #general-help and continue there
[Thanks
IOut of curiosity: how can you tell between RSC and client components there?
II'd be able to tell it's Next but that's it 
Pfrom what I could find, both the
connection closed error and self.__next_f are coming from Next.js' RSC
JRequiring users to enter their new password twice before changing it is a good practice. Since the password field is masked, users might not notice if they make a typing error. Confirming the password helps prevent mistakes.
