starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 14 Packages Projects Releases 10 Wiki Activity

Speedtest-Tracker ping issue #2207

New Issue
Closed
opened 2026-02-05 04:13:05 +03:00 by OVERLORD · 1 comment
OVERLORD commented 2026-02-05 04:13:05 +03:00
Owner
Copy Link

Originally created by @Deses on GitHub (Dec 22, 2025).

✅ Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

Yes, verbose mode was enabled and the output is included below

📜 What is the name of the script you are using?

Speedtest-Tracker

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/speedtest-tracker.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

pve-manager/9.1.2/9d436f37a0ac4172 (running kernel: 6.17.4-1-pve)

📝 Provide a clear and concise description of the issue.

I installed this community script as an unprivileged container. The installation completed successfully, and I can log into the web UI and use it without issues, but the tests did not run. Every test failed with the error Failed to connected to hostname "icanhazip.com". Error received "unknownError".

After locating the logs (/opt/speedtest-tracker/storage/logs/laravel.log), I found the root issue:

[2025-12-21 22:02:23] production.INFO: Pinged hostname {"host":"icanhazip.com","data":{"success":false,"error":"unknownError","host":"icanhazip.com","packet_loss_percentage":100,"packets_transmitted":null,"packets_received":null,"options":{"timeout_in_seconds":5,"interval":1.0,"packet_size_in_bytes":56,"ttl":64},"timings":{"minimum_time_in_ms":null,"maximum_time_in_ms":null,"average_time_in_ms":null,"standard_deviation_time_in_ms":null},"raw_output":"
ping: socktype: SOCK_RAW
ping: socket: Operation not permitted
ping: => missing cap_net_raw+p capability or setuid?
","lines":[]}}

More specifically, ping: => missing cap_net_raw+p capability or setuid?

To confirm, I ran getcap /bin/ping and I got no output because it has no capabilities.

The solution:

root@speedtest-tracker:~ # setcap cap_net_raw+ep /bin/ping
root@speedtest-tracker:~ # getcap /bin/ping
/bin/ping cap_net_raw=ep
root@speedtest-tracker:~ # systemctl restart speedtest-tracker.service

And now speedtest-tracker finally completes tests successfully:

[2025-12-21 22:05:57] production.INFO: Pinged hostname {"host":"icanhazip.com","data":{"success":true,"error":null,"host":"icanhazip.com","packet_loss_percentage":0,"packets_transmitted":1,"packets_received":1,"options":{"timeout_in_seconds":5,"interval":1.0,"packet_size_in_bytes":56,"ttl":64},"timings":{"minimum_time_in_ms":13.626,"maximum_time_in_ms":13.626,"average_time_in_ms":13.626,"standard_deviation_time_in_ms":0.0},"raw_output":"PING icanhazip.com (104.16.185.241) 56(84) bytes of data.
64 bytes from 104.16.185.241: icmp_seq=1 ttl=56 time=13.6 ms

--- icanhazip.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 13.626/13.626/13.626/0.000 ms
","lines":[{"line":"64 bytes from 104.16.185.241: icmp_seq=1 ttl=56 time=13.6 ms","time_in_ms":13.6}]}}

🔄 Steps to reproduce the issue.

Just install the script using defaults and run a test, it'll fail withFailed to connected to hostname "icanhazip.com". Error received "unknownError".

❌ Paste the full error output (if available).

[2025-12-21 22:02:23] production.INFO: Pinged hostname {"host":"icanhazip.com","data":{"success":false,"error":"unknownError","host":"icanhazip.com","packet_loss_percentage":100,"packets_transmitted":null,"packets_received":null,"options":{"timeout_in_seconds":5,"interval":1.0,"packet_size_in_bytes":56,"ttl":64},"timings":{"minimum_time_in_ms":null,"maximum_time_in_ms":null,"average_time_in_ms":null,"standard_deviation_time_in_ms":null},"raw_output":"
ping: socktype: SOCK_RAW
ping: socket: Operation not permitted
ping: => missing cap_net_raw+p capability or setuid?
","lines":[]}}

🖼️ Additional context (optional).

No response

Originally created by @Deses on GitHub (Dec 22, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? Yes, verbose mode was enabled and the output is included below ### 📜 What is the name of the script you are using? Speedtest-Tracker ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/speedtest-tracker.sh)" ### ⚙️ What settings are you using? - [ ] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? pve-manager/9.1.2/9d436f37a0ac4172 (running kernel: 6.17.4-1-pve) ### 📝 Provide a clear and concise description of the issue. I installed this community script as an **unprivileged** container. The installation completed successfully, and I can log into the web UI and use it without issues, but the tests did not run. Every test failed with the error `Failed to connected to hostname "icanhazip.com". Error received "unknownError".` After locating the logs (`/opt/speedtest-tracker/storage/logs/laravel.log`), I found the root issue: ```sh [2025-12-21 22:02:23] production.INFO: Pinged hostname {"host":"icanhazip.com","data":{"success":false,"error":"unknownError","host":"icanhazip.com","packet_loss_percentage":100,"packets_transmitted":null,"packets_received":null,"options":{"timeout_in_seconds":5,"interval":1.0,"packet_size_in_bytes":56,"ttl":64},"timings":{"minimum_time_in_ms":null,"maximum_time_in_ms":null,"average_time_in_ms":null,"standard_deviation_time_in_ms":null},"raw_output":" ping: socktype: SOCK_RAW ping: socket: Operation not permitted ping: => missing cap_net_raw+p capability or setuid? ","lines":[]}} ``` More specifically, `ping: => missing cap_net_raw+p capability or setuid?` To confirm, I ran `getcap /bin/ping` and I got no output because it has no capabilities. The solution: ```sh root@speedtest-tracker:~ # setcap cap_net_raw+ep /bin/ping root@speedtest-tracker:~ # getcap /bin/ping /bin/ping cap_net_raw=ep root@speedtest-tracker:~ # systemctl restart speedtest-tracker.service ``` And now speedtest-tracker finally completes tests successfully: ```sh [2025-12-21 22:05:57] production.INFO: Pinged hostname {"host":"icanhazip.com","data":{"success":true,"error":null,"host":"icanhazip.com","packet_loss_percentage":0,"packets_transmitted":1,"packets_received":1,"options":{"timeout_in_seconds":5,"interval":1.0,"packet_size_in_bytes":56,"ttl":64},"timings":{"minimum_time_in_ms":13.626,"maximum_time_in_ms":13.626,"average_time_in_ms":13.626,"standard_deviation_time_in_ms":0.0},"raw_output":"PING icanhazip.com (104.16.185.241) 56(84) bytes of data. 64 bytes from 104.16.185.241: icmp_seq=1 ttl=56 time=13.6 ms --- icanhazip.com ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 13.626/13.626/13.626/0.000 ms ","lines":[{"line":"64 bytes from 104.16.185.241: icmp_seq=1 ttl=56 time=13.6 ms","time_in_ms":13.6}]}} ``` ### 🔄 Steps to reproduce the issue. Just install the script using defaults and run a test, it'll fail with`Failed to connected to hostname "icanhazip.com". Error received "unknownError".` ### ❌ Paste the full error output (if available). [2025-12-21 22:02:23] production.INFO: Pinged hostname {"host":"icanhazip.com","data":{"success":false,"error":"unknownError","host":"icanhazip.com","packet_loss_percentage":100,"packets_transmitted":null,"packets_received":null,"options":{"timeout_in_seconds":5,"interval":1.0,"packet_size_in_bytes":56,"ttl":64},"timings":{"minimum_time_in_ms":null,"maximum_time_in_ms":null,"average_time_in_ms":null,"standard_deviation_time_in_ms":null},"raw_output":" ping: socktype: SOCK_RAW ping: socket: Operation not permitted ping: => missing cap_net_raw+p capability or setuid? ","lines":[]}} ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-05 04:13:05 +03:00
OVERLORD commented 2026-02-05 04:13:11 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 22, 2025):

its an known upstream error.

https://github.com/alexjustesen/speedtest-tracker/issues/2525

@MickLesk commented on GitHub (Dec 22, 2025): its an known upstream error. https://github.com/alexjustesen/speedtest-tracker/issues/2525
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#2207
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?