heartbeat url is not working if i have my application url https on consul
See original GitHub issueheartbeat url is not working if i have my application url https url
In consul am able to see the health check working on the Consul This the register to the consul
{
"ID": "api",
"Name": "api",
"Service": "api",
"Tags": [
"management.context-path=/api/v1",
"management.server.ssl.enabled=true"
],
"Meta": {},
"Port": 80,
"Address": "10.222.222.22",
"Weights": {
"Passing": 1,
"Warning": 1
},
"EnableTagOverride": false,
"check":{
"ID": "api",
"Name": "HTTP Health Check",
"HTTP": "https://10.222.222.22:80/api/v1/health",
"Method": "GET",
"Header": {"x-foo":["bar", "baz"]},
"Interval": "10s",
"TLSSkipVerify": true
}
}
how to make the heartbeat url to be https instead of http ?
@joshiste Can you help ?
I see issue fixed for http url https://github.com/codecentric/spring-boot-admin/issues/1092
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:11 (1 by maintainers)
Top Results From Across the Web
Common Error Messages - Troubleshoot | Consul
Troubleshoot issues based on the error message. Common errors result from failed actions, timeouts, multiple entries, bad and expired certificates, ...
Read more >Configure SSL | Heartbeat Reference [8.5] - Elastic
For server authentication, the path to the SSL authentication certificate must be specified for TLS. If the certificate is not specified, startup will...
Read more >Error: "Not sent because last heartbeat failed" after install ...
Solved: Hello Team, It is my first time using Dynatrace, I'm ... info [comm ] URL https://192.168.221.52:9999/communication not working ...
Read more >Appendix A: Common application properties - Spring Cloud
If format is Format.PROPERTIES or Format.YAML then the following field is used as key to look up consul for configuration. spring.cloud.consul.
Read more >Remote Configuration Manager console hangs for 20 seconds ...
A Configuration Manager console that's running on a remote computer stops responding ... service every 10 minutes by connecting to the following URL:....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
you must not set the discovery scheme to the metadata but for the application.properties of the SBA server (so that it’s discovery client get configured)
Please find the screen shot issue persist even following your recommendation.
I registered the application to consul through there api register this the payload i used
{ “ID”: “api”, “Name”: “api”, “Service”: “api”, “Tags”: [ “management.context-path=/api/v1”, “management.server.ssl.enabled=true”, “spring.cloud.consul.discovery.scheme=https”
], “Meta”: {}, “Port”: 80, “Address”: “10.222.222.22”, “Weights”: { “Passing”: 1, “Warning”: 1 }, “EnableTagOverride”: false, “check”:{ “ID”: “api”, “Name”: “HTTP Health Check”, “HTTP”: “https://10.222.222.22:80/api/v1/health”, “Method”: “GET”, “Header”: {“x-foo”:[“bar”, “baz”]}, “Interval”: “10s”, “TLSSkipVerify”: true } }
I guess the issues is with SBA it not able to pick the scheme of the application