mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Error 404, on Docker Installation for 2 known working Dockers (out of 20) #2282
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#2282
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 @bmpreston on GitHub (Jun 19, 2023).
⚠️ Please verify that this bug has NOT been raised before.
🛡️ Security Policy
📝 Describe your problem
I've only been using Uptime Kuma for about 12 hours. I believe I have done searches for this, and found errors pertaining to a slash // at the end of a website/domain name. My Uptime functioned throughout the night at began throwing error 404 offlines for 2 Docker instances. Unknown source. I have restarted the 2 dockers in question. Both were functioning, both are functioning now. I have since completely stopped and restarted Docker on my Unraid installation, error persists. Logs have been pulled, I don't see any source of these errors, it just started...
📝 Error Message(s) or Log
{"log":"2023-06-19T00:01:23-04:00 [AUTH] INFO: Successfully logged in user brian@prestons.family. IP=SCRUBBED\n","stream":"stdout","time":"2023-06-19T04:01:23.894943905Z"}
{"log":"2023-06-19T03:01:15-04:00 [MONITOR] WARN: Monitor #4 'DDNS Updater': Pending: Request failed with status code 404 | Max retries: 1 | Retry: 1 | Retry Interval: 60 seconds | Type: docker\n","stream":"stderr","time":"2023-06-19T07:01:15.438854446Z"}
{"log":"2023-06-19T03:01:16-04:00 [MONITOR] WARN: Monitor #11 'Radarr': Pending: Request failed with status code 404 | Max retries: 1 | Retry: 1 | Retry Interval: 60 seconds | Type: docker\n","stream":"stderr","time":"2023-06-19T07:01:16.887466769Z"}
{"log":"2023-06-19T03:02:16-04:00 [MONITOR] WARN: Monitor #4 'DDNS Updater': Failing: Request failed with status code 404 | Interval: 60 seconds | Type: docker | Down Count: 0 | Resend Interval: 0\n","stream":"stderr","time":"2023-06-19T07:02:16.159794725Z"}
{"log":"2023-06-19T03:02:17-04:00 [MONITOR] WARN: Monitor #11 'Radarr': Failing: Request failed with status code 404 | Interval: 60 seconds | Type: docker | Down Count: 0 | Resend Interval: 0\n","stream":"stderr","time":"2023-06-19T07:02:17.232571774Z"}
{"log":"2023-06-19T03:03:16-04:00 [MONITOR] WARN: Monitor #4 'DDNS Updater': Failing: Request failed with status code 404 | Interval: 60 seconds | Type: docker | Down Count: 0 | Resend Interval: 0\n","stream":"stderr","time":"2023-06-19T07:03:16.201994348Z"}
{"log":"2023-06-19T03:03:17-04:00 [MONITOR] WARN: Monitor #11 'Radarr': Failing: Request failed with status code 404 | Interval: 60 seconds | Type: docker | Down Count: 0 | Resend Interval: 0\n","stream":"stderr","time":"2023-06-19T07:03:17.324420224Z"}
{"log":"2023-06-19T03:04:16-04:00 [MONITOR] WARN: Monitor #4 'DDNS Updater': Failing: Request failed with status code 404 | Interval: 60 seconds | Type: docker | Down Count: 0 | Resend Interval: 0\n","stream":"stderr","time":"2023-06-19T07:04:16.258745908Z"}
{"log":"2023-06-19T03:04:17-04:00 [MONITOR] WARN: Monitor #11 'Radarr': Failing: Request failed with status code 404 | Interval: 60 seconds | Type: docker | Down Count: 0 | Resend Interval: 0\n","stream":"stderr","time":"2023-06-19T07:04:17.384971272Z"}
{"log":"2023-06-19T03:05:16-04:00 [MONITOR] WARN: Monitor #4 'DDNS Updater': Failing: Request failed with status code 404 | Interval: 60 seconds | Type: docker | Down Count: 0 | Resend Interval: 0\n","stream":"stderr","time":"2023-06-19T07:05:16.298362511Z"}
{"log":"2023-06-19T03:05:17-04:00 [MONITOR] WARN: Monitor #11 'Radarr': Failing: Request failed with status code 404 | Interval: 60 seconds | Type: docker | Down Count: 0 | Resend Interval: 0\n","stream":"stderr","time":"2023-06-19T07:05:17.448586584Z"}
{"log":"2023-06-19T03:06:16-04:00 [MONITOR] WARN: Monitor #4 'DDNS Updater': Failing: Request failed with status code 404 | Interval: 60 seconds | Type: docker | Down Count: 0 | Resend Interval: 0\n","stream":"stderr","time":"2023-06-19T07:06:16.347383994Z"}
{"log":"2023-06-19T03:06:17-04:00 [MONITOR] WARN: Monitor #11 'Radarr': Failing: Request failed with status code 404 | Interval: 60 seconds | Type: docker | Down Count: 0 | Resend Interval: 0\n","stream":"stderr","time":"2023-06-19T07:06:17.49067831Z"}
{"log":"2023-06-19T03:07:16-04:00 [MONITOR] WARN: Monitor #4 'DDNS Updater': Failing: Request failed with status code 404 | Interval: 60 seconds | Type: docker | Down Count: 0 | Resend Interval: 0\n","stream":"stderr","time":"2023-06-19T07:07:16.397953359Z"}
{"log":"2023-06-19T03:07:17-04:00 [MONITOR] WARN: Monitor #11 'Radarr': Failing: Request failed with status code 404 | Interval: 60 seconds | Type: docker | Down Count: 0 | Resend Interval: 0\n","stream":"stderr","time":"2023-06-19T07:07:17.546805414Z"}
🐻 Uptime-Kuma Version
1.21.3
💻 Operating System and Arch
Unraid 6.12.0
🌐 Browser
Google Chrome on Version 114.0.5735.133
🐋 Docker Version
23.0.6
🟩 NodeJS Version
null
@CommanderStorm commented on GitHub (Jun 19, 2023):
Is there something that is different for these tow docker insances?
Are they in a different docker-network/... ?
What do these two instances have in common?
What do you mean by
(slashes at the end of URLs are different URLs)
Longshot: What is the amount of pings you have set up and is your storage slow?
@bmpreston commented on GitHub (Jun 19, 2023):
So I figured it out. These are set for Docker, and both were updated at 0300. They must have a new container ID. (Confirming now). Confirmed. They pulled new images and the container ID is not the same. How might I set this up for Docker and not worry about continuously changing IDs.
The questions asked when submitted a ticket is 'have you searched for this issue before.'
@CommanderStorm commented on GitHub (Jun 19, 2023):
Cannot reproduce:
@CommanderStorm commented on GitHub (Jun 19, 2023):
If your problem is resolved, could you close this issue?
@bmpreston commented on GitHub (Jun 19, 2023):
It is not resolved. I'm wondering how to keep the Docker sock from
creating new IDs on each upgrade.
On Mon, Jun 19, 2023 at 12:20 PM Frank Elsinga @.***>
wrote:
@bmpreston commented on GitHub (Jun 19, 2023):
I'm confused. My text wasn't to the quote, but the question was asked, 'I checked and didn't find similar issue'. I then typed "I believe I have done searches for this, and found errors pertaining to a slash // at the end of a website/domain name."
I was answering the question of the form...
@bmpreston commented on GitHub (Jun 19, 2023):
I have figured out that you cannot use the container ID as it changes per Docker reload.
As such I changed to the container name and all is well.
Thanks!