Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


    Cloudron Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Add New Monitor - Accepted Status Codes

    Uptime Kuma
    3
    4
    17
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • FremieMico
      FremieMico last edited by

      Wasn't able to find any viable solution for this one, hoping someone will be able to help out.

      We're trying to add certain websites on Uptime Kuma to monitor their Certificate Expiration Dates. Do we need to follow strict Status Codes on it? Like if we wanted certificates should we only use 400-499 every time?

      Using the curl method ( curl -i website link ) on cmd/terminal to check seems like a hit or miss most of the time

      1 Reply Last reply Reply Quote 1
      • fbartels
        fbartels App Dev last edited by

        hmm.. I think it depends on the actual website. A status code in the range of 400-499 would be a return code that signals a kind of error (file not found, or unauthenticated). So if you normally curl your website and get a 403 then it would make sense to use it.

        Generally I would say even if you only monitor because you want to get a certificate expiry I would monitor for the expected http return as well. If the / of your website is huge, you could create some kind of dummy file on your webserver that you query instead. For a wordpress site I am monitoring I am querying the license file for example.

        1 Reply Last reply Reply Quote 1
        • girish
          girish Staff last edited by girish

          In uptime kuma, the cert check is an option of http status check. Technically, the cert check happens before the http request. You would do something like openssl s_client -connect cloudron.io:443 -showcerts .

          I see that uptime kuma does not have this cert check as a separate thing and neither is it part of the TCP check type (maybe, you can suggest upstream to add a TCPS type. this will help in checking mail server and other services as well like jabber, matrix maybe).

          If the goal is only to check the certs, I would put the HTTP status code range as 100-500 as a workaround since one can safely ignore this....

          1 Reply Last reply Reply Quote 3
          • girish
            girish Staff last edited by

            BTW, if you end up opening upstream for TCPS, you should also tell them to add STARTTLS as an option.

            openssl s_client -connect mail.domaincom:25 -showcerts -starttls smtp will help test the cert of a mail server for protocols like sieve, smtp that use starttls.

            1 Reply Last reply Reply Quote 2
            • First post
              Last post
            Powered by NodeBB