Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Mastodon
  3. Unable to cleanup Orphaned Media

Unable to cleanup Orphaned Media

Scheduled Pinned Locked Moved Solved Mastodon
3 Posts 2 Posters 502 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A Offline
    A Offline
    alwynispat
    wrote on last edited by
    #1

    So running the cleanup.sh works for most parts.
    Only the Orphaned Media portion fails. Running the command manually doesn't help too.

    I've got my media hosted in BackBlaze B2, no issues loading images, etc.
    Obviously the api key has read/write permissions. Something else I've missed?

    Screenshot 2023-01-08 at 22.16.40.png Screenshot 2023-01-08 at 22.22.17.png

    Find me at Mastodon

    1 Reply Last reply
    0
    • nebulonN Offline
      nebulonN Offline
      nebulon
      Staff
      wrote on last edited by
      #2

      This may actually be better reported upstream at https://github.com/mastodon/mastodon/issues after a search if this was already reported.

      A 1 Reply Last reply
      1
      • nebulonN nebulon marked this topic as a question on
      • A alwynispat has marked this topic as solved on
      • nebulonN nebulon

        This may actually be better reported upstream at https://github.com/mastodon/mastodon/issues after a search if this was already reported.

        A Offline
        A Offline
        alwynispat
        wrote on last edited by
        #3

        @nebulon i've identified the issue and it was my S3 configuration.

        The endpoint and hostname should never have the bucket name.

        S3_ENDPOINT=https://s3.us-west-001.example.com
        S3_HOSTNAME=s3.us-west-001.example.com

        Find me at Mastodon

        1 Reply Last reply
        2
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Bookmarks
        • Search