uptime kuma
I installed using docker cmd then from 7080 openlitespeed performed all this
OpenLiteSpeed
Create a new virtual host through the graphical admin like you normally would.
Basic tab
- Name:
uptime-kuma
- Virtual Host Root:
/path/to/uptime-kuma
- Enable Scripts/ExtApps:
Yes
External app tab
- Add a
web server
app type - Name:
uptime-kuma
- Address:
http://localhost:3001
Context tab
- Add a
proxy
context - URI:
/
- Web Server:
[VHost Level]: uptime-kuma
- Header Operations:
Upgrade websocket Connection upgrade
- Access Allowed:
*
Web Socket Proxy tab
- Add a
Web Socket Proxy Setup
- URI:
/
- Address:
127.0.0.1:3001
SSL tab (if needeed)
- Private Key File:
/path/to/ssl/key/privkey.pem
- Certificate File:
/path/to/ssl/cert/fullchain.pem
- Chained Certificate:
yes
Perform a graceful restart and launch uptime-kuma.
getaddrinfo EAI_AGAIN earnmoneyonline.vip
4f5e350a8484 mariadb:10.8 "docker-entrypoint.s…" 2 weeks ago Up 12 days 3306/tcp pushbluster_mariadb
root@server2:/mnt# docker start uptime-kuma
Error response from daemon: driver failed programming external connectivity on endpoint uptime-kuma (1d8d3e9e91ed6ffbd99c1958c6ba8f56778f08a792d94e82850e11888a79ac29): (iptables failed: iptables --wait -t nat -A DOCKER -p tcp -d 0/0 --dport 3001 -j DNAT --to-destination 172.17.0.2:3001 ! -i docker0: iptables: No chain/target/match by that name.
Something has deleted the docker iptables entries. Docker will recreate them if you restart it (systemctl restart docker
). You'll want to disable anything else that manages iptables to prevent this from happening in the future.
how to migrate dockerized uptime-kuma to a different server
I think if you installed using the docker based instructions:
docker volume create uptime-kuma
You would do the same install at the new server, and then here is the directory that you would need to copy everything from, into the same location at new server
/var/lib/docker/volumes/uptime-kuma/_data
Comments
Post a Comment