Cloudron Forum

Smokeping stands out for its ability to provide detailed, long-term network latency and performance monitoring through highly visual, customizable charts, making it an indispensable tool for maintaining network reliability. With Docker images readily available, integrating Smokeping into Cloudron’s app store should be fairly straightforward.

SmokePing is ...

• extensible through plug-in modules
• easy to customize through a webtemplate and an extensive configuration file.
• written in perl and should readily port to any unix system
• an RRDtool frontend
• able to deal with DYNAMIC IP addresses as used with Cable and ADSL internet.

https://oss.oetiker.ch/smokeping/
https://oss.oetiker.ch/smokeping/pub/
https://github.com/oetiker/SmokePing
https://hub.docker.com/r/linuxserver/smokeping
https://hub.docker.com/r/divyavanmahajan/smokeping
https://github.com/jwigley/docker-smokeping-speedtest

Demo:
https://smokeping.oetiker.ch/?target=Customers.OP

This would be a great addition. Tried it once, finding it a bit rough around the edges but the core functionality is definitely there.

@michaelpope Uptime Kuma caters to a completely different use case, although, there is some overlap e.g. webhook reporting and notification. I am running several instances of both, Uptime Kuma and healthchecks in production

Yes, this would be great. However, multi-tenancy might present some challenges due to the service ports required by the Unifi Controller, especially for device discovery. That said, as long as L3 adoption is implemented (e.g. via DNS or DHCP option), using a dedicated custom set of ports for each instance should work fine.

See also; https://help.ui.com/hc/en-us/articles/218506997-Required-Ports-Reference

Hi everyone,

A customer using Safari on Apple iOS 18 is unable to access any apps that rely on the managed WordPress app.

Before I investigate further, could someone try replicating this issue?

Initial test with SSL Test Labs comes back clean:

Apparently it's working on a freshly deployed managed wordpress app. So it's probably something with the htaccess configuration or some plugin related problems.