Possibility to check for HTTPs with self-signed certificates #12

New issue

Closed

opened 2026-02-28 01:31:40 -05:00 by deekerman · 4 comments

deekerman commented

2026-02-28 01:31:40 -05:00

Owner

Originally created by @xorguy on GitHub (Jul 12, 2021).

HI.

It will be handy to be able to override and check for servers (HTTPS) with self signed certificates.

Thanks.

Originally created by @xorguy on GitHub (Jul 12, 2021). HI. It will be handy to be able to override and check for servers (HTTPS) with self signed certificates. Thanks.

deekerman

2026-02-28 01:31:40 -05:00

closed this issue
added the
feature-request
label

deekerman commented

2026-02-28 01:31:45 -05:00

Author

Owner

@fire1ce commented on GitHub (Jul 30, 2021):

This should be top priority for the self hosted community

@fire1ce commented on GitHub (Jul 30, 2021): This should be top priority for the self hosted community

deekerman commented

2026-02-28 01:31:45 -05:00

Author

Owner

@Expro commented on GitHub (Jul 30, 2021):

Definitely. Ability to add custom CA and certificates would be very valuable. Or, as workaround, ability to ignore certificate errors,

@Expro commented on GitHub (Jul 30, 2021): Definitely. Ability to add custom CA and certificates would be very valuable. Or, as workaround, ability to ignore certificate errors,

deekerman commented

2026-02-28 01:31:45 -05:00

Author

Owner

@joe-eklund commented on GitHub (Jul 30, 2021):

Definitely. Ability to add custom CA and certificates would be very valuable. Or, as workaround, ability to ignore certificate errors,

Fwiw, you can inject your own CA or ignore all SSL cert issues by setting some environment variables. This can be accomplished by doing the following (note this is a docker stack file for docker swarm, but docker-compose is close. Really pay attention to the volumes and env variables, which shouldn't matter if on swarm or not):

version: "3.8"
services:
  uptime_kuma:
    image: louislam/uptime-kuma
    volumes:
       - /uptime_kuma/data:/app/data
       - /uptime_kuma/certs:/certs
    deploy:
      restart_policy:
        condition: any
    ports:
      - 3001:3001
    environment:
      - NODE_EXTRA_CA_CERTS=/certs/ca-bundle.crt # inject your CA.
      #-NODE_TLS_REJECT_UNAUTHORIZED=0 # ignore ssl issues, potentially dangerous but useful for testing :)

@louislam maybe you could add some documentation in the readme or wiki on how to do this since it seems to be a common question?

@joe-eklund commented on GitHub (Jul 30, 2021): > Definitely. Ability to add custom CA and certificates would be very valuable. Or, as workaround, ability to ignore certificate errors, Fwiw, you can inject your own CA or ignore all SSL cert issues by setting some environment variables. This can be accomplished by doing the following (note this is a docker stack file for docker swarm, but docker-compose is close. Really pay attention to the volumes and env variables, which shouldn't matter if on swarm or not): ``` version: "3.8" services: uptime_kuma: image: louislam/uptime-kuma volumes: - /uptime_kuma/data:/app/data - /uptime_kuma/certs:/certs deploy: restart_policy: condition: any ports: - 3001:3001 environment: - NODE_EXTRA_CA_CERTS=/certs/ca-bundle.crt # inject your CA. #-NODE_TLS_REJECT_UNAUTHORIZED=0 # ignore ssl issues, potentially dangerous but useful for testing :) ``` @louislam maybe you could add some documentation in the readme or wiki on how to do this since it seems to be a common question?

deekerman commented

2026-02-28 01:31:45 -05:00

Author

Owner

@louislam commented on GitHub (Aug 3, 2021):

Implemented in 1.0.8

https://github.com/louislam/uptime-kuma/releases/tag/1.0.8

@louislam commented on GitHub (Aug 3, 2021): Implemented in 1.0.8 https://github.com/louislam/uptime-kuma/releases/tag/1.0.8

deekerman referenced this issue

2026-02-28 01:32:22 -05:00

[Feature Request] Service Grouping #26

deekerman referenced this issue