Scott 🏴😷Can I get a quick check that things are working? Anyone who sees this interact with it?
Paul Chambers🚧@scott test Also, in
my mastodon self-hosted federation admin panel, it shows no issues with federating with tams.tech.
cc @scott
@scott
On my self-hosted account, interactions don't seem to be federating. I can make statuses, and they show up locally, but if I browse to @[email protected] from here I don't see anything posted since upgrading from 4.3.1 to 4.3.3. If this account likes a post on that one, for example, it shows up in my notifications on that account, but the other way around doesn't work. Can anyone help? Is this a bug I should report? #mastodon #mastoadmin #admin
scott@paul @scott there's more #mastodon #mastoadmin #admin
RE: https://shonk.social/notes/a38tbvmd5atn0004
RE: https://shonk.social/notes/a38tbvmd5atn0004
@scott
I have updated and rebooted and confirmed that no outbound network connections can be made from inside the sidekiq container #mastodon #mastoadmin #admin RE: ok, I narrowed it down: ``` docker run --network srv_mastodon_internal --rm ghcr.io/mastodon/mastodon:v4.3.3 curl https://mastodon.social/health ``` fails, quickly, `curl: (6) Could not resolve host: mastodon.social`. But ``` docker run --rm ghcr.io/mastodon/mastodon:v4.3.3 curl https://mastodon.social/health ``` works fine, so it's something specific to running sidekiq in a #docker internal network... #mastodon #mastoadmin #admin RE: ...
@scott ok. I'm not big in Docker. Maybe someone can help you here: https://matrix.to/#/#mastodon_admin:matrix.org @scott
@paul @scott I got it working, thanks to you and @bmitch for helping me figure it out
edit: solution: https://fosstodon.org/@bmitch/113861628366524555
Brandon Mitchell (@[email protected])
@[email protected] Is this by design? The "internal" part of that name implies that it was created with the internal option in #docker which intentionally prevents any internet access. https://docs.docker.com/reference/cli/docker/network/create/#internal