Startup error: Failed to check for announcements #1365
Labels
No labels
Blocked
Bug
Cherry-picking
Database
Dependencies
Dependencies/Renovate
Difficulty
Easy
Difficulty
Hard
Difficulty
Medium
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/E2EE
Matrix/Federation
Matrix/Hydra
Matrix/MSC
Matrix/Media
Matrix/T&S
Meta
Meta/CI
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
Support
To-Merge
Wont fix
old/ci/cd
old/rust
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
continuwuation/continuwuity#1365
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?
Hi,
I updated the image Docker to version 0.5.4 and I have this error in the logs:
I use Element and I have same error log in Admin Room.
Thanks.
That means that your server failed to check for a new announcement, like this one:
I'm working on making this warning more informative, but it's fine to ignore - we post more requent updates in our announcements channel.
Yes, I realize that it's to display something like that, but have I overlooked something that's preventing it from working?
Error logs : check for announcementsto Startup error: Failed to check for announcementsThis also caused me pain when first provisioning. I wasn't sure if there was a problem on the remote/announcement end, or if it was an indication that something was broken on my Continuwuity implementation.