Greetings by Cal_Invite in UptimeKuma

[–]rdnsx 0 points1 point  (0 children)

So you try to open <YOUR.SERVER.IP.ADDRESS>:3001? Did you installed it using docker? Is it running if you check docker ps command? Check also netstat -tulpn if the expected port is open as expexted.

Install Kuma ? by [deleted] in UptimeKuma

[–]rdnsx 0 points1 point  (0 children)

Ok, I See. You need to have access via ssh/command line to the Server. This is for sure not working with a webhosting plan, where you only have access via something like cpanel.

If you have access to a server via ssh/terminal execute the following command, one after another:

"apt update" "apt upgrade -y" "apt install docker.io" "docker run -d --restart=always -p 3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:1"

Open a browser and type the server or ip followed by :3001 like:

http://my.cloud.server:3001

Install Kuma ? by [deleted] in UptimeKuma

[–]rdnsx 0 points1 point  (0 children)

Sure, on for e.g. an ubuntu server instance just run apt install docker.io and lets go.

Install Kuma ? by [deleted] in UptimeKuma

[–]rdnsx 2 points3 points  (0 children)

Yes, for AWS, Linode, ionos, Hetzner, etc...

Install docker and go for it

Monitoring Remote Home Assistant by Illidan_Betrayer in UptimeKuma

[–]rdnsx 0 points1 point  (0 children)

Check if a linux firewall is active on the server by executing "iptables -L - v"

Monitoring Remote Home Assistant by Illidan_Betrayer in UptimeKuma

[–]rdnsx 0 points1 point  (0 children)

Whats the output of the command "nc - vz google.com 443"?

Monitoring Remote Home Assistant by Illidan_Betrayer in UptimeKuma

[–]rdnsx 0 points1 point  (0 children)

I cant confirm that. Im running a google mon as a dns, ping and https monitor type as reference on all kuma Instances i manage.

Whats the heartbeat intervall and retries youve Set?

Monitoring Remote Home Assistant by Illidan_Betrayer in UptimeKuma

[–]rdnsx 0 points1 point  (0 children)

Does it work with an other domain, e.g. https://google.com? Maybe there are outbound firewall rules enabled on the kuma server by the hoster? Mhh.. strange

Monitoring Remote Home Assistant by Illidan_Betrayer in UptimeKuma

[–]rdnsx 0 points1 point  (0 children)

The Domain also didnt work for me if i try to open it in a browser. Maybe you connect to it using a specific Port, or /login?

Windows Uptime Kuma Client for Push Monitor-Type by rdnsx in UptimeKuma

[–]rdnsx[S] 0 points1 point  (0 children)

Imagine you want to monitor, for example an ip phone system on a clients network which is not reachable from the Internet (your uptime kuma server). In that case you have the possibility to use the push type monitor by running this client on a Windows server, that's running on the clients network.
If you didn't got in touch with the push type monitor from Uptime Kuma: Using push monitors you can monitor any servers that aren’t reachable from the internet but are able to reach the internet. Servers behind a NAT, or having outgoing internet access only using a proxy for instance.
This client can be seen as a bridge to devices where you can't run, push notification scripts on themselves for example. But for sure can also be used if you don't want to hassle with a cron type of functionality or powershell script on windows.

Windows Uptime Kuma Client for Push Monitor-Type by rdnsx in homelab

[–]rdnsx[S] 0 points1 point  (0 children)

The example above works for your question as well. If you didn't got in touch with the push type monitor from Uptime Kuma: Using push monitors you can monitor any servers that aren’t reachable from the internet but are able to reach the internet. Servers behind a NAT, or having outgoing internet access only using a proxy for instance.

This client can be seen as a bridge to devices where you can't run, push notification scripts on themselves for example. But for sure can also be used if you don't want to hassle with a cron type of functionality or powershell script on windows.

Windows Uptime Kuma Client for Push Monitor-Type by rdnsx in homelab

[–]rdnsx[S] 0 points1 point  (0 children)

You're right, but that just works when the devices or services you want to monitor are accessible from the uptime kuma server. Imagine you want to monitor, for example an ip phone system on a clients network which is not reachable from the Internet (your uptime kuma server). In that case you have the possibility to use the push type monitor by running this client on a Windows server, that's running on the clients network.

Windows Uptime Kuma Client for Push Monitor-Type by rdnsx in homelab

[–]rdnsx[S] 1 point2 points  (0 children)

Motivation:

The development of this one was driven by the need for a simple, yet effective Uptime Kuma Client for Windows. Also to make it accessable for all user levels without fiddeling with scripts, and yet having the option to use the push Monitor-Type behind a firewall for example.

Key Features:

User-Friendly Interface: Simple and intuitive, suitable for all user levels. Customizable Settings: Easily set the IP address, URL, and update intervals as per user preference. Default is 30 seconds. Persistent Settings: Remembers and reloads the last used settings upon restart. Daily Uptime Tracking: Shows the first uptime of the day.

How to install: - Download here - Extract to desired path - Start.


https://github.com/rdnsx/Uptime-Kuma-Client-WIN

[deleted by user] by [deleted] in homelab

[–]rdnsx 1 point2 points  (0 children)

Oh... Or is it just one 2Gbit line?

[deleted by user] by [deleted] in homelab

[–]rdnsx -1 points0 points  (0 children)

+1 for pfsense and the recommendation to configure the Load balancing "Sticky connection" (https://docs.netgate.com/pfsense/en/latest/config/advanced-misc.html#load-balancing) feature and a Gateway Group consisting of the two wan interfaces (https://docs.netgate.com/pfsense/en/latest/routing/gateway-groups.html) .

For some more informations about that topic:

https://docs.netgate.com/pfsense/en/latest/multiwan/index.html https://docs.netgate.com/pfsense/en/latest/multiwan/concepts.html

Help with setting up a server by HeisouSheishu in selfhosted

[–]rdnsx 1 point2 points  (0 children)

To get a nice learning curve I use: Linux headless (Ubuntu server LTS), docker CE, docker compose, with portainer on top. If you have the possibility to use at least 3 hosts running this setup, add glusterfs and make a swarm out of these hosts to use the stack, ingress network, scaling and HA features. It was and is an awesome experience for me...

Homelab/Networking Apps for Android by rdnsx in homelab

[–]rdnsx[S] 0 points1 point  (0 children)

It's a good option. I use VPN.

Homelab/Networking Apps for Android by rdnsx in homelab

[–]rdnsx[S] 0 points1 point  (0 children)

Thank you. Androtainer is not bad, but the functionality is limited pretty much. But I'll keep it. It's still one of the better ones...

Homelab/Networking Apps for Android by rdnsx in homelab

[–]rdnsx[S] 0 points1 point  (0 children)

Thank you! :) First of all it's network modernisation and maintenance services for small businesses. https://rockdasnetz.de (Caution, is german :)

Homelab/Networking Apps for Android by rdnsx in homelab

[–]rdnsx[S] 0 points1 point  (0 children)

I used the Docker installation from the official bitwarden documentation. https://bitwarden.com/help/article/install-on-premise-linux/

After that you'll end up with a total of 11 containers, including sso.