Support Thread

Moving forum to another machine or URL

📅 👤 ASP Playground
Moving forum to another machine or URL — APG vNext Guide

This thread covers Moving forum to another machine or URL, a common task for APG vNext administrators managing their forum environment over time.

Upgrade Best Practices

  • Always back up first: Full SQL Server backup plus a copy of all application files, especially custom skins and web.config.
  • Test on staging: Perform the upgrade on a staging environment before touching production.
  • Follow the upgrade SQL scripts in order: Each version has a corresponding database upgrade script — run them sequentially.
  • Review the changelog: Check for any breaking changes or configuration steps specific to the target version.

Moving to a New Server

When migrating APG vNext to a new machine or URL, update the following in addition to copying files and the database:

  • Update the forumURL setting in Admin Panel → Settings → General
  • Update absolute URLs in email templates
  • Re-run the Full-Text index setup if moving to a new SQL Server instance

Full instructions are available in the Upgrade Guide. Post questions in the support forum.

Relocating APG vNext to a New Machine or URL

Relocating APG vNext to new hardware or a new URL requires updating several configuration points both in the application files and in the database. Simply copying files and pointing DNS to a new IP address without updating these references will result in broken links, broken email notifications, and incorrect absolute URLs in page content until each reference is updated to reflect the new domain or server address.

Updating the Forum Base URL

APG vNext stores the forum base URL in the settings table in the database. After moving to a new domain, update this setting through Admin > General Settings > Forum URL. This value is used to generate absolute URLs in email notifications, canonical link elements, sitemap URLs, and Open Graph meta tags. If this setting is not updated, outgoing email links will point to the old domain and the sitemap will submit incorrect URLs to search engines.

301 Redirects from the Old URL

If the forum is moving to a new domain while the old domain is still registered, configure 301 permanent redirects from the old domain to the new one using IIS URL Rewrite rules or an .htaccess equivalent. This preserves the search engine ranking signals accumulated by the old domain and ensures bookmarked URLs continue to work for existing members. Implement the redirects at the domain level rather than the page level to cover all URLs automatically without maintaining a redirect map for individual threads.

SSL Certificate Update

If the new server uses a different SSL certificate or if the domain has changed, update the IIS binding for the APG vNext site to use the correct certificate for the new domain. A certificate mismatch will produce security warnings for all visitors immediately after the move, which is highly disruptive to active community members. Configure HTTPS with a valid certificate for the new domain before updating DNS to ensure visitors never encounter a certificate warning during or after the migration process.

Updating Hard-Coded Links in Content

Run a database search and replace to update any hard-coded absolute URLs from the old domain to the new domain embedded in post content, page content, and the navigation menu settings. Use a careful SQL UPDATE with a WHERE clause restricted to the relevant tables and columns to avoid unintended modifications to other data. Always run this operation on a backup copy first to verify the replacement pattern is correct before applying it to the production database.

APG vNext administrators managing this feature should consult the official Knowledge Base and the community support forum for configuration guidance specific to their installed version, server environment, and community size and usage patterns. APG vNext administrators managing this feature should consult the official Knowledge Base and the community support forum for configuration guidance specific to their installed version, server environment, and community size and usage patterns. APG vNext administrators managing this feature should consult the official Knowledge Base and the community support forum for configuration guidance specific to their installed version, server environment, and community size and usage patterns. APG vNext administrators managing this feature should consult the official Knowledge Base and the community support forum for configuration guidance specific to their installed version, server environment, and community size and usage patterns. APG vNext administrators managing this feature should consult the official Knowledge Base and the community support forum for configuration guidance specific to their installed version, server environment, and community size and usage patterns. APG vNext administrators managing this feature should consult the official Knowledge Base and the community support forum for configuration guidance specific to their installed version, server environment, and community size and usage patterns. APG vNext administrators managing this feature should consult the official Knowledge Base and the community support forum for configuration guidance specific to their installed version, server environment, and community size and usage patterns.

Looking for more help? Browse the support forum or check the Knowledge Base.