Skip to main content

FluentCommunity

#General

Proper DNS Settings for CloudFlare Landing Page on Top of WP-FluentCommunity

So my intended setup isa Cloudflare page as a landing page then a link into the community at http://community.fedx.io . But it seems to bork DNS. Enabling the Cloudflare page gives me 404 for WordPress. I'm using XCloud.host. When I set up WP on the site i don't see a option for doing it in a sub domain. Anyone have an idea? I engaged support but couldn't resolve.

  • 2 comments

Mat ‎

Trevor Lowing currently you have your naked/apex domain configured with some landing page and it works. If you want your fCommunity to be installed on a subdomain: community.domain.com first you need to configure the A record with your CloudFlare (CF) DNS settings and assign it to your hosting IP where you will install WordPress with your fCommunity plugin.

Currently you don't have the subdomain configured and in this case you should:

  • Add a new A Resource Record (RR) in your current CF DNS with your hosting IP address. Once it is completed you need to wait a little bit for the DNS propagation so the A record will be visible in all public DNS and your new subdomain will work.

  • In a meantime you need to add your subdomain (assign domain/word: subdomain.domain.com) to your hosting account where you will install your WP instance and the plugin (dont worry if the subdomain IP address is not propagated yet to your hosting - just add your subdomain as you would own it 100 years ago haha). Next... Basically when installing your wordpress you can select the domain which you will be used for your WP instance - it depends on your installer - some hosting with DA (Direct Admin) have dedicated installers (example: softaculous.com) to allow you easily install a new WP instance (select Advanced option for the installation mode so you can specify some more details for the installation).

    If you install your WP manually (.zip) and your subdomain is already assigned to your hosting account you just select/navigate to the folder location on your hosting where the assigned subdomain is pointing to (/public_html/) etc.

  • You need to just change the /portal slug (subdomain.domain.com/portal) with some code snippet so your fCommunity won't use it and you will have nice and clean url (subdomain.domain.com) for your community - ref: link

I am not sure if this is what you are looking for but keeping my fingers crossed.

Ps. To fix 404 error try to resave your wp-admin > Permalinks

Trevor Lowing

For posterity, the A name record was 'community.domain.com' that goes to a subdomain WP site. Then a CNAME record that points to the Cloudflare pages. You connect that in the Cloudflare pages UI.