Support

On Uptime hosting, PHP runs with the working directory set to your site's web root (document root). This behavior is intentional. It keeps file resolution predictable and consistent across requests on IIS and FastCGI.

Many older PHP applications assume the working directory matches the folder that contains the script being executed. That assumption often breaks on modern hosting stacks—and it is the most common cause of “file not found” errors after migrating a legacy site to Uptime.

Typical symptoms

• include, require, or require_once failures for config or library files
• Broken paths to uploads, caches, or log directories
• Code that uses bare relative strings such as ../config.php or ./includes/bootstrap.php

What to change

Stop anchoring paths to the process working directory. Instead, build paths from a known base:

• Any PHP file: use __DIR__ so paths are relative to the current source file.
  Example: require __DIR__ . '/config/database.php';
• CodeIgniter 4 apps: use framework constants such as FCPATH, APPPATH, ROOTPATH, and WRITEPATH instead of hand-rolled relative strings.
• Path normalization: in CodeIgniter 4, load the filesystem helper and use set_realpath() to resolve local paths safely before reading or writing files.

Migration checklist

1. Search your codebase for relative includes (../, ./) and paths built from getcwd().
2. Replace them with __DIR__-based paths or your framework's path constants.
3. Retest entry points (front controller, cron scripts, and upload handlers) after deployment.
4. Keep writable directories outside the public web root whenever possible.

If you are unsure which pattern your application uses, open a chat or call support and mention the exact file path shown in the PHP error—we can point you to the correct base constant for your stack.

Moving WordPress to Uptime is a two-step process: export on your old host, then import on your new Uptime site. Use our free Uptime Site Migrator plugin for both sides of the move.

Before you start

• Provision your website on Uptime and install a fresh copy of WordPress on the new site.
• Make sure you can log in to wp-admin on both the old site and the new Uptime site.
• Large sites may take several minutes and can require higher PHP upload limits on the destination server.

Step 1: Export on your old host

1. Download the plugin from /tools/wordpress-migrator/download or visit the Tools page for details.
2. In WordPress admin, go to Plugins → Add New → Upload Plugin, upload the zip, and activate it.
3. Open Uptime Migrator in the admin sidebar and choose Export site.
4. Click Begin export and download the backup zip when it is ready.

The export includes your database, themes, plugins, uploads, and root .htaccess. It does not include wp-config.php, so database credentials stay on each server.

Step 2: Import on Uptime

1. Install and activate the same plugin on your new Uptime WordPress site.
2. Open Uptime Migrator and choose Import site.
3. Upload the backup zip from step 1 and click Begin import.
4. When import completes, visit the front end, log in with your existing WordPress users, and save Settings → Permalinks if links do not work immediately.

Need help after the move?

If the site loads but throws errors that were not present on your old host, see our support guides on migration remediation and PHP file paths, or open a chat with the exact error message.

If your site worked on a previous host but fails after moving to Uptime, you may need migration remediation rather than standard support.

Which option to choose

• Simple ($50) — one focused issue such as relative file paths, a single broken include, or one configuration error.
• Complex ($100) — multiple errors, legacy PHP behavior, or issues spanning several files.

What you receive

• Diagnosis and code or configuration updates within scope
• Verification after the fix
• A written remediation report in your account (findings, changes made, and recommendations)
• Email delivery when the report is published

Purchase from the Development → Migration remediation section or ask staff to add it during checkout.

Each Uptime hosting plan maps to one website. After checkout, sign in to your account portal to provision the site on an available node.

Steps

1. Complete checkout for your hosting plan (and domain, if purchased).
2. Go to Account → Websites and choose Provision on the pending site.
3. Save the one-time setup password shown after provisioning—it is displayed only once.
4. Visit your site's setup URL to finish installing WordPress, upload files, or configure your application.

Need help choosing a plan or understanding what is included? Browse our Development packages or contact support before checkout.

You can register a new domain during checkout or connect a domain you already own.

Domains purchased through Uptime

We register the domain on your behalf and manage DNS through your account portal. After your site is provisioned, A records for @ and www should point to your assigned node's public IP.

Common record types

• A — maps a hostname to an IPv4 address (used for @ and often www)
• CNAME — aliases one hostname to another (for example, www to your apex domain)
• MX — directs email to your mail provider
• TXT — used for SPF, DKIM, and domain verification

DNS changes can take time to propagate worldwide. If a site does not resolve after provisioning, allow up to a few hours before troubleshooting.

If you purchased hosting only and already own a domain at another registrar, you will need to point DNS at Uptime after your site is provisioned.

What you need

• Your site's assigned node public IP (shown in the account portal after provisioning)
• Access to DNS management at your current registrar

Recommended records

• A record for @ → node public IP
• A record or CNAME for www → node public IP or your apex domain

Leave existing MX records in place if email is hosted elsewhere. Add or update TXT records only when we provide values for verification or email authentication.

Business email is available on eligible hosting plans. Enable mail service for your domain from the account portal before creating mailboxes.

Setup overview

1. Open Account → Email and enable the domain.
2. Create the mailboxes you need.
3. Apply the DNS records shown in the portal (MX, SPF, and DKIM where provided).
4. Configure your mail client or device with the server settings we supply.

Allow time for DNS propagation after changing MX or TXT records. Sending issues are often traced to missing SPF or DKIM—verify those records first.

Checkout is processed securely through Stripe. Completed orders appear under Account → Billing, where you can review charges tied to your account.

Subscriptions and renewals

Hosting and add-on services renew according to the term selected at checkout. Domain registrations renew annually unless configured otherwise at your registrar.

Receipts

Payment confirmation is sent by Stripe to the email address used during checkout. Account-level receipt history in the portal continues to expand—contact support if you need a copy of a specific charge today.

Live chat connects you with our team in real time when agents are available. Look for the chat widget in the lower-right corner of the site or open Support → Chat.

Before you start

• Chat availability is shown on the widget and support page.
• You may enter a display name if you are not signed in.
• Signed-in customers are identified automatically.

During the session

Stay on the page or navigate the site—the chat widget keeps your conversation open. Use Disconnect when you are finished so we can help the next customer in queue.

If chat is offline, use Call Us or email support instead.

Build your order from the public site or account portal. Domains and hosting can be purchased together or separately depending on what you need.

Cart tips

• Domain-only checkout is supported—hosting is not required to register a domain.
• Each hosting plan provisions one website.
• Review term length and pricing before starting checkout.

After payment

Successful checkout creates or updates resources in your account. Domains and websites may appear as pending until registration or provisioning completes. Sign in to track progress and finish setup.