Yes, screenshots will most likely assist in clarifying the issue, however 
please reassure that no private information is being displayed within the 
screenshots and if so, please make sure to eliminate any private 
information before posting.

Additionally,  upon some investigation, I came across this link [1] that 
might be helpful for this situation.

__________________________________________________________________________________________________________

[1]:
https://webmasters.stackexchange.com/questions/84739/can-i-route-only-a-subdomain-through-cloudflare


On Tuesday, March 10, 2020 at 7:00:29 AM UTC+1, Rajesh Gupta wrote:
>
> I have posted the following issue on stackoverflow also.
>
> https://stackoverflow.com/questions/60574690/subdomain-is-not-working-through-cloudflare-for-google-appengine
>   
> .  
>
> My domain is registered in godaddy.com.
>
> I am using cloudflare for directing traffic to Google Appengine.
>
> I did the following steps:
>
>    1. I changed the nameservers in godaddy to Cloudflare's nameservers
>    2. I verified my domain in appengine setting by adding a TXT record
>    3. I added my subdomains the appengine console.
>    4. I copied all the A, AAAA and CNAME records to CloudFlare
>    5. I have not setup either managed or custom certificates in 
>    appengine, since I plan to use flexi ssl in cloudflare
>    6. I have setup to use proxy on cloudflare
>    7. I have setup to use flexi ssl on cloudflare
>
> I have uploaded my app as two services in appengine. 'default' and 'app1'
>
> www is working fine. any other subdomain will always reach to www 
> subdomain only.
>
> -- 
> Rajesh
> www.servicefolder.com
> *Field Service Software on Google Cloud Platform and Mobile*
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/a88ffa40-1f84-4849-b59d-da609a50cf7c%40googlegroups.com.

Reply via email to