pleroma-support issueshttps://git.pleroma.social/pleroma/pleroma-support/-/issues2024-03-13T22:57:21Zhttps://git.pleroma.social/pleroma/pleroma-support/-/issues/105search broken with CaseClauseError2024-03-13T22:57:21Zlamplamp@owo69.mesearch broken with CaseClauseErrorthe search on my new pleroma does not work, it prints this error `[error] Elixir.Pleroma.Web.MastodonAPI.SearchController search error: %CaseClauseError{term: {"false", %Pleroma.User{`... followed by a dump of all the user data.
I had m...the search on my new pleroma does not work, it prints this error `[error] Elixir.Pleroma.Web.MastodonAPI.SearchController search error: %CaseClauseError{term: {"false", %Pleroma.User{`... followed by a dump of all the user data.
I had manually changed the name of a user in the database and I had cleared the activites and objects tables to clear up test garbage before I started federation. Could that have had something to do with it?https://git.pleroma.social/pleroma/pleroma-support/-/issues/104On Firefish/Iceshrimp/catodon, it is not possible to follow some Pleroma users.2024-03-01T05:59:18Z老周部落On Firefish/Iceshrimp/catodon, it is not possible to follow some Pleroma users.On Firefish/Iceshrimp/catodon (both forks of Misskey v12), it is not possible to follow some Pleroma users, such as FiveYellowMice@social.fym.moe.
When encountering such an account, the follow request cannot be initiated from Firefish/I...On Firefish/Iceshrimp/catodon (both forks of Misskey v12), it is not possible to follow some Pleroma users, such as FiveYellowMice@social.fym.moe.
When encountering such an account, the follow request cannot be initiated from Firefish/Iceshrimp/catodon, and Firefish/Iceshrimp/catodon is stuck in the processing state without responding.
I'm trying to debug a federation issue with Firefish, debugging failed because we could not find a way to let Pleroma trust the internal self-signed CA. After putting the self-signed certificate into the system truststore, either `echo ":public_key.cacerts_load()" >> mix.exs` or refer to https://git.pleroma.social/pleroma/pleroma/-/issues/2512 let certificate verification is turned off, Pleroma always prompts `"request_id=F7hY6BrigUMOAlsAAAjC [error] Could not decode user at fetch https://01firefish.fedi.local/users/xxx, {:tls_alert, {: unknown_ca, ~c"TLS client: In state wait_cert_cr at ssl_handshake.erl:2134 generated CLIENT ALERT: Fatal - Unknown CA\n"}}".`
By the way, social.fym.moe instance Backend verison is 2.5.2. Is there anything else I can do, thank you.https://git.pleroma.social/pleroma/pleroma-support/-/issues/103Install with Postgres on IPv6-only container fails with :nxdomain error2023-12-15T09:10:46ZMathias PickerInstall with Postgres on IPv6-only container fails with :nxdomain errorHi all,
I'm in the process of installing pleroma for the first time.
The database server is only reachable via v6, and running
`MIX_ENV=prod mix ecto.migrate`
throws
`19:16:15.153 [error] Postgrex.Protocol (#PID<0.690.0>) failed to ...Hi all,
I'm in the process of installing pleroma for the first time.
The database server is only reachable via v6, and running
`MIX_ENV=prod mix ecto.migrate`
throws
`19:16:15.153 [error] Postgrex.Protocol (#PID<0.690.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (pgsql15.XXX.XXX:5432): non-existing domain - :nxdomain`
Reading up on erlang and IPv6 DNS I created a file erl_inetrc with the following content:
`%% allow IPv6 lookup`
`{inet6, true}.`
and set the environment variable for erlang to use it:
`export ERL_INETRC=$(pwd)/config/erl_inetrc`
Now erl and iex work fine:
`Interactive Elixir (1.14.5) - press Ctrl+C to exit (type h() ENTER for help)`
`iex(1)> :inet.gethostbyname('pgsql15.xxx.xxx')`
`{:ok, {:hostent, 'pgsql15.XXX.XXX', [], :inet6, 16, [{...}]}}`
Sadly, `MIX_ENV=prod mix ecto.migrate` still throws an `:nxdomain` error.
Where can I configure mix and/or pleroma do do IPv6 lookups and/or to read the erl_inetrc config?
Or, better still, can you patch pleroma to lookup IPv6 addresses?
Thanks, Mathiashttps://git.pleroma.social/pleroma/pleroma-support/-/issues/81Accidental root pull when updating2023-05-30T17:33:03Za aAccidental root pull when updatingSo after probably re-reading the update instructions a couple of times, I still seem to have managed to fail on the first step and pull changes as (presumably) root on my previous update.
First I chowned the .git directory back to `pler...So after probably re-reading the update instructions a couple of times, I still seem to have managed to fail on the first step and pull changes as (presumably) root on my previous update.
First I chowned the .git directory back to `pleroma:pleroma` as instructed in the #pleroma channel and I was allowed to pull, but the pull failed to unlink and create a bunch of files, breaking the web front end.
I then asked if it's okay to just chown the entire `pleroma` directory, and was given green light (later realizing this was actually a step in the install guide).
The problem is now that even after performing `git reset --hard` to get rid of unnecessary changes (as instructed by #pleroma), I suspect the ownership issues are still keeping a ton of files red in my `git status`. I assume I need to simply force the pull somehow? It won't pull normally as it says I would be "overwriting files".
Thank you in advance.https://git.pleroma.social/pleroma/pleroma-support/-/issues/23Set default poll time in PleromaFE2023-05-10T21:19:06ZMew MewSet default poll time in PleromaFEHow can I change the default poll time in PleromaFE to be something other than 10 minutes?How can I change the default poll time in PleromaFE to be something other than 10 minutes?https://git.pleroma.social/pleroma/pleroma-support/-/issues/57May I use another domain in user account other than the entry website?2023-05-10T21:12:58Zfivestone .May I use another domain in user account other than the entry website?For example, I wish to format my account id as @xxx@domain.com, but set the pleroma web site to subdomain.domain.com, while remaining the domain.com to my homepage.
Thanks.For example, I wish to format my account id as @xxx@domain.com, but set the pleroma web site to subdomain.domain.com, while remaining the domain.com to my homepage.
Thanks.https://git.pleroma.social/pleroma/pleroma-support/-/issues/61some posts are missing on pleroma blog today2023-05-10T21:11:58ZSnowsome posts are missing on pleroma blog today![30007cb068](/uploads/c5523aea06b29cea52610ec4363be9a6/30007cb068.png)
This is the newest post I saw in there today...![30007cb068](/uploads/c5523aea06b29cea52610ec4363be9a6/30007cb068.png)
This is the newest post I saw in there today...https://git.pleroma.social/pleroma/pleroma-support/-/issues/77Error: Access token does not include the required scope2023-05-10T02:22:49ZSevicheError: Access token does not include the required scopeHi! I tried multiple ways to install pleroma on ubuntu 20.04, but all ended with `{"error": "Error. Access token does not include the required scope"}`, and the error always occurs after command `sleep 20 && curl http://localhost:4000/a...Hi! I tried multiple ways to install pleroma on ubuntu 20.04, but all ended with `{"error": "Error. Access token does not include the required scope"}`, and the error always occurs after command `sleep 20 && curl http://localhost:4000/api/v1/instance`
What should I do next? I feel very confused now 😰https://git.pleroma.social/pleroma/pleroma-support/-/issues/66Read-Only User2023-05-10T02:21:57ZAzureRead-Only UserIf I want to allow a user to log in and read past direct messages but not post anything, what is the most expedient way to do that?
'Disallow posts from federating' seems promising as a partial solution, but searching suggests it's not ...If I want to allow a user to log in and read past direct messages but not post anything, what is the most expedient way to do that?
'Disallow posts from federating' seems promising as a partial solution, but searching suggests it's not actually implemented?https://git.pleroma.social/pleroma/pleroma-support/-/issues/88v2.4.5 Docker Build Fails2023-05-10T02:20:52ZAlex Markleyv2.4.5 Docker Build FailsWhen running a `docker build .` on the release source tree, I get the following error message:
`ERROR: http://nl.alpinelinux.org/alpine/latest-stable/community: UNTRUSTED signature`
This is caused by an error in the RUN command on line...When running a `docker build .` on the release source tree, I get the following error message:
`ERROR: http://nl.alpinelinux.org/alpine/latest-stable/community: UNTRUSTED signature`
This is caused by an error in the RUN command on line 34 of the Dockerfile. Specifically this is caused by a mismatch between `latest-stable` on line 34 and `FROM alpine:3.11` on line 15.
If I update line 15 to point at `alpine:3.17` and line 34 to point at `https://nl.alpinelinux.org/alpine/v3.17/community/`, the build succeeds.https://git.pleroma.social/pleroma/pleroma-support/-/issues/100Error 500 when reciving post from wafrn instances2023-04-29T19:53:49ZGabriel amadorError 500 when reciving post from wafrn instancesHello, wafrn creator here!
When I send new posts or answer to a plerona post, I recive an error 500 from pleroma.
I found out a few days ago that I was not able to comunicate with a plerona instance. Made a plerona test instance and fr...Hello, wafrn creator here!
When I send new posts or answer to a plerona post, I recive an error 500 from pleroma.
I found out a few days ago that I was not able to comunicate with a plerona instance. Made a plerona test instance and from a wafrn dev instance was able to get this on the logs
[I have the thing in this pastebin](https://pastebin.com/Sg5hWwJK)
It's the logs of my dev instance and also the object that I am sending.
Any idea of how could I debug this? I do not know anything about elixir nor plerona source code.
If you want to try reproduce the issue by yourself, wafrn still has no good documentation on creating your own instance, [feel free to register on mine](https://app.wafrn.net) as a quick and dirty hack and try sending a post to your unfavourite pleroma account.https://git.pleroma.social/pleroma/pleroma-support/-/issues/99[solved] particular remote account not available on whole instance2023-04-25T13:06:10ZDynamic Operations Architect[solved] particular remote account not available on whole instanceI am running Pleroma 2.5.1 (OTP 23.3.4.18) and my instance does not "see" a particular remote account on social.cologne. The account in question is @koeln@social.cologne. Search, interaction, nothing works. It feels like this particular ...I am running Pleroma 2.5.1 (OTP 23.3.4.18) and my instance does not "see" a particular remote account on social.cologne. The account in question is @koeln@social.cologne. Search, interaction, nothing works. It feels like this particular remote account does not exist. Other accounts on social.cologne are discoverable and interaction is not a problem. I am already in contact with the admin of social.cologne. He has found no problem on his end.
Where and how do I best get started with troubleshooting?https://git.pleroma.social/pleroma/pleroma-support/-/issues/95Reloading user pages (local and remote) not working2023-01-02T20:33:02ZEirik ØverbyReloading user pages (local and remote) not workingBeen running Pleroma for a couple of years, more active use recently so not sure how long this has been a problem:
When viewing user info in the default FE and then hitting reload in the browser (or leaving and then going back to the pa...Been running Pleroma for a couple of years, more active use recently so not sure how long this has been a problem:
When viewing user info in the default FE and then hitting reload in the browser (or leaving and then going back to the page), the logged-in session is lost and a "remote follow" screen is shown.
For remote users, reloading gives "oops user not found".
Screenshots attached.
![pleroma-userinfo-local-initial](/uploads/9db368f7cc697f694d988d263cd2d3d7/pleroma-userinfo-local-initial.png)
![pleroma-userinfo-local-reload](/uploads/2e360188e601d6425608e96dd685dc71/pleroma-userinfo-local-reload.png)
![pleroma-userinfo-remote-initial](/uploads/96236b2316f67c9070c74c3e8144410c/pleroma-userinfo-remote-initial.png)
![pleroma-userinfo-remote-reload](/uploads/7afcb74cd77cd070f7b05d535f698660/pleroma-userinfo-remote-reload.png)https://git.pleroma.social/pleroma/pleroma-support/-/issues/91Home Timeline taking longer than 15 seconds to load2022-12-29T17:14:54ZTim SoderstromHome Timeline taking longer than 15 seconds to loadI ran into an issue today where my home timeline was bumping up into the configured statement timeout in Pleroma. After poking around some closed bugs I increased it via:
```
# Database
config :pleroma, Pleroma.Repo,
adapter: Ecto.Ada...I ran into an issue today where my home timeline was bumping up into the configured statement timeout in Pleroma. After poking around some closed bugs I increased it via:
```
# Database
config :pleroma, Pleroma.Repo,
adapter: Ecto.Adapters.Postgres,
...
pool_size: 30,
timeout: 60_000
# DB performance is sucky
config :pleroma, :dangerzone, override_repo_pool_size: true
```
This helped in that the timeline isn't causing a 500 but is still oddly slow for my Pleroma instance size. It has 3 users, 1 of which is my main account, 1 is a sort of announcement account, and my band mate who never uses it :P So it's basically just me. I'm running an 8GB Pi4 and have tuned the DB as follows:
```
max_connections = 100
shared_buffers = 512MB
effective_cache_size = 1536MB
maintenance_work_mem = 128MB
checkpoint_completion_target = 0.9
wal_buffers = 16MB
default_statistics_target = 100
random_page_cost = 1.1
effective_io_concurrency = 200
work_mem = 2621kB
min_wal_size = 1GB
max_wal_size = 4GB
max_worker_processes = 4
max_parallel_workers_per_gather = 2
max_parallel_workers = 4
max_parallel_maintenance_workers = 2
```
I'm also logging slow queries and the home timeline causes this one to get logged:
```
2022-12-07 22:37:28.833 UTC [2107] pleroma@victimcache_pleorma STATEMENT: SELECT a0."id", a0."data", a0."local", a0."actor", a0."recipients", a0."inserted_at", a0."updated_at", b2."id", b2."user_id", b2."activity_id", b2."inserted_at", b2."updated_at", o1."id", o1."data", o1."inserted_at", o1."updated_at", NOT (t3."id" IS NULL) FROM "activities" AS a0 INNER JOIN "objects" AS o1 ON (o1."data"->>'id') = COALESCE(a0."data"->'object'->>'id', a0."data"->>'object') LEFT OUTER JOIN "bookmarks" AS b2 ON (b2."user_id" = $1) AND (b2."activity_id" = a0."id") LEFT OUTER JOIN "thread_mutes" AS t3 ON (t3."user_id" = $2) AND (t3."context" = a0."data"->>'context') WHERE ((($3 && a0."recipients")) OR (a0."actor" = $4)) AND (a0."data"->>'type' = ANY($5)) AND (not (a0."actor" = ANY($6))) AND (((not (a0."recipients" && $7)) or a0."actor" = $8)) AND (recipients_contain_blocked_domains(a0."recipients", $9) = false) AND (not (a0."data"->>'type' = 'Announce' and a0."data"->'to' ?| $10)) AND ((not (split_part(a0."actor", '/', 3) = ANY($11))) or a0."actor" = ANY($12)) AND ((not (split_part(o1."data"->>'actor', '/', 3) = ANY($13))) or (o1."data"->>'actor') = ANY($14)) AND (not ( a0."data"->>'type' = 'Announce' and a0."actor" = ANY($15))) AND (a0."data"->>'type' != 'Announce' or o1."data"->>'actor' != $16) AND (NOT (a0."actor" = ANY($17))) AND (not(o1."data"->>'type' = 'Answer')) AND (not(o1."data"->>'type' = 'ChatMessage')) AND (NOT (a0."actor" = ANY($18))) ORDER BY a0."id" desc nulls last LIMIT $19
```
The interesting bit is that I don't see any I/O wait on my Pi which leads me to believe it's not because of disk I/O (I'm running a SATA SSD via USB3). It is burning CPU cycles though, seems to be partly single threaded as I'll see one CPU core hit 100% user when looking at top, at least when initially refreshing the timeline. Then it starts to even out.
It feels like this just popped up almost overnight and my other Pleroma instance doesn't have this issue (same Pi). I post on that one less and it's similar (just a few users, mostly me). That one I have _not_ upgraded to the latest release. I was having performance issues on the one I'm referring to here before I upgraded and it doesn't seem to have helped (it may even be worse). Opting to keep that instance at the previous version just to try and better compare the two.
I tried to run explains and things on the above query but I'm a MySQL and Clickhouse DBA and don't have a lot of PGSQL experience - or at least all the info I have is really dated. Since the above has a ton of variables/parameters I wasn't able to pursue it much further yet. I would assume I can get the literal query being sent to PGSQL but haven't found them in looking at the execution list (processlist in MySQL speak).
The slow load is in both the web and Whalebird (hitting the same API endpoint I'm sure, I believe it's /api/v1/timelines/home
)https://git.pleroma.social/pleroma/pleroma-support/-/issues/93Reply to a followers-only post showed up on timeline, is it by design?2022-12-19T18:49:27ZRenn AkazaReply to a followers-only post showed up on timeline, is it by design?Let's assume we have users A, B and me. B is following A, and I'm following B but not A.
A sent a followers-only post and B, as A's follower, saw replied to it in followers-only mode, too. B's reply appeared on my timeline while A's po...Let's assume we have users A, B and me. B is following A, and I'm following B but not A.
A sent a followers-only post and B, as A's follower, saw replied to it in followers-only mode, too. B's reply appeared on my timeline while A's posts are not. It doesn't seem to make much sense because I can only see half of the conversation which provides no context.
I thought a followers-only post should only be visible when I'm following all the mentioned persons in the post, and that should be what Mastodon is doing right now. Is the difference by design or a bug?
Or it's probably related to the "Safe DM" option in settings?https://git.pleroma.social/pleroma/pleroma-support/-/issues/92Cannot find/PM certain users2022-12-14T04:09:50ZRenn AkazaCannot find/PM certain usersThe user appears like inexistent to my instance. Searching the user`@username@domain.tld` returns nothing, and posing "@username@domain.tld test" will cause an error, the post will not be processed internally.
* The same user can be fou...The user appears like inexistent to my instance. Searching the user`@username@domain.tld` returns nothing, and posing "@username@domain.tld test" will cause an error, the post will not be processed internally.
* The same user can be found from another public Pleroma instance
* My issued instance can find some other users also from `domain.tld`
* `domain.tld` is running Mastodon v3.5.2
* I've tested on my instance with Pleroma v2.4.4 and v2.4.5-2
* Tested on a new instance built anew using OTP, v2.4.5-2, still couldn't find the user
I'm not familiar with the structure, if there's anyone who is willing to take a look and offer some advice, it would be greatly appreciated. Here are some logs to help:
When searching the user:
```
17:02:11.871 request_id=xxxxxxxxxxx[error] Preloading for /static/stickers.json failed.
** (UndefinedFunctionError) function Pleroma.Web.Preload.Providers.StatusNet.generate_terms/1 is undefined (module Pleroma.Web.Preload.Providers.StatusNet is not available)
Pleroma.Web.Preload.Providers.StatusNet.generate_terms(%{"path" => ["static", "stickers.json"]})
(pleroma 2.4.4) lib/pleroma/web/preload.ex:14: anonymous fn/3 in Pleroma.Web.Preload.build_tags/2
(elixir 1.10.4) lib/enum.ex:2111: Enum."-reduce/3-lists^foldl/2-0-"/3
(pleroma 2.4.4) lib/pleroma/web/preload.ex:11: Pleroma.Web.Preload.build_tags/2
(pleroma 2.4.4) lib/pleroma/web/fallback/redirect_controller.ex:99: Pleroma.Web.Fallback.RedirectController.preload_data/2
(pleroma 2.4.4) lib/pleroma/web/fallback/redirect_controller.ex:57: Pleroma.Web.Fallback.RedirectController.redirector_with_preload/2
(pleroma 2.4.4) lib/pleroma/web/fallback/redirect_controller.ex:5: Pleroma.Web.Fallback.RedirectController.action/2
(pleroma 2.4.4) lib/pleroma/web/fallback/redirect_controller.ex:5: Pleroma.Web.Fallback.RedirectController.phoenix_controller_pipeline/2
17:02:11.871 request_id=xxxxxxxxxxx[info] Sent 200 in 690ms
17:02:12.183 request_id=xxxxxxxxxxx[info] Sent 200 in 317ms
17:02:12.200 request_id=xxxxxxxxxxx[info] Sent 200 in 1095ms
17:02:12.699 [error] Elixir.Pleroma.Web.MastodonAPI.SearchController search error: %FunctionClauseError{args: nil, arity: 1, clauses: nil, function: :"-pin_data_from_featured_collection/1-fun-0-", kind: nil, module: Pleroma.Web.ActivityPub.ActivityPub}
```
When posting to the user:
```
17:02:41.770 request_id=xxxxxxxxxxx[error] Internal server error: %Cachex.ExecutionError{message: "no function clause matching in anonymous fn/1 in Pleroma.Web.ActivityPub.ActivityPub.pin_data_from_featured_collection/1"}
17:02:41.771 request_id=xxxxxxxxxxx[info] Sent 500 in 764ms
17:02:41.777 [error] #PID<0.9334.0> running Pleroma.Web.Endpoint (connection #PID<0.9333.0>, stream id 1) terminated
Server: not.iee.engineer:80 (http)
Request: POST /api/v1/statuses
** (exit) an exception was raised:
** (Cachex.ExecutionError) no function clause matching in anonymous fn/1 in Pleroma.Web.ActivityPub.ActivityPub.pin_data_from_featured_collection/1
(cachex 3.3.0) lib/cachex.ex:1443: Cachex.unwrap_unsafe/1
(pleroma 2.4.4) lib/pleroma/formatter.ex:24: Pleroma.Formatter.escape_mention_handler/4
(linkify 0.5.1) lib/linkify/parser.ex:389: Linkify.Parser.link_mention/4
(linkify 0.5.1) lib/linkify/parser.ex:444: Linkify.Parser.check_and_link_reducer/4
(elixir 1.10.4) lib/enum.ex:3686: Enumerable.List.reduce/3
(elixir 1.10.4) lib/enum.ex:2161: Enum.reduce_while/3
(linkify 0.5.1) lib/linkify/parser.ex:155: Linkify.Parser.do_parse/3
(linkify 0.5.1) lib/linkify/parser.ex:72: Linkify.Parser.parse/2
```https://git.pleroma.social/pleroma/pleroma-support/-/issues/79Exact steps to move from one server (running Pleroma) to a different server2022-11-24T00:02:46ZWesley MooreExact steps to move from one server (running Pleroma) to a different serverI've seen https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3524 and https://git.pleroma.social/pleroma/pleroma-support/-/issues/75 and the move note on https://docs.joinmastodon.org/spec/activitypub/#profile but it's still a ...I've seen https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3524 and https://git.pleroma.social/pleroma/pleroma-support/-/issues/75 and the move note on https://docs.joinmastodon.org/spec/activitypub/#profile but it's still a little unclear to me the exact steps required to migrate from one server to another.
Is it something like this:
1. Set up new server
1. `PUT /api/pleroma/aliases` to add alias pointing at account on new server
2. Do the equivalent on the new server pointing back at the account on the old server
3. `POST /api/pleroma/move_account` to emit a `Move` activity and hopefully migrate followers from the old server to the new server.https://git.pleroma.social/pleroma/pleroma-support/-/issues/86My instance can no longer render timelines reliably2022-11-19T22:25:33ZAzureMy instance can no longer render timelines reliablyAs of two hours ago, my instance can no longer render timelines properly. Initially the local timeline, and then home timelines. I get errors like:
```
Nov 19 16:15:33 coyote mix[770]: 16:15:33.500 [error] Postgrex.Protocol (#PID<0.1248...As of two hours ago, my instance can no longer render timelines properly. Initially the local timeline, and then home timelines. I get errors like:
```
Nov 19 16:15:33 coyote mix[770]: 16:15:33.500 [error] Postgrex.Protocol (#PID<0.1248.0>) disconnected: ** (DBConnection.ConnectionError) client #PID<0
.6467.0> timed out because it queued and checked out the connection for longer than 15000ms
Nov 19 16:15:33 coyote mix[770]: #PID<0.6467.0> was at location:
Nov 19 16:15:33 coyote mix[770]: :prim_inet.recv0/3
Nov 19 16:15:33 coyote mix[770]: (postgrex 0.15.9) lib/postgrex/protocol.ex:2972: Postgrex.Protocol.msg_recv/4
Nov 19 16:15:33 coyote mix[770]: (postgrex 0.15.9) lib/postgrex/protocol.ex:2014: Postgrex.Protocol.recv_bind/3
Nov 19 16:15:33 coyote mix[770]: (postgrex 0.15.9) lib/postgrex/protocol.ex:1869: Postgrex.Protocol.bind_execute_close/4
Nov 19 16:15:33 coyote mix[770]: (db_connection 2.4.0) lib/db_connection/holder.ex:325: DBConnection.Holder.holder_apply/4
Nov 19 16:15:33 coyote mix[770]: (db_connection 2.4.0) lib/db_connection.ex:1314: DBConnection.run_execute/5
Nov 19 16:15:33 coyote mix[770]: (db_connection 2.4.0) lib/db_connection.ex:1409: DBConnection.run/6
Nov 19 16:15:33 coyote mix[770]: (db_connection 2.4.0) lib/db_connection.ex:631: DBConnection.execute/4
Nov 19 16:15:33 coyote mix[770]: 16:15:33.504 request_id=FykY50IMKjZer2wAAFMh [error] Internal server error: %DBConnection.ConnectionError{message: "tcp recv: closed (the connection was closed by the pool, possibly due to a timeout or because the pool has been terminated)", reason: :error, severity: :error}
Nov 19 16:15:33 coyote mix[770]: 16:15:33.505 [error] #PID<0.6467.0> running Pleroma.Web.Endpoint (connection #PID<0.6466.0>, stream id 1) terminated
Nov 19 16:15:33 coyote mix[770]: Server: tailswish.industries:80 (http)
Nov 19 16:15:33 coyote mix[770]: Request: GET /api/v1/timelines/home?with_muted=false&limit=20
Nov 19 16:15:33 coyote mix[770]: ** (exit) an exception was raised:
Nov 19 16:15:33 coyote mix[770]: ** (DBConnection.ConnectionError) tcp recv: closed (the connection was closed by the pool, possibly due to a timeout or because the pool has been terminated)
Nov 19 16:15:33 coyote mix[770]: (ecto_sql 3.6.2) lib/ecto/adapters/sql.ex:760: Ecto.Adapters.SQL.raise_sql_call_error/1
Nov 19 16:15:33 coyote mix[770]: (ecto_sql 3.6.2) lib/ecto/adapters/sql.ex:693: Ecto.Adapters.SQL.execute/5
Nov 19 16:15:33 coyote mix[770]: (ecto 3.6.2) lib/ecto/repo/queryable.ex:224: Ecto.Repo.Queryable.execute/4
Nov 19 16:15:33 coyote mix[770]: (ecto 3.6.2) lib/ecto/repo/queryable.ex:19: Ecto.Repo.Queryable.all/3
Nov 19 16:15:33 coyote mix[770]: (pleroma 2.4.4-6-g112aea8e-tailswish) lib/pleroma/pagination.ex:40: Pleroma.Pagination.fetch_paginated/4
Nov 19 16:15:33 coyote mix[770]: (pleroma 2.4.4-6-g112aea8e-tailswish) lib/pleroma/web/activity_pub/activity_pub.ex:484: Pleroma.Web.ActivityPub.ActivityPub.fetch_activities/3
Nov 19 16:15:33 coyote mix[770]: (pleroma 2.4.4-6-g112aea8e-tailswish) lib/pleroma/web/mastodon_api/controllers/timeline_controller.ex:56: Pleroma.Web.MastodonAPI.TimelineController.home/2
Nov 19 16:15:33 coyote mix[770]: (pleroma 2.4.4-6-g112aea8e-tailswish) lib/pleroma/web/mastodon_api/controllers/timeline_controller.ex:5: Pleroma.Web.MastodonAPI.TimelineController.action/2
```
I have tried running both a remote prune and a full vacuum but neither one seems to have made an improvement.
This doesn't seem to have been triggered by any change in configuration, starting on its own this afternoon when I wasn't anywhere near the system.https://git.pleroma.social/pleroma/pleroma-support/-/issues/83Can't edit posts in the latest version2022-11-15T19:08:17ZCarlos SolísCan't edit posts in the latest versionRecently, I upgraded my instance of Pleroma (backend to 2.4.4, Pleroma-FE frontend to commit 6263ad75 (November 8)), and I still couldn't find the option to edit posts enabled. I checked my admin dashboard and found nothing I could turn ...Recently, I upgraded my instance of Pleroma (backend to 2.4.4, Pleroma-FE frontend to commit 6263ad75 (November 8)), and I still couldn't find the option to edit posts enabled. I checked my admin dashboard and found nothing I could turn on to enable this functionality. Is there some particular setting I'm missing?https://git.pleroma.social/pleroma/pleroma-support/-/issues/75[Question] Is it possible to "move" account from mastodon to pleroma?2022-11-08T00:45:46ZGrischa Brockhaus[Question] Is it possible to "move" account from mastodon to pleroma?Hello.
Mastodon allows moving accounts from one instance to another (mastodon) instance.
Is it possible to move my mastodon account to another instance running pleroma the same way, so my followers know, I have moved? Or is this "instan...Hello.
Mastodon allows moving accounts from one instance to another (mastodon) instance.
Is it possible to move my mastodon account to another instance running pleroma the same way, so my followers know, I have moved? Or is this "instance hopping" very mastodon specific?