如果您的软件部署在外部 IP 地址托管内容，则软件部署会自动针对运行部署的网络配置防火墙规则。例如，Wordpress 部署会打开端口，以便您可以访问 Web 控制台并通过 HTTP 和 HTTPS 显示内容。如果防火墙配置失败，则尝试在外部 IP 地址上连接到 Web 控制台时，您可能会收到 HTTP 404 错误。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-09-04。"],[],[],null,["# Troubleshooting deployments\n\nIf a deployment fails, check your instances or deployments to identify the\nproblem. Go to\n[Cloud Deployment Manager](https://console.cloud.google.com/deployments)\nto see detailed messages that indicate what caused the deployment to fail.\n\nA deployment might fail to complete successfully for one of the following\nreasons:\n\n- Deployment Manager fails to create the necessary resources, such as an instance, disk, or load-balancing forwarding rule.\n- You're missing an Identity and Access Management (IAM) role.\n- The software fails to install and configure.\n- The deployment does not configure the firewall rules correctly on the Virtual Private Cloud (VPC) network.\n\nContents\n--------\n\n[Accessing your deployment](#accessing_your_deployment) \n\n[Deployment Manager failure](#deployment_manager_failure) \n\n[Missing permissions](#missing_permissions) \n\n[Software installation failure](#software_installation_failure) \n\n[Network and firewall issues](#network_and_firewall_issues) \n\n[Sending email from software deployments](#sending_email_from_software_deployments)\n\n### Accessing your deployment\n\nYou can return to your solutions by revisiting the\n[Cloud Marketplace](https://console.cloud.google.com/marketplace).\nGo to the solution page where you'll see a menu that shows your previous\ndeployments. For services, you can update the service options directly from\nthat page.\n\nOtherwise, if your deployment is running a VM instance, you can go to\n[Deployment Manager](https://console.cloud.google.com/deployments) in the\nGoogle Cloud console. From there, you can manage your deployment and view of all the\nGoogle Cloud resources that make up the deployment.\n\n### Deployment Manager failure\n\nSometimes your project might not have enough CPU quota to create the deployment\nresources. Check the remaining quota for your project at\n[Compute Engine Quotas](https://console.cloud.google.com/iam-admin/quotas), and request\nadditional quota if necessary. Then try to deploy the software package again.\n\n### Missing permissions\n\nYou might not have the `roles/deploymentmanager.editor` role applied to\nyour account for the project. Review [Access control for users](/deployment-manager/docs/access-control#roles)\nto ensure that your user account is added to the correct project and that you\nhave the correct roles applied to the account.\n\n### Software installation failure\n\nMost solutions provide logging for your instances so you can\ntroubleshoot software installation failures. If your deployment creates all of\nthe requested resources but you see a deployment error message in\n[Deployment Manager](https://console.cloud.google.com/deployments), it's possible\nthat the software failed to install or configure successfully. Connect to the\ninstances in the deployment and check the logs to identify the issue.\n\nEach entry in the log corresponds to the sequenced command that was executed\non that instance. Execution terminates on the first command to exit with a\nnon-zero exit code. The specific cause of failure will be typically be found\nat the end of the error log.\n\n### Network and firewall issues\n\nIf your software deployment hosts content on an\n[external IP address](/compute/docs/ip-addresses#externaladdresses),\nthe software deployment automatically configures\n[firewall](/vpc/docs/firewalls) rules on the network where your\ndeployment runs. For example,\n[Wordpress](/marketplace/solution/bitnami-launchpad/wordpress) deployments open\nports so that you can access the web console and display content over HTTP and\nHTTPS. If the firewall configuration fails, you might receive a HTTP 404 error\nwhen you try to connect to the web console on the external IP address.\n\nIf you need to configure the firewall manually or open additional ports for\nother services that run on your instances,\n[add firewall rules](/vpc/docs/using-firewalls#creating_firewall_rules) to the\nVPC network that your deployments run on.\n\n### Sending email from software deployments\n\nSome software packages try to send email over specific ports. However,\nCompute Engine does not allow outbound connections on port 25.\nTo send email from the instances that host your software packages, you must\nfollow the tutorial on [sending mail](/compute/docs/tutorials/sending-mail)."]]
