influxdata / influxdata/influxdb
while trying to enable HTTPS for Influxdb , giving errors.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 31.7k
- Forks
- 3.7k
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 8
Description
We have made below changes in our influxdb conf file
[admin]
enabled = true
bind-address = “127.0.0.1:5083”
https-enabled = false
https-certificate = "/etc/ssl/influxdb.pem
[http]
enabled = false
bind-address = “127.0.0.1:5086”
auth-enabled = false
log-enabled = true
write-tracing = false
pprof-enabled = false
https-enabled = true
https-certificate = “/etc/ssl/influxdb-selfsigned.crt”
https-private-key = “/etc/ssl/influxdb-selfsigned.key”
Steps to reproduce:__
List the minimal actions needed to reproduce the behavior.
1. install certificates
2. make changes in the influxdb.conf file.
3. restart Influxdb and verify the login.
After I have placed the certificates and key , and made relevant changes in influxdb.conf file, i thought influxd will start running.
Getting below error message while we try to bring the Influxdb up.
Error Message : "Failed to find any PEM data in key input."
* System info: Redhat Linux server
* InfluxDB version: 1.7
* Other relevant environment details: Container runtime, disk info, etc
__Config:__
Copy any non-default config values here or attach the full config as a gist or file.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the reported influxdb.conf HTTPS settings and the startup error, "Failed to find any PEM data in key input," for InfluxDB 1.7 on Red Hat Linux. Reproduce the restart after installing the certificates and verify that InfluxDB starts and login works without the error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100