There are a number of factors that may prevent you from accessing the webapps homepage for your deployment. The following steps can help you narrow down the scope of the issue, fix common issues, and collect information for further Technical Support.
Check security rules
By default, the security policies applied to the deployed resources permit only the administrator IP address and client IP addresses included in the "IP Addresses Allowed to Access MATLAB Web App Server Apps Home Page" section of the reference architecture template to access the webapps homepage. If your current IP address is not included in these CIDR ranges, you can edit the security rules associated with your deployed resources to allow your current IP address to access the webapps homepage:
Azure - Edit the webapp-nsg security group rule "allow-client" to include additional IP addresses.
AWS (pre-R2024a) - Edit the security group MatlabWebappServerCloudStackSg2 rules to add a new rule allowing HTTPS access on port 443 for additional IP addresses.
AWS (R2024a and later) - Edit the security group MatlabWebappServerCloudStackSg rules to add a new rule allowing HTTPS access on port 9988 for additional IP addresses.
Check webapps-status
If the Web App Server service fails to start on the deployed VM, you will be unable to access the webapps homepage for your deployment. To confirm if this service is running, open a terminal session to the VM hosting your Web App Server (Azure | AWS) and run the following commands: - Use the "cd" command to navigate to the Web App Server script directory (replace R20XXx with the specific release you deployed):
- Windows:
cd "C:\Program Files\MATLAB\MATLAB Web App Server\R2024a\script"
- Linux:
cd /usr/local/MATLAB/MATLAB_Web_App_Server/R2024a/script
- Check the status of the webapps service:
- If the service is listed as "Stopped," attempt to manually start the service:
If the service is listed as "Running" or starts successfully after completing these steps, confirm again if you are able to access the webapps homepage.
If the service fails to start, check the listed logs for more information.
A common cause for startup failure is issues relating to the certificate and private key files used to secure traffic to the webapps homepage. If the webapps_<timestamp>.log file shows SSL, certificate, or private key errors, verify your certificate and key files:
Azure - For Azure deployments, the certificate/key files are decoded from the base64-encoded strings entered into the reference architecture template. Refer to this
MATLAB Answer for steps to verify these files.
AWS (pre-R2024a) - The certificate/key used for an AWS deployment (R2023b and earlier) corresponds to the ACM ARN provided during deployment. This certificate is used to secure the load balancer. Check the certificate in the AWS portal to confirm it has not expired.
AWS (R2024a and later) - The certificate/key files used by an AWS deployment for R2024a or later are generated during the deployment process. If you experience certificate/key errors with this configuration, please contact technical support.
Collect logs and information for TS
For further troubleshooting, collect logs for your deployment to provide to technical support. These logs may also provide more information about the root of the issue for self-serve troubleshooting.
To locate the logs for your deployment:
Refer to this link to contact technical support.