Meta tags:
Headings (most frequently used words):
error, an, to, wrong, how, why, the, but, page, do, what, logs, information, after, upgrade, newer, version, some, fail, about, or, am, rails, is, mastodon, troubleshooting, errors, ipv4, ipv6, conflicts, see, that, says, something, went, find, out, not, seeing, much, in, my, enable, additional, logging, debugging, pages, look, weird, like, they, have, unstyled, elements, requests, and, show, messages, missing, columns, tables, trying, run, tootctl, rake, command, all, get, uninitialized, constants, encountered, compilation, while, executing, rails_env, production, bundle, exec, assets, precompile, no, more, given, fix, it, getting, this, read, only, file, system, dir_s_mkdir, webui, just, displays, api, works, postgres, database, migrations, during, update, sponsored, by,
Text of the page (most frequently used words):
the (52), mastodon (32), and (21), you (18), error (18), your (18), rails (14), #production (13), admin (13), #rails_env (11), web (11), that (11), assets (10), run (10), with (10), service (9), how (9), logs (9), bundle (8), exec (8), using (8), precompile (8), not (8), have (8), but (8), this (7), page (7), for (7), after (7), can (7), like (6), environment (6), api (6), system (6), why (6), server (6), more (6), what (6), wrong (6), upgrade (6), migrations (5), messages (5), then (5), some (5), correct (5), command (5), sidekiq (5), systemd (5), information (5), are (5), newer (5), log (5), logging (5), errors (5), see (4), running (4), default (4), make (4), example (4), database (4), fail (4), systemctl (4), restart (4), rake (4), cache (4), clear (4), directory (4), getting (4), out (4), show (4), about (4), version (4), level (4), troubleshooting (4), instance (4), profile (4), account (4), oauth (4), also (3), pg_bouncer (3), migrate (3), postgresql (3), bin (3), will (3), fix (3), when (3), file (3), because (3), while (3), increase (3), sure (3), compilation (3), check (3), code (3), installing (3), from (3), all (3), get (3), looks (3), machine (3), public (3), they (3), configuring (3), set (3), debugging (3), find (3), stack (3), ipv6 (3), search (3), preferences (3), apps (3), reports (3), accounts (3), setting (3), new (3), source (2), deployment (2), scaling (2), db_port (2), probably (2), port (2), add (2), release (2), lock (2), activerecord (2), concurrentmigrationerror (2), own (2), postgres (2), during (2), update (2), tmp (2), yarn (2), install (2), immutable (2), live (2), been (2), yet (2), files (2), installed (2), again (2), webui (2), just (2), displays (2), works (2), readwritepaths (2), etc (2), use (2), read (2), only (2), dir_s_mkdir (2), memory (2), encountered (2), executing (2), given (2), development (2), gems (2), trying (2), uninitialized (2), constants (2), tootctl (2), pgbouncer (2), requests (2), missing (2), columns (2), tables (2), pages (2), look (2), weird (2), unstyled (2), elements (2), levels (2), silly (2), debug (2), other (2), value (2), attempting (2), troubleshoot (2), streaming (2), env (2), application (2), seeing (2), much (2), enable (2), additional (2), each (2), substitute (2), name (2), docker (2), says (2), something (2), went (2), dns (2), ipv4 (2), conflicts (2), notificationpolicy (2), filter (2), report (2), quote (2), domainblock (2), notifications (2), trends (2), collections (2), domain_blocks (2), tokens (2), security (2), implementing (2), posts (2), features (2), imprint, view, blog, join, sponsored, last, updated, november, 2025, available, 简体中文, improve, needs, done, both, pre, post, section, 5432, front, forgot, specify, manually, instead, commands, work, failed, advisory, aborted, warning, don, type, exclusivelock, encounter, sudo, without, valid, functional, nodejs, cases, has, help, here, happens, start, daemon, reload, stop, parameter, makes, way, disallows, writing, outside, elsewhere, may, need, allow, write, custom, home, sandboxing, capabilities, usually, ran, compiling, swapfile, swap, space, capacity, execute, compile, everything, leave, unchanged, specifying, before, assumed, tries, load, related, however, environments, avoid, those, where, comes, accessing, older, schema, one, connects, directly, does, support, kind, table, locks, used, within, restarted, process, serving, outdated, stylesheets, scripts, precompilation, fails, possible, different, copy, over, packs, very, verbose, should, take, care, change, back, lower, once, completed, these, option, found, log_level, rails_log_level, modify, relevant, info, please, note, factor, usual, watch, console, root, stdout, response, carries, header, unique, request, which, reflected, inspecting, headers, easily, corresponding, trace, specific, details, side, displayed, reveal, setup, internally, give, attackers, clues, abuse, efficiently, never, traces, written, browsed, similar, container, mastodon_web_1, journalctl, having, firewalling, applied, cause, problems, including, performance, timing, failing, jobs, fediverse, fully, working, dual, aaaa, record, zone, webpushsubscription, translation, token, termsofservice, tag, suggestion, statussource, statusedit, status, shallowtag, shallowquote, scheduledstatus, rule, role, relationshipseveranceevent, relationship, reaction, quoteapproval, privacypolicy, previewcardauthor, previewcard, poll, notificationrequest, notificationfallback, notification, mediaattachment, marker, list, identityproof, filterstatus, filterresult, filterkeyword, featuredtag, featureapproval, familiarfollowers, extendeddescription, customemoji, conversation, context, collectionwithaccounts, collectionitem, collection, asyncrefresh, appeal, annualreport, announcement, measure, ipblock, emaildomainblock, domainallow, dimension, cohort, canonicalemailblock, accountwarning, entities, markers, lists, conversations, timelines, scheduled_statuses, polls, media, statuses, proofs, oembed, push, custom_emojis, announcements, health, grouped, async_refreshes, emails, annual, retention, measures, ip_blocks, email_domain_blocks, domain_allows, dimensions, canonical_email_blocks, tags, suggestions, mutes, followed_tags, follow_requests, filters, featured_tags, favourites, endorsements, bookmarks, blocks, methods, rate, limits, scopes, guidelines, best, practices, datetime, formats, rest, bearcaps, microformats, webfinger, activitypub, spec, compliance, design, reference, creating, themes, css, styling, state, management, components, frontend, guide, issues, responsible, disclosure, routes, structure, dev, technical, overview, contributing, libraries, implementations, obtaining, client, app, access, playing, data, started, developing, roles, webhooks, index, corruption, moderation, actions, migrating, backing, upgrading, cli, single, sign, captcha, onion, services, object, storage, optional, full, text, preparing, official, ios, android, moving, leaving, externally, settings, promoting, yourself, others, dealing, unwanted, content, quoting, network, posting, signing, documentation,
Text of the page (random words):
troubleshooting errors mastodon documentation what is mastodon using mastodon signing up for an account setting up your profile posting to your profile using the network features quoting other posts dealing with unwanted content promoting yourself and others set your preferences more settings using mastodon externally moving or leaving accounts official ios and android apps running your own server running mastodon preparing your machine installing from source configuring your environment configuring full text search installing optional features object storage onion services captcha single sign on setting up your new instance using the admin cli upgrading to a new release backing up your server migrating to a new machine scaling up your server moderation actions troubleshooting errors database index corruption webhooks roles developing mastodon apps getting started with the api playing with public data obtaining client app access logging in with an account libraries and implementations implementing quote posts implementing collections contributing to mastodon technical overview setting up a dev environment code structure routes security issues and responsible disclosure frontend guide components state management css and styling creating themes design tokens reference spec compliance activitypub webfinger security microformats oauth bearcaps rest api datetime formats guidelines and best practices oauth tokens oauth scopes rate limits api methods accounts blocks bookmarks domain_blocks endorsements favourites featured_tags filters follow_requests followed_tags mutes preferences reports suggestions tags admin accounts canonical_email_blocks dimensions domain_allows domain_blocks email_domain_blocks ip_blocks measures reports retention trends annual reports apps emails oauth async_refreshes collections grouped notifications health instance announcements custom_emojis directory trends notifications push oembed profile proofs search statuses media polls scheduled_statuses timelines conversations lists markers streaming api entities account accountwarning admin account admin canonicalemailblock admin cohort admin dimension admin domainallow admin domainblock admin emaildomainblock admin ip admin ipblock admin measure admin report announcement annualreport appeal application asyncrefresh collection collectionitem collectionwithaccounts context conversation customemoji domainblock error extendeddescription familiarfollowers featureapproval featuredtag filter filterkeyword filterresult filterstatus identityproof instance list marker mediaattachment notification notificationfallback notificationpolicy notificationrequest poll preferences previewcard previewcardauthor privacypolicy profile quote quoteapproval reaction relationship relationshipseveranceevent report role rule scheduledstatus search shallowquote shallowtag status statusedit statussource suggestion tag termsofservice token translation v1 filter v1 instance v1 notificationpolicy webpushsubscription troubleshooting errors ipv4 ipv6 conflicts i see an error page that says something went wrong how do i find out what s wrong i m not seeing much in my logs how do i enable additional logging debugging information after an upgrade to a newer version some pages look weird like they have unstyled elements why after an upgrade to a newer version some requests fail and the logs show error messages about missing columns or tables why i am trying to run a tootctl or rake rails command but all i get is an error about uninitialized constants what s wrong i encountered a compilation error while executing rails_env production bundle exec rails assets precompile but no more information is given how to fix it i am getting this error read only file system dir_s_mkdir why the mastodon webui just displays an error page but the api works postgres database migrations fail during a mastodon update ipv4 ipv6 conflicts having ipv6 on your dns but not getting the correct ip or firewalling applied can cause problems including performance timing out errors or failing jobs for the fediverse make sure you have fully working dual stack if you have a aaaa record in your dns zone i see an error page that says something went wrong how do i find out what s wrong all error messages with stack traces are written to the system log when using systemd the logs of each systemd service can be browsed with journalctl u mastodon web substitute with the correct service name when using docker it s similar docker logs mastodon_web_1 substitute with the correct container name specific details of server side errors are never displayed to the public as they can reveal what your setup looks like internally and give attackers clues on how to get in or how to abuse the system more efficiently each response from mastodon s web server carries a header with a unique request id which is also reflected in the logs by inspecting the headers of the error page you can easily find the corresponding stack trace in the log i m not seeing much in my logs how do i enable additional logging debugging information please note that mastodon as a 12 factor application logs to stdout and not rails root log rails env log as it s usual in rails watch your console by default your logs will show info level logging to see more debugging messages you can modify your env production file to increase the level for the relevant service web sidekiq set the value of rails_log_level to debug and then restart the service that you re attempting to troubleshoot streaming set the value of log_level to silly and then restart the service that you re attempting to troubleshoot more information on other logging levels for these option can be found on the configuring your environment page the debug or silly levels can be very verbose and you should take care to change the log level back to a lower level once you have completed your troubleshooting after an upgrade to a newer version some pages look weird like they have unstyled elements why check that you have run rails_env production bin rails assets precompile after the upgrade and restarted mastodon s web process because it looks like it s serving outdated stylesheets and scripts if precompilation fails it s possible to precompile the assets on a different machine then copy over the public packs directory after an upgrade to a newer version some requests fail and the logs show error messages about missing columns or tables why check that you have run rails_env production bin rails db migrate after the upgrade because it looks like mastodon s code is accessing a newer or older database schema if you are using pgbouncer make sure this one command connects directly to postgresql as pgbouncer does not support the kind of table locks that are used within migrations i am trying to run a tootctl or rake rails command but all i get is an error about uninitialized constants what s wrong check that you are specifying the correct environment with rails_env production before the command by default the environment is assumed to be development so the code tries to load development related gems however in production environments we avoid installing those gems and that s where the error comes from i encountered a compilation error while executing rails_env production bundle exec rails assets precompile but no more information is given how to fix it usually it s because your server ran out of memory while compiling assets use a swapfile or increase the swap space to increase the memory capacity run rails_env production bundle exec rake tmp cache clear to clear cache then execute rails_env production bundle exec rails assets precompile to compile again make sure you clear the cache after a compilation error or it will show everything s ok but leave the assets unchanged i am getting this error read only file system dir_s_mkdir why by default mastodon makes use of systemd s sandboxing capabilities in a way that disallows writing outside of home mastodon if mastodon is installed elsewhere you may need to allow mastodon sidekiq and mastodon web to write to a custom directory add parameter readwritepaths to files etc systemd system mastodon sidekiq service and etc systemd system mastodon web service example readwritepaths example mastodon live run systemctl stop mastodon sidekiq mastodon web run systemctl daemon reload run systemctl start mastodon sidekiq mastodon web the mastodon webui just displays an error page but the api works this happens for example when you run rails_env production bundle exec rails assets precompile without a valid functional nodejs environment in some cases yarn install immutable has not been run yet and the web files have not been installed to the correct directory yet running the assets precompile command again will probably not help here s how to fix it cd live yarn install immutable rails_env production bundle exec rake tmp cache clear rails_env production bundle exec rails assets precompile then restart the mastodon web service sudo systemctl restart mastodon web service postgres database migrations fail during a mastodon update if you encounter error messages like this warning you don t own a lock of type exclusivelock bin rails aborted activerecord concurrentmigrationerror activerecord concurrentmigrationerror failed to release advisory lock you re probably running pg_bouncer in front of postgresql and forgot to specify the postgresql port manually instead of using the default pg_bouncer port to make the migrate commands work add db_port for example rails_env production db_port 5432 bundle exec rails db migrate this needs to be done for both pre deployment migrations and post deployment migrations also see scaling mastodon pg_bouncer section last updated november 21 2025 improve this page also available in 简体中文 sponsored by join mastodon blog view source cc by sa 4 0 imprint
|
