AFD Configuration for custom domains doesnt work by default

[nsp37]

When setting AFD_CUSTOM_DOMAIN setup doesnt tackle (or define steps to):

• Remove the old assigned domain from the route
• Add Forward Host Header
• Add the domain to the AppService so it accepts the HOST header traffic matching the custom domain

[karpikpl]

hey @nsp37 I think this might be related to issue I just opened #92
Can you provide more details what configuration you've added in AFD?

[nsp37]

In AFD under the Route - you can hardcode the forwarded HOST header - you need to set this to the custom domain. It defaults to the AFD original hostname so Wordpress will redirect you infinitely.

To get AppService to accept the host heaader you have to then add the Custom Domain there as well - but only validate it, do not bind it.

[karpikpl]

Hey,
Thanks for your help!

I tried something similar but I'm getting lost in the wordpress space and can't get any logs out of WP.

My Setup is:

AFD:

• route for custom domain site1.foo.com to Azure App Service with origin group that has Origin Host Header set to site1.foo.com (instead of wordpress-foo.azurewebsites.net). Origin Path is set to /site1

App Service

• added domain site1.foo.com - validated without CNAME

WP:

• Config:
  • WORDPRESS_MULTISITE_TYPE - subdirectory
  • WORDPRESS_MULTISITE_CONVERT - true
• Network manager - added site1
• In site1 settings changed site Address (URL), home and siteurl to https://site1.foo.com

Is that correct?