RE: HTTPS connection to mmonit

[Jamie Burchell]

It doesn't matter where the server is as long as you can create an SSH
connection to it. Usually this is port 22 (on the server).
The software used on your client machine to create the ssh connection
depends on your operating system. For Linux, Mac and Windows Subsystem for
Linux ssh is already available to use as a command.

Once you've established a connection, local port 2812 on your client is
forwarded to remote port 2812 on your server, through the ssh tunnel.
In the monirc config, you will need at least

set httpd port 2812
  use address localhost
  allow localhost

I can't comment on m/monit I'm affarid as I haven't used it.

-----Original Message-----
From: monit-general [mailto:address@hidden
On Behalf Of Mr Subs
Sent: 01 May 2019 17:09
To: This is the general mailing list for monit <address@hidden>
Subject: Re: HTTPS connection to mmonit

Jamie,

This looks interesting, but it is not something I have used before, so I
have some questions:

1. My server is located in the cloud, so my client is not on the same
network. Where does this port mapping occur - client or server?
2. How do I configure mmonit on my server?

Any advice welcome!

Thanks

> On 1 May 2019, at 13:50, Jamie Burchell <address@hidden> wrote:
>
> If you already have SSH access to the server, you could also access
> the web interface over SSH by using port forwarding.
>
> This is great because the connection is encrypted (there's no need to
> mess around with HTTPS or certificates), there's no need to open any
> additional firewall ports and the web UI remains locked down from the
public.
>
> E.g:
>
> ssh -L 2812:127.0.0.1:2812 your-server-ip
>
> Then the web UI is available at 127.0.0.1:2821 in your browser.
>
> -----Original Message-----
> From: monit-general
> [mailto:address@hidden
> On Behalf Of Jan-Henrik Haukeland
> Sent: 01 May 2019 00:45
> To: This is the general mailing list for monit
> <address@hidden>
> Subject: Re: HTTPS connection to mmonit
>
>
>> On 1 May 2019, at 01:14, Jan-Henrik Haukeland <address@hidden>
> wrote:
>>
>> You must then access mmonit using https://<your-ip-address>/
>
> PS. Which of course kind of defy using SSL (where a certificate is for
> a domain/host name in DNS), but if you are using a self-signed
> certificate that might not be super important and you can as well use
> the IP-address directly. BTW, I forgot, as you configured M/Monit the
> URL needs to include the port number also,  so the URL will be,
> https://172.31.24.86:8443/ apparently your host running M/Monit has
> IP-address 172.31.24.86
> --
> To unsubscribe:
> https://lists.nongnu.org/mailman/listinfo/monit-general
>
> --
> To unsubscribe:
> https://lists.nongnu.org/mailman/listinfo/monit-general


-- 
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general