You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently having a hard time trying to setup an Application Gateway with end-to-end SSL on Azure.
First of all, I noticed the configuration (and documentation as well) is a bit confusing. The backend_http_settings block expects an authentication_certificate nested object/block, instead of a reference to it like all the other blocks (frontend_ip_configuration_name, backend_address_pool_name, etc).
I could get it to work with a configuration like this.
backend_http_settings {
name = "https"
cookie_based_affinity = "Disabled"
port = "${var.master_port}"
protocol = "Https"
request_timeout = 5
probe_name = "default"
authentication_certificate {
name = "master"
}
}
I'm also declaring a separate authentication_certificate block.
authentication_certificate {
name = "master"
data = "${base64encode(file("files/keys/master.cer"))}"
}
Documentation seems to indicate there's something to be fixed regarding this.
Anyway, applying it, I get a generic error from the API, and the resource ends up stuck with a Failed status on panel.
Error Creating/Updating ApplicationGateway network.ApplicationGatewaysClient#CreateOrUpdate: Failure sending request: StatusCode=200 -- Original Error: Long running operation terminated with status 'Failed': Code="InternalServerError" Message="An error occurred."
This issue has been automatically migrated to hashicorp/terraform-provider-azurerm#619 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to this issue and let us know.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
ghost
locked and limited conversation to collaborators
Apr 5, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm currently having a hard time trying to setup an Application Gateway with end-to-end SSL on Azure.
First of all, I noticed the configuration (and documentation as well) is a bit confusing. The
backend_http_settings
block expects anauthentication_certificate
nested object/block, instead of a reference to it like all the other blocks (frontend_ip_configuration_name
,backend_address_pool_name
, etc).I could get it to work with a configuration like this.
I'm also declaring a separate
authentication_certificate
block.Documentation seems to indicate there's something to be fixed regarding this.
Anyway, applying it, I get a generic error from the API, and the resource ends up stuck with a Failed status on panel.
Any clues on this?
The complete resource configuration is below:
The text was updated successfully, but these errors were encountered: