I have 100% had success here with it
I have 100% had success here with it
CI doubt it.
VCan we suggest this feature somewhere? Because it will be waste of money if I have 10 TLDs and buy paid plan for all
IAs Leo has said, we can't bump abuse tickets and don't even have any insight at all into them - it's a completely separate team that we have no visibility into.
EHello everyone, I'm Eddy.
EI'm experiencing an issue and need help. I can reach my website https://ledradiant.com , which is hosted at AWS, but can't reach the website admin https://ledradiant.com/ledradmin , the browser displays 504 Gateway Time-out
nginx/1.10.3 (Ubuntu)
nginx/1.10.3 (Ubuntu)
LED Radiant
LEDRadiant offers industrial and commercial LED lighting fixtures. Shop our huge selection of high bay, low bay, strip, street lights, flood lights, and more.
EI have contacted AWS support, but got not the help I need or I didn't understand correctly, I'm not a developer, just the business owner with limited knowledge
EI have set it to DNS only just to check
Dwhat's the purpose of the multiple domains? If it's the same site, you can just redirect everything that hits the free zone to your primary zone
EThank you for responding Leo
EHi Dave, thanks for the reply
EIs 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.1Cor you can do
AAAA 100::Cdoesn'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.xyz pointing at the dummy IPthen made a CNAME
proxy.foo.xyz pointing at fallback.foo.xyzthen set up CNAME from
foo.otherdomain.example pointing at proxy.foo.xyz and added foo.otherdomain.example as a custom hostnamewould the workers route then look something like
foo.otherdomain.example.com/*? can I match on that external domain?Cthen 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.com, so people could cname like google.customers.saasprovider.comJhmm, 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