mirror of
https://github.com/natrontech/pbs-exporter.git
synced 2026-04-25 18:35:51 +03:00
[GH-ISSUE #58] can't connect to pbs api, reprot "tls: failed to verify certificate: x509: certificate is valid for 127.0.0.1, ::1, not 192.168.31.64" #9
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/pbs-exporter#9
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @xinmans on GitHub (Sep 8, 2024).
Original GitHub issue: https://github.com/natrontech/pbs-exporter/issues/58
deploy config as below
docker-compose.yaml
services:
pbs-exporter:
image: ghcr.io/natrontech/pbs-exporter:latest
container_name: pbs-exporter
restart: always
ports:
- "10019:10019"
environment:
- PBS_API_TOKEN=b975aa4f-2abf-49ac-bd7d-929530b0b8e5
- PBS_ENDPOINT=http://192.168.31.64:8007
- PBS_INSECURE=false
sudo docker logs pbs-exporter
2024/09/08 12:46:07 INFO: Starting PBS Exporter v0.6.1, commit
e8c63cb, built at 2024-07-08T14:17:48+00:002024/09/08 12:46:07 INFO: Using fix connection endpoint: http://192.168.31.64:8007
2024/09/08 12:46:07 INFO: Listening on: :10019
2024/09/08 12:46:07 INFO: Metrics path: /metrics
2024/09/08 12:46:10 Get "https://192.168.31.64:8007": tls: failed to verify certificate: x509: certificate is valid for 127.0.0.1, ::1, not 192.168.31.64
2024/09/08 12:46:11 Get "https://192.168.31.64:8007": tls: failed to verify certificate: x509: certificate is valid for 127.0.0.1, ::1, not 192.168.31.64
@FabianVolkers commented on GitHub (Nov 23, 2024):
You need to set PBS_INSECURE to true in order to disable verification of the self-signed certificate. An alternative would be using lets encrypt to generate a valid certificate for your backup server.
@janfuhrer commented on GitHub (Dec 27, 2024):
@xinmans Has this solved your problem, can I close this issue?