Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[inputs.internet_speed] ping test failed : x509: certificate has expired #12595

Closed
Xer69 opened this issue Feb 2, 2023 · 2 comments · Fixed by #12617
Closed

[inputs.internet_speed] ping test failed : x509: certificate has expired #12595

Xer69 opened this issue Feb 2, 2023 · 2 comments · Fixed by #12617
Labels
bug unexpected problem or unintended behavior

Comments

@Xer69
Copy link

Xer69 commented Feb 2, 2023

Relevant telegraf.conf

[[inputs.internet_speed]]
  ## This plugin downloads many MB of data each time it is run. As such
  ## consider setting a higher interval for this plugin to reduce the
  ## demand on your internet connection.
  interval = "5m"

  ## Enable to reduce memory usage
  # memory_saving_mode = false

  ## Caches the closest server location
  # cache = true

Logs from Telegraf

2023-02-02T09:31:04Z D! [inputs.internet_speed] Found server: [16835]     2.10km 
Lyon (France) by La Fibre Pro
2023-02-02T09:31:04Z D! [inputs.internet_speed] Starting Speed Test
2023-02-02T09:31:04Z D! [inputs.internet_speed] Running Ping...
2023-02-02T09:31:08Z E! [inputs.internet_speed] Error in plugin: ping test failed: Get "https://speedtest.muona.com:8080/speedtest/latency.txt": x509: certificate has expired or is not yet valid: current time 2023-02-02T09:31:08Z is after 2022-08-28T12:56:43Z

System info

image: telegraf:1.25.1

Docker

telegraf:
  image: telegraf:1.25.1
  user: telegraf:995
  container_name: telegraf
  restart: always
  volumes:
    - ./telegraf.conf:/etc/telegraf/telegraf.conf

Steps to reproduce

  1. docker-compose up -d
  2. docker-compose logs telegraf

Expected behavior

I expect Download/Upload/Latency to be mesured

Actual behavior

The server don't provide a valid certificat.
As I see, it is not yet possible to force another server : #11625

Additional info

No response

@Xer69 Xer69 added the bug unexpected problem or unintended behavior label Feb 2, 2023
@srebhan
Copy link
Member

srebhan commented Feb 2, 2023

@Xer69 what do you expect us to do? The certificate of that server is invalid, so you should maybe contact those guys in order to renew their cert...

@powersj powersj added the waiting for response waiting for response from contributor label Feb 2, 2023
powersj added a commit to powersj/telegraf that referenced this issue Feb 3, 2023
This adds the ability to exclude or include specific speedtest server
IDs. If a user excludes a server ID that server is always excluded from
selection. If a user includes a specific server ID, then we will look
for only that ID.

This does not let a user pick a random server ID. The speedtest-go
library will receive the 10 closet servers. As such, users need to
be careful as they can prevent any server from being picked.

fixes: influxdata#11449
fixes: influxdata#11625
fixes: influxdata#12595
@Xer69
Copy link
Author

Xer69 commented Mar 7, 2023

thank you @powersj ! I'll wait the release to test this but sound really great :)
@srebhan I ask them to update their cert or leave the speedtest service ;) (but I prefer the option to blacklist their server)

@telegraf-tiger telegraf-tiger bot removed the waiting for response waiting for response from contributor label Mar 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug unexpected problem or unintended behavior
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants