mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Cloudflare Tunnel: not installed #1150
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#1150
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @zxmacc on GitHub (Jun 8, 2022).
⚠️ Please verify that this bug has NOT been raised before.
🛡️ Security Policy
📝 Describe your problem
Sorry, I'm a little confused about how to configure this.

I saw a reverse proxy setup showing CloudFlared Tunnel: not installed
Do I need to install this Cloudflare Tunnel by myself?
sorry to disturb
🐻 Uptime-Kuma Version
1.16.1
💻 Operating System and Arch
Railway (Heroku Buildpacks)
🌐 Browser
Microsoft Edge 102.0.1245.33
🐋 Docker Version
Unknown, possibly new
🟩 NodeJS Version
Unknown, possibly new
@chakflying commented on GitHub (Jun 8, 2022):
Did you configure the custom docker file as mentioned here? We don't put the dockerfile in project root so it's most likely not detected.
@zxmacc commented on GitHub (Jun 8, 2022):
Thank you, docker deployment is now available
But there's still a little problem
@zxmacc commented on GitHub (Jun 8, 2022):
--> docker host: 20.10.12 linux x86_64
[+] Building 0.0s (0/1)
[+] Building 34.7s (11/12)
=> [internal] load remote build context 0.0s
=> copy /context / 0.2s
=> [internal] load metadata for docker.io/louislam/uptime-kuma:base-debian 2.5s
=> [build 1/4] FROM docker.io/louislam/uptime-kuma:base-debian@sha256:a2628f4746a8ca7f690c95e87caee95effb030f68d6e28b 0.0s
=> CACHED [build 2/4] WORKDIR /app 0.0s
=> [build 3/4] COPY . . 0.1s
=> [build 4/4] RUN npm ci --production && chmod +x /app/extra/entrypoint.sh 24.9s
=> CACHED [upload-artifact 2/7] RUN apt update && apt --yes install curl file 0.0s
=> [upload-artifact 3/7] COPY --from=build /app /app 3.1s
=> [upload-artifact 4/7] RUN chmod +x /app/extra/upload-github-release-asset.sh 0.5s
=> ERROR [upload-artifact 5/7] RUN cd /app && tar -zcvf dist.tar.gz dist 0.5s
Error error building: executor failed running [/bin/sh -c cd /app && tar -zcvf $DIST dist]: exit code: 2
@zxmacc commented on GitHub (Jun 8, 2022):
I tried Railway and fly.io, both stopped deployment due to the same problem. I don't know why
@zxmacc commented on GitHub (Jun 8, 2022):
Sorry, I'm not very good at deployment
@zxmacc commented on GitHub (Jun 8, 2022):
I don't understand why. I tried Base-Alpine and it didn't work either
2022-06-08T12:49:27.000 [info] Unpacking image
2022-06-08T12:49:37.000 [info] Preparing kernel init
2022-06-08T12:49:39.000 [info] Configuring firecracker
2022-06-08T12:49:39.000 [info] Starting virtual machine
2022-06-08T12:49:39.000 [info] Starting init (commit: e3eb6d2)...
2022-06-08T12:49:39.000 [info] Preparing to run:
/usr/bin/dumb-init -- extra/entrypoint.sh node server/server.jsas root2022-06-08T12:49:39.000 [info] 2022/06/08 12:49:39 listening on [fdaa:0:4f32:a7b:aca:8544:7458:2]:22 (DNS: [fdaa::3]:53)
2022-06-08T12:49:39.000 [info] ==> Performing startup jobs and maintenance tasks
2022-06-08T12:49:39.000 [info] chown: /app/data: No such file or directory
2022-06-08T12:49:40.000 [info] Main child exited normally with code: 1
2022-06-08T12:49:40.000 [info] Starting clean up.
***v1 failed - Failed due to unhealthy allocations - no stable job version to auto revert to and deploying as v2