SSH Tunneling #2196

New issue

Closed

opened 2026-02-28 02:46:11 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-28 02:46:11 -05:00

Owner

Originally created by @WisdomSky on GitHub (May 18, 2023).

⚠️ Please verify that this feature request has NOT been suggested before.

I checked and didn't find similar feature request

🏷️ Feature Request Type

API

🔖 Feature description

Is there an option to use SSH Tunneling so we can access services which are not publicly accessible (from a remote server)?

We have mysql and mongodb services from other servers that are not externally accessible and I want to monitor it from an uptime kuma instance from different server.

✔️ Solution

none

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @WisdomSky on GitHub (May 18, 2023). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type API ### 🔖 Feature description Is there an option to use SSH Tunneling so we can access services which are not publicly accessible (from a remote server)? We have mysql and mongodb services from other servers that are not externally accessible and I want to monitor it from an uptime kuma instance from different server. ### ✔️ Solution none ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman

2026-02-28 02:46:11 -05:00

closed this issue
added the
feature-request
label

deekerman commented

2026-02-28 02:46:16 -05:00

Author

Owner

@CommanderStorm commented on GitHub (May 18, 2023):

I am assuming your environment is

internal	public
`database`	`backend`, `uptime-kuma`

And the backend also has an uptime monitor.

Would it not be better to include the status of the underlying infrastructure in the backend status?
Reasoning:

This would alert you in case one of the infrastructure pieces goes down
Databases are build like tanks nowadays.
The logs from the backend will tell you clearly that the database is not healthy.
=> not a big downside to include this here
Adding such a tunnel adds extra complexity which you will have to maintain.

Another option is to use the push monitor, i.e. the database tells uptime-kuma periodically that it is healthy. see #279

Do you agree with this assessment?

@CommanderStorm commented on GitHub (May 18, 2023): I am assuming your environment is | internal | public | |--------|--------| | `database` | `backend`, `uptime-kuma` | And the `backend` also has an uptime monitor. Would it not be better to include the status of the underlying infrastructure in the `backend` status? Reasoning: - This would alert you in case one of the infrastructure pieces goes down - Databases are build like tanks nowadays. - The logs from the backend will tell you clearly that the database is not healthy. => not a big downside to include this here - Adding such a tunnel adds extra complexity which you will have to maintain. Another option is to use the `push` monitor, i.e. the `database` tells `uptime-kuma` periodically that it is healthy. see #279 Do you agree with this assessment?

deekerman commented

2026-02-28 02:46:16 -05:00

Author

Owner

@WisdomSky commented on GitHub (May 18, 2023):

Oh I did not know about this. I think this would be a great alternative to ssh tunneling. Thanks for recommending me this option (push monitor).
I think I missed this while browsing the list of monitors.

@WisdomSky commented on GitHub (May 18, 2023): Oh I did not know about this. I think this would be a great alternative to ssh tunneling. Thanks for recommending me this option (push monitor). I think I missed this while browsing the list of monitors.