我注册时希望获得可靠的云和安全的托管以及干净的 WordPress 安装。相反，我发现 hostarmada 将隐藏代码注入 wp-config.php 并在安装大量不需要的插件后添加自定义 ha-custom.php 文件，而没有任何通知或许可。
这破坏了基本的 WordPress 功能，如 xml 输出，只有在经过几个小时的调试后，支持人员很快将责任归咎于 SEOpress（以及第二次手动安装），我才发现问题出在 Hostarmada 自己的内部设置上。技术支持确认这是故意的，无法禁用。相反，我推出了价格过高的 VPS 产品，因为我要求进行干净的 WordPress 安装，而不将任何代码注入到核心文件中。
这明显违反了 wordpress.org 的最佳实践，并且对于任何期望干净、功能齐全的 Wordpress 托管的人来说，它使该平台变得不可靠且不安全。我现在已将我的网站移走，并根据 45 天退款保证申请退款。
更新 2：由于 Hostarmada 正在尝试各种伎俩来否认此评论的有效性，因此 Philip 回应并确认了 WordPress 核心文件中存在未经请求的代码注入：
“嗨，
我确实找到了源代码并解决了问题，这与我之前关于 Softaculous 在未经我许可或未经我要求的情况下随机安装一堆的问题有很大关系。
在 wp-content 中有 ha-custom.php ，它引用了所有已安装的 Softaculous 插件。
删除该文件会创建一个 Wordpress 致命错误，指向 wp-config 文件中的这一行：
require_once ABSPATH 。 'wp-content/ha-custom.php';
删除该行可以解决致命错误和 xml 问题。
我不知道为什么 Hostarmada 仍然在空的 WordPress 安装上强制随机安装一堆插件，然后将自定义代码插入到关键的 Wordpress 文件中，导致正常的网站/Wordpress 功能无法使用......我什至不知道为什么第一个响应是指向 SEOpress 来解决问题，而插件在这里没有故障......
但现在很明显，问题是由 Hostarmada 引起的，这一切现在让我积极考虑使用 45 天退款保证......因为我不再相信我的网站可以在 Hostarmada 服务器上安全、正确地运行。”
更新：Hostarmada 要求删除该评论，并标记其包含虚假信息。很遗憾我无法添加屏幕截图，但这些是我从 Philip 那里得到的回复的 1-1 副本：
“您找到并添加到安装中的文件来自 HostArmada 的自定义内部配置 - 此时，在从 Softaculous 执行安装时无法删除/排除该文件。
我知道在某些情况下，它可能会带来类似于您的票证中所解释的问题，但在与我们的系统管理员协商后，恐怕我们无法针对每个帐户/用户禁用它。
考虑到这一点，您可以在执行安装后手动删除该文件以及 wp-config.php 文件中的包含内容，这样就不会导致任何进一步的问题。如果您希望将其完全删除，并在每次安装后避免此类手动干预，那么我建议您考虑使用 VPS 服务器，我们可以在其中按照您想要的方式调整环境：“
我确实理解 Hostarmada 更愿意保守这个秘密，但他们自己的技术支持证实了这一点，无论他们试图传播多少误导性和煤气灯效应的答案。
2026 年 7 月 24 日更新：Hostarmada 再次滥用 Trustpilot 系统，错误地标记合法评论，试图将其删除并隐藏真相。
HostArmada 回复2025-07-29Thank you for sharing your feedback, though we must respectfully clarify that your claims are entirely inaccurate.
HostArmada does not inject any hidden code into the wp-config.php file, or install unwanted plugins without consent. Our WordPress installations are 100% clean, and we strictly adhere to WordPress.org best practices. These accusations are simply false.
We take pride in delivering secure, reliable, and transparent hosting solutions. Our auto-installer provides the option to install WordPress with or without additional plugins, and any tools offered during setup are entirely optional and meant to enhance user experience, not to interfere with core functionality.
Furthermore, at no point would our technical support team "confirm" practices that do not exist. We’re also surprised to hear about being "pushed" toward a VPS plan, this is not how we handle support. We recommend solutions based on actual needs, not upsells.
If you believe there’s been a misunderstanding or if you were experiencing issues, we would have gladly investigated and resolved them if given the opportunity. At the time of replying to this review, we have already honored our 45-day money-back guarantee as promised and issued a full refund to you. Still, we must set the record straight for the sake of anyone reading this review.
We’re always here if you'd like to revisit this with an open mind.
Reply to the update:
Thank you for updating your review and sharing more details. We welcome open feedback and we would like to address a few key points for clarity and transparency.
First and foremost, it is a standard practice for any responsible hosting provider to discuss feedback directly with customers and attempt to resolve any concerns. This is not an effort to silence criticism; it’s part of our ongoing commitment to improving customer experience and addressing misunderstandings when they arise.
Regarding the quoted message from our support representative: while it’s authentic, it can easily be taken out of context. The file you’re referring to is part of a non-intrusive, internal configuration added during WordPress installation via Softaculous. It’s designed solely to provide better integration and performance optimization in certain environments and does not interfere with WordPress core functionality. It is not hidden, malicious, or in violation of any WordPress.org best practices.
In fact, many reputable hosting providers use similar lightweight configuration files to tailor their environment. That said, we absolutely agree this should never result in unexpected behavior or require manual debugging.
We also agree that suggesting a VPS in your case was unnecessary. That response wasn’t aligned with the actual scope of your concern, and we’re addressing it internally with the appropriate team to prevent similar confusion in the future. Even though we haven't pushed the VPS solution, it doesn't reflect a sensible solution.
Finally, we want to make it absolutely clear: we are not trying to hide anything. If that were the case, we wouldn't be engaging openly here or offering detailed responses. We're simply committed to ensuring all feedback(positive or negative) is rooted in fact.
We genuinely hope your future hosting experiences are smooth and positive, and we remain available should you choose to revisit the conversation with us directly.
ChemiCloud
ScalaHosting
Hostinger
IONOS | ionos.com
NameHero®
SiteGround
DreamHost
HostPapa