mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Notification via Apprise results in "No module named 'six'" #1242
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#1242
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 @danijelst on GitHub (Jul 8, 2022).
⚠️ Please verify that this bug has NOT been raised before.
🛡️ Security Policy
Description
I'm using Homeassistant to run the Uptime Kuma via the Addon.
I wanted to define a notification config and use Apprise to push to Homeassistant. However the UI returning "No output from apprise" when I press test.
Further test was done via docker, see result in the Expected behaviour description.
👟 Reproduction steps
Case via UI
Case via Docker
apprice -vvv hassio://myhassio/mylonglivedaccesstoken👀 Expected behavior
Receive a notification in Homeassistatnt
😓 Actual Behavior
Nothing happens in the UI
but the docker returns
🐻 Uptime-Kuma Version
1.16.1
💻 Operating System and Arch
Alpine Linux v3.16
🌐 Browser
Brave
🐋 Docker Version
20.10.14
🟩 NodeJS Version
No response
📝 Relevant log output
No response
@louislam commented on GitHub (Jul 9, 2022):
Currently, Uptime Kuma bundled Apprise 0.9.8.
I suggest you should try Apprise 0.9.9. If it is still not working.
You should report to Apprise's repo.
https://github.com/caronc/apprise/issues/626
@caronc commented on GitHub (Jul 9, 2022):
I'm not sure if this is an issue with Apprise. Unless
sixis a package that is no longer supported. But as far as i can tell this isn't the case (source). I would guess that thesixpackage didn't get pulled into the environment correct perhaps or there is a conflicting package in it?sixis still very much a part of the Appriserequirements.txt.My best guess is that this is not a bug at all and related to the current users environment and/or how he installed Apprise.
Perhaps a
pip install appriseorpip install -r requirements.txtis all that is required?@louislam commented on GitHub (Jul 9, 2022):
Oh, I just realize that @danijelst is not using the official Uptime Kuma docker image.
I checked the addon, they actually didn't follow my Dockerfile.
https://github.com/hassio-addons/addon-uptime-kuma/blob/main/uptime-kuma/Dockerfile
For Alpine, it have to install many packages in order to get it working.
github.com/louislam/uptime-kuma@a78cb7ab42/docker/alpine-base.dockerfile (L6-L8)Honestly, I don't know why people would like to reinvent my Dockerfile.
I would highly recommended that you should use my official docker image. It is a bit newer and I believe it is no such bug.
@danijelst commented on GitHub (Jul 10, 2022):
Thank you very much for your help. I have switched to the official image and then it works. I will later create an issue in the addon's repository so that they can fix resp. switch to the official docker.