A month ago, I paid attention to the relevant blog information of unlimited hosting space. After searching through Google, I found that there is indeed such a product. For the detailed application tutorial, please refer to the blog post “[免費主機] 建立一個完全免費的網站：InfinityFree虛擬主機“. The article also introduces how to build a WordPress personal space. You can quickly install WordPress in InfinityFree through the built-in one-click installation of Softaculous. I first applied for two spaces on InfinityFree, one using its own secondary level domain name, the other a free domain name that I applied for before. After installing WordPress separately, some problems were found, and they were effectively resolved after network retrieval and actual operations. Here is a brief record of the problems and their solutions.

一个月前关注了一下无限主机空间的相关博客信息，经过Google检索后发现确实有一款这样的产品，详细申请教程参见博文“[免費主機] 建立一個完全免費的網站：InfinityFree虛擬主機”。文中还有介绍了如何构建WordPress个人空间的方法，即可以在InfinityFree中通过Softaculous内建的一键安裝快速安装WordPress，我在InfinityFree上先申请了两个空间，一个采用了其自带的二级域名，另一个采用了自己之前申请的免费域名，在分别安装好WordPress后，发现出现了一些问题，经过网络检索及实际操作后均得到了有效解决。下面就简要记录一下问题及其解决方案。

Because the website after using its own secondary level domain name cannot open SSL for free, and also cannot be bound to Cloudflare, the WordPress blog space address opened by this domain name cannot be used with SSL connection, while the custom domain name can be opened. You can use the panel to be activated directly, or it can be bound to Cloudflare to be activated. I used the latter method. After this operation, pay attention to the URL selection http:// or https:// when installing WordPress. The homepage after installation cannot be opened directly. You can refer to the above method to delete the index2.html file, so that the homepage can be opened smoothly .

因为采用其自带的二级域名后的网站无法免费开通SSL，也无法绑定至Cloudflare，故由该域名开通的WordPress博客空间地址无法使用SSL连接，而自定义域名则可以开通，你可以利用该面板直接开通，也可以绑定至Cloudflare开通，我是采用了后者开通的。这样的操作以后，在安装WordPress时注意URL选择http://或https://，安装后的主页无法直接打开，可以参照上文中的方法删除index2.html文件，这样的话主页就可以顺利打开了。

However, the administrative backstage was found not be opened, and the blogs of the two spaces showed different error descriptions. The space blog administrative background with its own secondary level domain name cannot be opened, and an SSL error occurs. Please refer to the blog post “误改http为https之后WordPress管理后台打不开的解决过程” to solve the problem in phpMyAdmin introduced. In fact, we did not change it by mistake, but the solution is the same. The space blog administrative background with a custom domain name can’t be opened either. There are too many redirection errors. Please refer to the blog post “WordPress配置https后重定向次数过多” to modify the wp-config.php file as described in the method. Add the following codes after <?php:

$_SERVER[‘HTTPS’] = ‘on’;

define(‘FORCE_SSL_LOGIN’, true);

define(‘FORCE_SSL_ADMIN’, true);

但是管理后台却发现也都打不开，两个空间的博客出现不一样的错误说明。采用自带二级域名的空间博客管理后台无法打开，出现SSL的错误，可参考博文“误改http为https之后WordPress管理后台打不开的解决过程”中介绍的方法去phpMyAdmin解决问题，其实我们这里并非误改，不过解决方法相同。用自定义域名的空间博客管理后台也无法打开，出现太多重定向的错误，可参考博文“WordPress配置https后重定向次数过多”中介绍的方法修改wp-config.php文件，在<?php后其添加如下代码：

$_SERVER[‘HTTPS’] = ‘on’;

define(‘FORCE_SSL_LOGIN’, true);

define(‘FORCE_SSL_ADMIN’, true);