ports check broken? about uptime-kuma HOT 25 CLOSED

used to work fine for me and then stopped and still does not

Software normally does not stop working without external effects ("admins/users mucking with it"). => Bisect the changes you did when the changes occured.

What is the next way to get more detail logs from uptime kuma to troubleshoot

You can exec inside the container and then progressively go outward.
We have documented how to do this partially in https://github.com/louislam/uptime-kuma/wiki/Troubleshooting#uptime-kuma-reports-down-but-the-service-can-be-accessed

It works on https://uptime.kuma.pet/ as expected.

from uptime-kuma.

No, I can confirm it working on my end.

How have you deployed our software?
Could it be the case that you have it deployed via docker and are targetting a local network?
In this case please have a look at https://docs.docker.com/network/

For using the host network the correct addition to the docker command would be --network=host

from uptime-kuma.

My URL is external and HTTPS Emby server

from uptime-kuma.

If the url is external, could you share the ip/port of said service?

from uptime-kuma.

If the url is external, could you share the ip/port of said service?

Let me look for a public server as an example (I'd like to avoid sharing mine publicly)

from uptime-kuma.

You can share it to me via my email adress if you'd prefer:

from uptime-kuma.

Check you email 😉

from uptime-kuma.

Sorry, but I cannot reproduce said ip responding to a tcp connection.

I think you are misunderstanding something:

• TCP port is the equivalent of telnet IP PORT
• https://portchecker.co/ checks for "open ports".

it is unclear to me what mechanism they use, to determine this, best I can think of is

from uptime-kuma.

@CommanderStorm
I am blocking non-US inbound traffic and that's why you could not telnet to it.
I disabled the block now. Can you retry?
TIA

from uptime-kuma.

After disabling the geoblock this started working as expected.

from uptime-kuma.

Pls paste your setup of this ping

from uptime-kuma.

[REDACTED]

Above was a screenshot of the heartbeat setup as requested by the user in the previous comment.
Ip goes into the HOSTNAME and Port goes into the PORT field

If there is a field that needs better UX, feedback is appreciated.

from uptime-kuma.

It's odd. It used to work fine for me and then stopped and still does not.

I guess it's some combination of odd things.

What is the next way to get more detail logs from uptime kuma to troubleshoot?

from uptime-kuma.

If there is a field that needs better UX, feedback is appreciated

please remove the IP !

from uptime-kuma.

used to work fine for me and then stopped and still does not

Software normally does not stop working without external effects ("admins/users mucking with it"). => Bisect the changes you did when the changes occured.

What is the next way to get more detail logs from uptime kuma to troubleshoot

You can exec inside the container and then progressively go outward. We have documented how to do this partially in https://github.com/louislam/uptime-kuma/wiki/Troubleshooting#uptime-kuma-reports-down-but-the-service-can-be-accessed

It works on https://uptime.kuma.pet/ as expected.

Not for me:

Tried on my network and a different network

And in the same settings, facebook works as expected:

Something fishy :)

from uptime-kuma.

I restored an old version of UK from last November with the hope it would work, but no it shows the same problem.

Very interesting...

from uptime-kuma.

@CommanderStorm how can you check the port on the same node where UK runs via the command line tool?
Cam you try it for me pls?
Thx

from uptime-kuma.

If I run a temporary docker container in the same network, they are consistent with each other => your service does not respond to my requests.

docker run -it --network=host louislam/uptime-kuma:1.23.11

I get these results:

from uptime-kuma.

I am blocking non-US inbound traffic

Note that you likely re-enabled this block. Remember that I am doing this from a residential, German internet access.

from uptime-kuma.

I don't run docker 😞
Anything else you can use?

from uptime-kuma.

Try any external port pls

from uptime-kuma.

I don't know what you mean by any external port. I tried this already as noted above:
The ip+port you specified are external to me, and they don't want to connect to me.

Here is what telnet should look like if a website wants to connect via TCP:

from uptime-kuma.

I don't run docker 😞 Anything else you can use?

You are likely searching at the wrong spot.
From my perspective, your service is either geo-locked, defective or not at said ip + port any more.

from uptime-kuma.

I don't run docker 😞 Anything else you can use?

You are likely searching at the wrong spot. From my perspective, your service is either geo-locked, defective or not at said ip + port any more.

My ports are definitely open. Yes I block all traffic from non-US.
I suspect the issue is the way UK was deployed via https://tteck.github.io/Proxmox/

Sorry for being unclear.
All I need help with is to check a port via the command line (on Debian), so I can compare.
I bet the port won't check as open from the same node as UK is installed.

By "any" port I meant it does not have to be my port :)

from uptime-kuma.

Yup confirmed - the port is not checkable.
Why - who knows?!
Workaround - use local LAN IP address instead of an external host name

from uptime-kuma.