Resolve 404 errors after migrating Jira Align to a new AWS environment

Summary

This article helps you troubleshoot and resolve 404 errors when accessing Jira Align after migrating to a new AWS environment.

Diagnosis

After migrating Jira Align to a new AWS environment, browsing to your Jira Align URL (for example, https://jira-align.example.com) returns 404 Not Found page

Cause

404 errors after migration are most often caused by misconfigured load balancers, incomplete IIS or SSL setup, or database connectivity issues. In some cases, using an outdated or corrupted installer can also prevent Jira Align from responding at the new URL.

Solution

Follow these steps to resolve 404 errors after migrating Jira Align to a new AWS environment:

1. Verify network and load balancer configuration

1. Ensure your load balancer is configured as an application load balancer (not a network load balancer) for HTTP/HTTPS traffic to Jira Align.

2. Confirm that the load balancer listener forwards requests to the correct backend server and port (typically 443 for HTTPS).

3. Check that RDP (TCP/UDP) is handled by a network load balancer if remote desktop access is required.

2. Review IIS and site bindings

1. Open IIS Manager on your Jira Align server.

2. Remove any old or duplicate sites related to previous environments.

3. Recreate the Jira Align site:

   1. Set the physical path to your Jira Align installation directory (for example, C:/ROOT_DIRECTORY/).

   2. Configure site bindings:

      • Type: https

      • IP address: All Unassigned or the correct server IP

      • Port: 443

      • Host name: your Jira Align URL (for example, jira-align.example.com)

      • SSL certificate: select the certificate matching your new hostname

4. In IIS Manager, double-click the ASP icon under the IIS section and adjust the following:

   • Set Maximum Request Entity Body Limit to 20,000,000

   • Set Response Buffering Limit to 67,108,864

   • Adjust Session Timeout as needed

3. Clean up and redeploy Jira Align

1. Stop the Jira Align IIS site.

2. Remove any existing Jira Connectors:

   • Navigate to each Jira Connector folder (for example, C:/ROOT_DIRECTORY/Jira, C:/ROOT_DIRECTORY/Jira2, C:/ROOT_DIRECTORY/Jira3).

   • Run uninstall.bat as an administrator in each folder.

3. Delete all content inside your Jira Align installation directory (C:/ROOT_DIRECTORY/).

4. Copy Global.asa and Web.config from your installation sources to C:/ROOT_DIRECTORY/.

5. Edit Web.config:

   • After the </clear> tag, add your database connection string: <add name='Main' connectionString='Data Source=<DB_SERVER>;Initial Catalog=<DB_NAME>;Integrated Security=False;User Id=<DB_USER>;Password=<DB_PASSWORD>;Encrypt=yes;TrustServerCertificate=True;MultipleActiveResultSets=True;' />

   • Replace <DB_SERVER>, <DB_NAME>, <DB_USER>, and <DB_PASSWORD> with your actual database server, database name, SQL username, and password.

6. Redeploy Jira Align using the Atlassian-provided installer:

   • Run the deployment script as an administrator (for example, /Sources/deploy-only-.bat).

7. Restart IIS for the Jira Align site.

4. Confirm database connectivity

1. Ensure the SQL Server allows remote connections:

   • Open SQL Server Configuration Manager on your database server.

   • Go to SQL Server Network Configuration > Protocols for MSSQLSERVER.

   • Enable required protocols (such as TCP/IP).

   • In TCP/IP Properties, confirm the correct IP addresses are enabled and the TCP port (typically 1433) is set.

   • Restart SQL Server services after making changes.

2. Update the Web.config connection string if your database server or credentials have changed.

5. Test access and verify resolution

1. From a browser, access your Jira Align URL (for example, https://jira-align.example.com).

2. Confirm the application loads without a 404 error.

3. If issues persist, review the latest installation and application logs for errors and confirm all steps above were followed using the Atlassian-provided installer.

6. Additional troubleshooting

• Check DNS records to ensure your domain points to the correct load balancer or server IP.

• Verify SSL certificates match your new hostname.

• Ensure Windows Firewall allows inbound traffic on port 443.

• Update any integrations or automation rules to use the new Jira Align URL.