In order to run the admin over an SSL connection, while also using the free tier of Cloudflare, I have set up a subdomain for accessing my site’s admin via SSL. The subdomain bypasses Cloudflare.
I have done some quick tests connecting to the admin via the subdomain and most things work ok. The few that don’t, I believe I can fix by using the WordPress HTTPS plugin.
I am using nginx to serve the site and can write appropriate rewrite rules into the site config to make all admin requests go to the subdomain over https and all non-admin requests go to the regular domain over http.
My question is whether there will be any side effects of accessing the admin on a subdomain that I should be aware of before I go ahead and implement this method.
For example, I notice that when I create a new post, in the database, the GUID for the post references the URL including the subdomain (i.e. it looks like
I am also using the Jetpack plugin to provide various WordPress.com services like comments and subscriptions. Would there be any issues in the communication between my site and WordPress.com if I am creating things in the DB via a subdomain?
Any other gotchas that I should be aware of?
Thanks for any help, pointers, feedback.
- The topic ‘Any gotchas accessing [single site] admin on separate subdomain?’ is closed to new replies.