question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Version 1.7.0 breaks ping for local devices

See original GitHub issue

Describe the bug After updating to version 1.7.0, all my ping monitors for local devices are broken. Prior to v1.7.0 these worked just fine - for example:

Monitor type: Ping Hostname: local IP address - i.e. 192.168.1.21

The above worked just fine before updating to v1.7.0, but now they’re all borked.

To fix, I have to change to:

Monitor type: TCP Port Hostname: local IP address - i.e. 192.168.1.21 Port: 80 (for example, I’m running Pi-Hole on the above local IP address so port 80 is the web UI).

Expected behavior The pings should work still as nothing has changed. Testing manually via a terminal (i.e. ping 192.168.1.21 -c 10 works as expected. The expected behaviour is that the ping monitor should “just work”.

Info Uptime Kuma Version: 1.7.0 Using Docker?: Yes Docker Version: 20.10.3 build b35e731 OS: Synology DSM Browser: Brave / Chrome

Error Log "Device name": Failing: ping: socket: Operation not permitted

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:15 (7 by maintainers)

github_iconTop GitHub Comments

2reactions
raspberrycouliscommented, Sep 28, 2021

Update: @louislam / @nbvcxz - running as root on the latest image resolves the issue, so definitely a permissions issue.

I’m using a compose file with version 3.5, so the parameters are:

    environment:
      - PUID=0
      - PGID=0

Hope this helps!

1reaction
louislamcommented, Sep 29, 2021

Fixed in 1.7.1.

Will try to find out how to reproduce the problem.

Read more comments on GitHub >

github_iconTop Results From Across the Web

How Do I Troubleshoot a Ping Failure or Packet Loss Using a ...
Symptom. When you accessed other resources from an ECS, network freezing occurred. The ping command output showed that packet loss occurred ...
Read more >
How do I resolve a "request timed out" when pinging? - Quora
It happens because of two reasons: 1. Your computer does not have connectivity to the pinged site/address. You need to ensure that you...
Read more >
Ping command basics for testing and troubleshooting - Red Hat
The timeout message indicates that your machine believes it successfully sent ping queries to the destination. However, it did not receive ...
Read more >
Possible UDM bug associated with DNS Filters feature
In its default state, local DNS hostname resolution for DHCP clients works as expected on the ... Ping, nslookup, and dig all failed...
Read more >
Troubleshoot the PingID desktop app
pingauthorize_ce ; pf_ce; pfb_ce; pingaccess_ce; pingintelligence_ce ... Configuring an authenticating from new device rule (web policy) ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found