jrollans.com is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.

This server runs the snac software and there is no automatic sign-up process.

Site description
These are the voyag... uh, things I post about.
Admin email
jrollans@gmail.com
Admin account
@jrollans@jrollans.com

Search results for tag #mastoadmin

AodeRelay boosted

[?]Ryan Wild » 🌐
@wild1145@mastodonapp.uk

For those 's that use the Universeodon relay, we've been seeing some issues it seems overnight. I've made some changes to our infrastructure to try to cope with what looks like a huge amount of traffic now. You may need to disable and re-enable the relay if it isn't working on your server.

    [?]Ian Littman » 🌐
    @ian@phpc.social

    phpc.social is now running on Mastodon 4.6.5, released about 5 hours ago.

      [?]Mastodon Engineering » 🌐
      @MastodonEngineering@mastodon.social

      We just released Mastodon 4.6.5. It contains one important bug fix and we recommend every instance running 4.6 to update.

      We are also releasing Mastodon v4.5.15 and v4.4.22 with minor bugfixes

      Full release notes and update instructions are available on the GitHub releases page.

      github.com/mastodon/mastodon/r

        [?]Bird » 🌐
        @bird@birdbox.party

        So I restarted my Mastodon server and it appears my Sidekiq queue has a problem

        Screenshot of the Sidekiq queue page showing the ingress queue with a backlog of 6,159,274 and the pull queue with a backlog of 43,085

        Alt...Screenshot of the Sidekiq queue page showing the ingress queue with a backlog of 6,159,274 and the pull queue with a backlog of 43,085

          [?]Mastodon Release Watcher » 🤖 🌐
          @mstdn_release_watcher@mastodon.kodesumber.com

          v4.6.5

          Upgrade overview This release contains upgrade notes that deviate from the norm: ℹ️ Requires assets recompilation For more information, view the complete release notes and scroll down to the upgrade instructions section. Changelog Fixed Fix...

          github.com/mastodon/mastodon/r

            [?]Chad :mstdn: [he/him/his] » 🌐
            @chad@mstdn.ca

            Wishing all at a happy convention!

            If I wasn’t preparing to sing LOTR Two Towers I’d absolutely have been there.

              [?]Larvitz :fedora: » 🌐
              @Larvitz@burningboard.net

              Nice!

              Our Mastodon instance burningboard.net has almost 60% of total using the current generation of the Internet Protocol (IPv6) and only arround 40% still using the legacy-protocol from the 1980s (IPv4).

              Measured on the PF firewall of our Mastodon webserver over the last 48 hours.

              Terminal screenshot running a shell command pipeline (pfctl -si | awk) that calculates IPv4 vs IPv6 network traffic on a server. The terminal output displays IPv4 traffic at 160.68 GiB (41.1%) and IPv6 traffic at 230.46 GiB (58.9%).

              Alt...Terminal screenshot running a shell command pipeline (pfctl -si | awk) that calculates IPv4 vs IPv6 network traffic on a server. The terminal output displays IPv4 traffic at 160.68 GiB (41.1%) and IPv6 traffic at 230.46 GiB (58.9%).

                [?]Dima » 🌐
                @dima@dol.social

                Sometimes newer is not better. At least not for the things that matter to you.

                I benchmarked two OVH VPS in the same Zurich location. My current 2025 model with a 500 Mbit network against the newer 2027 model with 1 Gbit. Same AMD EPYC Genoa cores, same provider, nearly identical sysbench CPU scores.

                Then the surprises started.
                The older box pushes 6,612 MiB/s in memory tests, the newer one 932 MiB/s. That is 7x.
                Random 4K reads: 1.32 million IOPS against 832k.
                And the old model is even about 1 EUR cheaper.

                For a Mastodon instance, databases, and Docker workloads, memory and disk beat extra bandwidth every time. So the shiny new VPS gets demoted to reverse proxy and backup duty, and this instance stays exactly where it is.

                Benchmark before you migrate.

                Screenshot of the OVH control panel showing two active VPS in the EU-WEST-LZ-ZRH location: vps-817e781a.vps.ovh.net labeled vps-2027-model2.LZ and zrh-1.dol.ch labeled vps-2025-model1.LZ. Both marked Active, the model names underlined in red

                Alt...Screenshot of the OVH control panel showing two active VPS in the EU-WEST-LZ-ZRH location: vps-817e781a.vps.ovh.net labeled vps-2027-model2.LZ and zrh-1.dol.ch labeled vps-2025-model1.LZ. Both marked Active, the model names underlined in red

                  [?]Dima » 🌐
                  @dima@dol.social

                  The numbers behind the previous post, for the curious.

                  Same fio and sysbench setup on both boxes, Debian 13, direct=1, libaio.

                  Random read 4K, the workload databases actually live on:
                  1.41M IOPS on the 2025 box against 822k on the 2027 one.

                  RAM bandwidth: 64,038 MiB/s against 11,906. That is 5.4x.

                  Single thread CPU: 4,504 against 4,147 events/sec. Same EPYC Genoa on paper.

                  And here is my favorite part. The old box ran all of this while carrying my entire production: Mastodon, Postgres, Valkey, a pile of Docker containers, 17 days of uptime.

                  The new box was empty and idle.

                  The loaded veteran still won almost everything.

                    [?]Rolle Laukkarinen » 🌐
                    @rolle@mementomori.social

                    Sometimes Mastodon loses link preview card images and never refetches them, especially for older links. I haven't had time to figure out the root cause, so I created a quick cron script to fetch the missing images. Here it is, in case it's useful to anyone: github.com/mementomori-social/

                      [?]propapanda :verified: [He/Him] » 🌐
                      @panda@pandas.social

                      AodeRelay boosted

                      [?]weed stallman » 🌐
                      @incentive@mastodon.circlewithadot.net

                      I get conflicted about infosec.exchange- there's a lot of good tooters on there that I find pretty invaluable and would not have discovered if not seeing them relayed into my feed.

                      However there's a plethora of CVE bots and it's truly a nightmare. Muting them all is getting annoying.

                      I'd set the restriction for infosec to "limit" but then I'm going to miss stuff I do actually want to see.

                      wat do

                        [?]paratos » 🌐
                        @paratos@social.ixcat.ovh

                        Il y a quelques jours je me suis fait bloquer/suspendu par deux instances pour avoir dénoncer une personne que je suspecte très fortement de faire des fausses captures d'écrans.(certes, de manière très maladroite, avec un exemple fait par moi-même)
                        Je pensait quelle faisait ça que pour nuire a un mouvement politique.
                        Mais j'avais tord, en fait ça vas plus loin que ça.
                        Là plus besoin de fausse capture, mais uniquement d'amalgame foireux pour faire passer toute critique de la politique d'Israël pour de l'antisémitisme.
                        (exemple : piaille.fr/@scudery/117004528553340201)
                        Ou comment sans le dire, défendre la politique israélienne et son génocide.

                        Du coup est-ce que les admins de ces instances sont ok avec ça, vous bloquez ce vous voulez hein, mais que au moins que les utilisateurs de ces instances sachent a qui ils font confiance.

                          [?]craftxbox » 🌐
                          @craftxbox@transfur.social

                          Can anyone run some numbers for sanity? is 45,345 media uploads per day across the network correct? no single instance sticks out to me but WOW that is. A concerningly large amount of image files???

                            [?]Paul Chambers🚧 » 🌐
                            @paul@oldfriends.live

                            My catch-all email address is getting spam emails for accounts on my self-hosted Mastodon instance. The spam scrappers must be confusing federation email-like user@instance account handles as email. Anyone with a catch-all box seeing this? Interested if another instance with two or three dozen or more users on their instance is...

                              [?]Hardy Erlinger » 🌐
                              @hardy@social.netspectrum.de

                              @michael Quick follow-up: I made OIDC login work on my instance based on your writeup. Thanks again!

                              I am not familiar with Pocket ID, but is it possible that the OIDC_CLIENT_ID and OIDC_CLIENT_SECRET env variables are missing from your .env.production file?

                                fedicat boosted

                                [?]Mastodon Engineering » 🌐
                                @MastodonEngineering@mastodon.social

                                We just released Mastodon 4.6.4, 4.5.14 and 4.4.21.

                                Those updates include multiple security fixes, including fixes for two major issues.

                                We encourage server administrators to update as soon as possible, as one of the issues can expose PII of local users. We are investigating potential uses of this exploit and will soon share more information.

                                Full release notes and update instructions are available on the GitHub release page.

                                github.com/mastodon/mastodon/r

                                  fedicat boosted

                                  [?]Mastodon Engineering » 🌐
                                  @MastodonEngineering@mastodon.social

                                  We are planning to release new Mastodon security updates for versions 4.4, 4.5, 4.6 and nightly this Monday, Jul 27, at around 14:00 UTC.

                                  It solves two major security issues.

                                  We encourage server administrators to plan for an update in the hours following the release to ensure their instance is protected. These versions will not require database migrations.