[19:54:06] @agentisai WT phorge daemons need a restart [19:54:32] Also, at least for me, images aren’t working [20:04:31] Hrm, I'm not able to reproduce any image issues. MacFan4000, is there a particular problem you're seeing? [20:05:21] @notaracham on either phorge install images don’t show up [20:11:30] Ahhh, phorge-specific then [22:14:30] Is https://issue-tracker.wikitide.org/ open to all WikITide users? [22:18:43] Yep, though right now you do need to be logged in to see tickets by default, we're looking into updating that [22:33:50] why do I get this? [22:44:31] [1/2] Guessing this is the phorge daemon issue mentioned by MacFan4000 earlier. You're getting this on issue-tracker.wikitide.org? [22:44:31] [2/2] Adding @Site Reliability Engineers for visibility. [22:50:40] Visibility is an easy fix - just needs an admin to change Default view policy to public on https://issue-tracker.wikitide.org/applications/view/PhabricatorManiphestApplication/ [22:51:09] Well hey, excellent! Thanks, MacFan. [22:51:18] Can’t see the image though so no idea what the reported problem is [22:51:37] (Doesn’t come through the relay) [22:53:03] [1/7] PhutilAggregateException [22:53:03] [2/7] All storage engines failed to write file [22:53:03] [3/7] 403 error [22:53:03] [4/7] AWS request failed, access key does not exist in records [22:53:04] [5/7] and [22:53:04] [6/7] PhutilAWS exception [22:53:04] [7/7] AWS request failed, same general error as above [22:53:37] That sounds like it may be related to the images issue [22:54:05] Daemons are responsible for sending email, updating feeds and repos, etc [22:54:08] Likely so, guessing either an out of space thing or an expired access key thing [22:54:35] Ah, so probably not daemon-related, but the daemon issue probably could have a similar root [23:25:40] Trying on my phone and I get this https://imgur.com/a/mLHP6iu [23:26:32] Thanks, this will unfortunately need to wait until @agentisai is available, as they are the only one with sufficient permissions to resolve this at the moment.