The pre-purchase questions (cost, whether you can move away, whether you can install plugins) are covered in full on the WordPress product page. This article collects the questions that come up during actual use.
Configuration and Limits
Q: Can I change PHP settings myself, such as memory_limit or max_execution_time?
No — we have to adjust those for you. RoamerHost's WordPress hosting mounts server configuration, vhost templates, and PHP settings read-only and shared across all sites, so you can't change them from inside your site. If a plugin of yours needs unusual PHP parameters (common with large import tools and image processing plugins), let us know and we'll adjust them on the platform side.
That's the trade-off of a fully managed architecture: you don't maintain the server, but you also can't alter the foundation. The upside is that we tune it once and every site benefits at the same time — and malicious code can't tamper with server settings either.
Q: I'm migrating from another host. Do I need to rewrite my .htaccess rewrite rules?
No. RoamerHost's WordPress runs on OpenLiteSpeed, which supports .htaccess natively. That's the biggest difference from nginx — nginx ignores .htaccess entirely, so migrating there means translating your whole rule set into nginx configuration. OpenLiteSpeed reads it directly, so your cache plugin, security plugin, and hotlink protection rules work as soon as you move them over.
Performance
Q: Do I need to install an object cache plugin or set up Redis myself?
No — every site comes with Redis object caching built in, isolated per site: each site has its own Redis username and password and can only reach its own data, so sites never affect each other.
Note that what it accelerates is database queries, not full-page caching. If what you want is static page generation, you can add the LiteSpeed Cache plugin alongside it — OpenLiteSpeed supports it natively.
Q: My scheduled posts often missed their time on my old host. Will that happen here?
No. WordPress's built-in wp-cron is triggered by page requests by default — schedules are only checked when a visitor browses the site. On a site with no traffic, a post scheduled for the middle of the night simply doesn't publish.
RoamerHost disables that trigger mechanism and instead has the platform actively fire schedules every 5 minutes for every running site. So your scheduled posts and your plugins' background jobs run on time, and the cost of running them isn't passed on to your visitors' load times.
Q: Does my site go down when I upgrade my plan?
No. WordPress CPU, memory, and PHP tuning can be applied live to an existing site without rebuilding the container, so the site keeps running throughout the upgrade and the data volume is never unmounted and remounted.
Troubleshooting
Q: My site suddenly shows a white screen or a 500 error. What do I do?
The most common cause is a newly installed or updated plugin conflicting with the environment. Think back to what you changed recently and deactivate that plugin. If you can't even reach the admin area, try "Restart" on the instance from the dashboard; if that still doesn't resolve it, contact us — don't run a wipe-and-rebuild, because that erases your data.
Q: The admin area is slow but the front end is fine. What's going on?
A slow admin area is usually a different bottleneck from the front end. The common cause is a plugin running background jobs in the admin (scans, statistics, syncing). Start by checking whether only certain pages are slow, and whether you have several plugins with overlapping functionality installed. If it's a resource shortage, the Basic plan can get tight once you have a lot of plugins, so consider moving up to the Pro plan, which has more CPU and storage.
Q: What are the symptoms of running out of memory?
Processes get cut off rather than simply slowing down — a large file import fails halfway through, a batch operation doesn't finish. Because container memory is a hard cap with no swap, exceeding it means immediate termination. Full details in the shared FAQ.
Sources and Further Reading
For WordPress ecosystem specs and best practices, the official documentation is authoritative:
- WordPress user documentation
- WordPress developer documentation — technical specifications for plugins and themes
Further Reading
- How Long Before You Notice Your Site Is Down? Which Pages to Monitor
- WordPress Hosting Pre-Purchase FAQ: Migration, Multiple Sites, and Traffic
- When to Upgrade Your WordPress Plan: Basic vs. Pro
- WordPress for Beginners
- Connecting a Custom Domain and SSL
- Why We Use OpenLiteSpeed
- Redis Object Caching and the wp-cron Rework
Want Someone to Build It for You?
Once your requirements go beyond what plugins can do, someone has to touch the code. Roamer Tech takes on advanced WordPress development:
