pleroma issueshttps://git.pleroma.social/pleroma/pleroma/-/issues2023-06-19T00:08:21Zhttps://git.pleroma.social/pleroma/pleroma/-/issues/3137Internal links don't load the page properly (unless opened in a new tab)2023-06-19T00:08:21ZLotte VInternal links don't load the page properly (unless opened in a new tab)<!--
### Precheck
* For support use https://git.pleroma.social/pleroma/pleroma-support or [community channels](https://git.pleroma.social/pleroma/pleroma#community-channels).
* Please do a quick search to ensure no similar bug has been ...<!--
### Precheck
* For support use https://git.pleroma.social/pleroma/pleroma-support or [community channels](https://git.pleroma.social/pleroma/pleroma#community-channels).
* Please do a quick search to ensure no similar bug has been reported before. If the bug has not been addressed after 2 weeks, it's fine to bump it.
* Try to ensure that the bug is actually related to the Pleroma backend. For example, if a bug happens in Pleroma-FE but not in Mastodon-FE or mobile clients, it's likely that the bug should be filed in [Pleroma-FE](https://git.pleroma.social/pleroma/pleroma-fe/issues/new) repository.
-->
### Environment
* **Installation type (OTP or From Source):** From source
* **Pleroma version (could be found in the "Version" tab of settings in Pleroma-FE):** 2.5.52-235-g589301ce-develop
* **Elixir version (`elixir -v` for from source installations, N/A for OTP):** 1.13.0
* **Operating system:** Debian 10 (Buster)
* **PostgreSQL version (`psql -V`):** 11.12
### Bug description
Whenever I click on a link to load a different page from my instance, the page does not load properly. I have to refresh every single time I click on an internal link, or open the link in a new tab. I can work around this most of the time, but for example, right now I am unable to log out unless I clear my instance's cookies (since I can't open that in a new tab). This is quite the hassle and not something I want to do every single time. It's the same way in every browser, so that can't be the issue either.
I also can't collapse threads anymore for some reason, though if I should make a separate issue about this, I will. Though my suspicion is that the two are related.https://git.pleroma.social/pleroma/pleroma/-/issues/3136Can upload (but not display) media2023-07-06T14:11:12ZThom CatCan upload (but not display) media<!--
### Precheck
* For support use https://git.pleroma.social/pleroma/pleroma-support or [community channels](https://git.pleroma.social/pleroma/pleroma#community-channels).
* Please do a quick search to ensure no similar bug has been ...<!--
### Precheck
* For support use https://git.pleroma.social/pleroma/pleroma-support or [community channels](https://git.pleroma.social/pleroma/pleroma#community-channels).
* Please do a quick search to ensure no similar bug has been reported before. If the bug has not been addressed after 2 weeks, it's fine to bump it.
* Try to ensure that the bug is actually related to the Pleroma backend. For example, if a bug happens in Pleroma-FE but not in Mastodon-FE or mobile clients, it's likely that the bug should be filed in [Pleroma-FE](https://git.pleroma.social/pleroma/pleroma-fe/issues/new) repository.
-->
### Environment
* Installation type (OTP or From Source): Source (Docker)
* Pleroma version (could be found in the "Version" tab of settings in Pleroma-FE): 2.5.52-235-g589301ce-develop
* Elixir version (`elixir -v` for from source installations, N/A for OTP): "Elixir 1.14.2 (compiled with Erlang/OTP 25)"
* Operating system: Ubuntu 20.04.6
* PostgreSQL version (`psql -V`): 12.1
### Bug description
After spinning up Pleroma using the [angristan Dockerfile repo](https://github.com/angristan/docker-pleroma), I am able to upload media, but am unable to view the same media from any web browser or app. Specifically, I will open the piece of Media in a new tab, and will get a "Too many redirects" error. Opening the dev console and looking at the network tab shows a dozen 302 redirects with the exact same url in the `location` header. "Media" includes profile pictures, site logo, or any media included in posts. **Remote** media from other Mastodon/Pleroma instances works just fine, no issues.
Chrome (Android)
![Screenshot_20230615-172220](/uploads/9aea3000830d006c72d11cf054bea69b/Screenshot_20230615-172220.png)
Fedilab
![Screenshot_20230615-172252](/uploads/6ee9b3a3eddb8db39bf315145714e71c/Screenshot_20230615-172252.png)
I see the media hit my `uploads` folder and have tried `chmod -r`ing the permissions to `777`.
![Screenshot_20230615-172624_2](/uploads/95e1800e1e02031baba807106f50ab5c/Screenshot_20230615-172624_2.png)
I've quadruple checked that my `nginx` config is exactly the same as the base config provided (except for the SSL certs, and `phoenix` upstream stanza being the IP for my docker container). I have no other issues with the install, only the uploads are the issue.https://git.pleroma.social/pleroma/pleroma/-/issues/3131Unable to close/resolve report if the actor's account is deactivated2023-07-02T21:27:16ZYour New SJW WaifuUnable to close/resolve report if the actor's account is deactivated<!--
### Precheck
* For support use https://git.pleroma.social/pleroma/pleroma-support or [community channels](https://git.pleroma.social/pleroma/pleroma#community-channels).
* Please do a quick search to ensure no similar bug has been ...<!--
### Precheck
* For support use https://git.pleroma.social/pleroma/pleroma-support or [community channels](https://git.pleroma.social/pleroma/pleroma#community-channels).
* Please do a quick search to ensure no similar bug has been reported before. If the bug has not been addressed after 2 weeks, it's fine to bump it.
* Try to ensure that the bug is actually related to the Pleroma backend. For example, if a bug happens in Pleroma-FE but not in Mastodon-FE or mobile clients, it's likely that the bug should be filed in [Pleroma-FE](https://git.pleroma.social/pleroma/pleroma-fe/issues/new) repository.
-->
### Environment
* Installation type (OTP or From Source):
- [ ] The virgin OTP install
- [X] The chad source install
* Pleroma version (could be found in the "Version" tab of settings in Pleroma-FE): 31ec5cd3
* Elixir version (`elixir -v` for from source installations, N/A for OTP):
```
Erlang/OTP 25 [erts-13.0.4] [source] [64-bit] [smp:24:24] [ds:24:24:10] [async-threads:1] [jit:ns]
Elixir 1.13.4 (compiled with Erlang/OTP 25)
```
* Operating system: Ubuntu Pro 22.04
* PostgreSQL version (`psql -V`): 15.3
### Bug description
I had a report from a local user about a remote user. The local user had deactivated their account shortly after making the report.
I could not mark the report closed or resolved until I re-activated the account that made the report. At which time I was able to mark the report resolved.
Interesting the API was returning a 404 when trying to change the state of a report with the actor's account deactivated.https://git.pleroma.social/pleroma/pleroma/-/issues/3126Confirmed user javascript execution bug2023-05-29T08:48:04ZlainConfirmed user javascript execution bugPoa.st has apparently lost some user token to a rather sophisticated attack.
Apparently, the user was able to upload javascript (nothing unusual here) and then executive it via a nostr bridge. I don't understand how this is supposed to...Poa.st has apparently lost some user token to a rather sophisticated attack.
Apparently, the user was able to upload javascript (nothing unusual here) and then executive it via a nostr bridge. I don't understand how this is supposed to work yet.
The poa.st admin has written about it, I'll quote the full post here:
https://poa.st/notice/AW21NSFdXhFPb2Zzai
> on may 19, 2023 an unknown user registered the domain name fedirelay.xyz and setup a fake mostr (nostr) relay to listen for requests on the fediverse.
>
> on may 20, 2023 at 20:52 (utc) a user uploaded the attached document to poast. it was originally an obfuscated javascript file (unobfuscated and attached it here, renamed to .txt so you can view it in any editor).
>
> what this javascript file does is take the viewers oauth token, encode it to make it look like a nostr pubkey and then forced the clandestine mostr relay to look up that user locally giving that server the encoded token all while appearing to be a legitimate mostr (nostr) bridge
>
> i have taken steps to completely limit access to the admin api and corrected any CSP or other issues that could possibly have contributed to this, however most of you (instance owners) are still vulnerable to it. the default pleroma install serves media files on your root domain as a local folder (i.e. yourdomain.xyz/media) and the default CSP for any site is to allow executing scripts via the root domain. in order to prevent this you should take steps to either move your media from yourdomain.xyz/media to media.yourdomain.xyz (or any subdomain outside of your root domain) or perhaps by limiting the CSP for that subdirectory via nginx configuration.
>
> if you are an instance owner, the obfuscated file hash is `b2977f2d97f598d2ebd6dcf37afd9047b5da2b6dc95a7b2824fb111c906fb117` so you can search yourdomain.xyz/media/b2977f2d97f598d2ebd6dcf37afd9047b5da2b6dc95a7b2824fb111c906fb117.js and see if you have it on your server.
>
> no user password or anything beyond email:user and your chats and media associated with them have been archived and everybody's tokens were dropped forcing you to all relog on your accounts. this is to ensure that if any of you had tokens exposed by viewing this JavaScript, they are no longer functional on poast.
>
> sorry to anybody i let down but i could never have foreseen this level of sophistication and i would not have ever expected it. now that we are aware of it, we will be more diligent in the future. thanks for being here with us still friends
> 4ed28ef4fa5e18bfa5c1f7…7e2fcc6d0cdb0215f15.txt
[4ed28ef4fa5e18bfa5c1f75a5c1cc759f7b718c0b600e7e2fcc6d0cdb0215f15.txt](/uploads/652ff240e96c1c9913c5eff75dba2778/4ed28ef4fa5e18bfa5c1f75a5c1cc759f7b718c0b600e7e2fcc6d0cdb0215f15.txt)https://git.pleroma.social/pleroma/pleroma/-/issues/3123cannot post status on new instance2023-05-25T16:39:00Zjeffcannot post status on new instance
### Environment
* Installation type (OTP or From Source): source (develop)
* Pleroma version (could be found in the "Version" tab of settings in Pleroma-FE):
```
Backend version
2.5.51-156-g5433742f-develop
Frontend version
c730c9...
### Environment
* Installation type (OTP or From Source): source (develop)
* Pleroma version (could be found in the "Version" tab of settings in Pleroma-FE):
```
Backend version
2.5.51-156-g5433742f-develop
Frontend version
c730c9b6
```
* Elixir version (`elixir -v` for from source installations, N/A for OTP):
```
Erlang/OTP 25 [erts-13.1.5] [source] [64-bit] [smp:3:3] [ds:3:3:10] [async-threads:1] [jit:ns]
Elixir 1.14.0 (compiled with Erlang/OTP 24)
```
* Operating system: debian bookworm
* PostgreSQL version (`psql -V`):
```
psql (PostgreSQL) 15.3 (Debian 15.3-1.pgdg120+1)
```
### Bug description
try to make new post, get a http 422 from the request with a giant pile of json as the error message.
![Screenshot_20230525_122231](/uploads/09f185f4d74f77d1293d4778f35c56cb/Screenshot_20230525_122231.webp)https://git.pleroma.social/pleroma/pleroma/-/issues/3121Non-HTTP/S "url" entries cause entire post to be rejected (blocks FEP-fffd)2023-06-11T11:02:40ZAdam NelsonNon-HTTP/S "url" entries cause entire post to be rejected (blocks FEP-fffd)[The current draft of FEP-fffd](https://codeberg.org/fediverse/fep/src/commit/0c2bbbe6b157f052a1b3109354a7574e2d45058f/feps/fep-fffd.md) proposes adding additional `url` entries to signal that a post is bridged from another protocol, lik...[The current draft of FEP-fffd](https://codeberg.org/fediverse/fep/src/commit/0c2bbbe6b157f052a1b3109354a7574e2d45058f/feps/fep-fffd.md) proposes adding additional `url` entries to signal that a post is bridged from another protocol, like Nostr or AT. This requires using non-HTTP/S URIs, such as `nostr:` or `at:`, to identify objects on these alternate protocols.
There's no need for Pleroma to actually support this FEP, but currently Pleroma will reject any posts with a non-HTTP/S URI in `url`. This makes implementing FEP-fffd in other applications impractical because it will cause posts to be ignored by Pleroma.
Ideally, Pleroma would simply ignore `url` entries it does not understand, without rejecting a post entirely.https://git.pleroma.social/pleroma/pleroma/-/issues/3119Send a 413 when a user bio goes beyond character limit2023-06-27T18:49:45ZDuponinSend a 413 when a user bio goes beyond character limitWhen a user updates their bio out of character limit boundary, backend is sending a 403 error code and `{"error":"Invalid request"}`.
The correct error code is 413 "Payload Too Large" and answer should be `{"error":"Payload Too Large"}`....When a user updates their bio out of character limit boundary, backend is sending a 403 error code and `{"error":"Invalid request"}`.
The correct error code is 413 "Payload Too Large" and answer should be `{"error":"Payload Too Large"}`.
Relates to #3053.tusooatusooahttps://git.pleroma.social/pleroma/pleroma/-/issues/3114`content-disposition` HTTP header from uploaded media lacks `disposition-type...2023-04-26T15:39:22ZKagami Rosylight`content-disposition` HTTP header from uploaded media lacks `disposition-type` field<!--
### Precheck
* For support use https://git.pleroma.social/pleroma/pleroma-support or [community channels](https://git.pleroma.social/pleroma/pleroma#community-channels).
* Please do a quick search to ensure no similar bug has been ...<!--
### Precheck
* For support use https://git.pleroma.social/pleroma/pleroma-support or [community channels](https://git.pleroma.social/pleroma/pleroma#community-channels).
* Please do a quick search to ensure no similar bug has been reported before. If the bug has not been addressed after 2 weeks, it's fine to bump it.
* Try to ensure that the bug is actually related to the Pleroma backend. For example, if a bug happens in Pleroma-FE but not in Mastodon-FE or mobile clients, it's likely that the bug should be filed in [Pleroma-FE](https://git.pleroma.social/pleroma/pleroma-fe/issues/new) repository.
-->
### Bug description
It seems Pleroma sets `content-disposition` field in invalid way:
https://git.pleroma.social/pleroma/pleroma/-/blob/e853cfe7c3438650fd0f95bfe69e2bccfe12390c/lib/pleroma/web/plugs/uploaded_media.ex#L40
The format needs to start with `inline;` or `attachment;` but this line lacks that and caused issue on recent versions of Misskey. (https://github.com/misskey-dev/misskey/issues/10626)https://git.pleroma.social/pleroma/pleroma/-/issues/3073Previous reactions no longer shown2023-03-27T10:05:48ZcptnPrevious reactions no longer shownAfter upgrading to latest develop (Backend version 2.5.51-78-gbf9db784-develop Frontend version fa532b1f) previous emoji reactions are no longer shown in Pleroma-FE or Husky. Adding this issue here since they first disappeared after upgr...After upgrading to latest develop (Backend version 2.5.51-78-gbf9db784-develop Frontend version fa532b1f) previous emoji reactions are no longer shown in Pleroma-FE or Husky. Adding this issue here since they first disappeared after upgrading just BE. They didn't come back after upgrading FE.https://git.pleroma.social/pleroma/pleroma/-/issues/3068Is there a rate limiter to resist inbox flood attack?2023-03-14T04:13:38ZdebulaIs there a rate limiter to resist inbox flood attack?Today my instance suddenly went offline.
After checking the logs, it is found that pleroma cannot connect to postgresql.
When I try to restart the service, the CPU and memory usage of the server goes crazy.
I realized it was unusual, ...Today my instance suddenly went offline.
After checking the logs, it is found that pleroma cannot connect to postgresql.
When I try to restart the service, the CPU and memory usage of the server goes crazy.
I realized it was unusual, so I shut down the service. Then the reverse proxy added a new line of `POST /inbox` error every second.
At the time of writing this issue, these errors are still continuing. Since I didn't set up a procedure to record IP and request content, I still don't know who launched the attack ...
Although this may be a bit off-topic:
- Are there any protection mechanisms in Pleroma against flood attacks?
- What would you do if you were to encounter such an attack?https://git.pleroma.social/pleroma/pleroma/-/issues/3066DM clearing functionality2023-03-06T20:01:18ZJeff CliffDM clearing functionalityit would be nice if there was some means of deleting DMs, either for the admin (perhaps yearly pruning it) or as the user
use case: it's been a year since I told friend X that Y. We both know it. We both have saved it if we wanted to....it would be nice if there was some means of deleting DMs, either for the admin (perhaps yearly pruning it) or as the user
use case: it's been a year since I told friend X that Y. We both know it. We both have saved it if we wanted to. that Y is a risk to keep around because sooner or later someone will pwn the server.
and yeah, sure the other server could still have it but the point is on *that* server.https://git.pleroma.social/pleroma/pleroma/-/issues/3065OAuth scopes should have (translatable) descriptions2023-05-17T18:51:27ZtusooaOAuth scopes should have (translatable) descriptionsCurrently our web UI only gives out the name of the scope, without ever explaining what it does. It should, instead, have an explanation.Currently our web UI only gives out the name of the scope, without ever explaining what it does. It should, instead, have an explanation.https://git.pleroma.social/pleroma/pleroma/-/issues/3064trailing slash in url bamboozles relay fetcher2023-02-20T22:37:13Zdanso dansotrailing slash in url bamboozles relay fetcher```
» bin/pleroma_ctl relay follow 'https://relay-new.activitypub.ca/'
00:19:00.832 [error] Could not decode user at fetch https://relay-new.activitypub.ca/, {:content_type, "text/html; charset=utf-8"}
00:19:00.844 [error] error: :not_...```
» bin/pleroma_ctl relay follow 'https://relay-new.activitypub.ca/'
00:19:00.832 [error] Could not decode user at fetch https://relay-new.activitypub.ca/, {:content_type, "text/html; charset=utf-8"}
00:19:00.844 [error] error: :not_found
» bin/pleroma_ctl relay follow 'https://relay-new.activitypub.ca'
»
```https://git.pleroma.social/pleroma/pleroma/-/issues/30622.5.0 build from source: '/opt/pleroma/lib/crypt-0.4.3/priv/crypt.so: undefin...2023-05-26T22:16:26ZKuoi Z2.5.0 build from source: '/opt/pleroma/lib/crypt-0.4.3/priv/crypt.so: undefined symbol: crypt'"<!--
### Precheck
* For support use https://git.pleroma.social/pleroma/pleroma-support or [community channels](https://git.pleroma.social/pleroma/pleroma#community-channels).
* Please do a quick search to ensure no similar bug has been ...<!--
### Precheck
* For support use https://git.pleroma.social/pleroma/pleroma-support or [community channels](https://git.pleroma.social/pleroma/pleroma#community-channels).
* Please do a quick search to ensure no similar bug has been reported before. If the bug has not been addressed after 2 weeks, it's fine to bump it.
* Try to ensure that the bug is actually related to the Pleroma backend. For example, if a bug happens in Pleroma-FE but not in Mastodon-FE or mobile clients, it's likely that the bug should be filed in [Pleroma-FE](https://git.pleroma.social/pleroma/pleroma-fe/issues/new) repository.
-->
### Environment
* Installation type (OTP or From Source): OTP, Compile from source by myself
* Pleroma version (could be found in the "Version" tab of settings in Pleroma-FE): 2.5.0
* Elixir version (`elixir -v` for from source installations, N/A for OTP): 1.14.0
* Operating system: ArchLinux
* PostgreSQL version (`psql -V`): 15.1
### Bug description
My build command is that
```
cd git_repo_tag_2.5.0
mix local.hex --force
mix local.rebar --force
mix deps.get
mix deps.get --only prod
mkdir /opt/pleroma
mix release --path /opt/pleroma
```
After it's built I configure it. With the configuration below, I successfully run the official OTP release but fail with my build OTP. I already installed [libxcrypt-compat](https://archlinux.org/packages/core/x86_64/libxcrypt-compat/) and [libxcrypt](https://archlinux.org/packages/core/x86_64/libxcrypt/)
```
sudo -Hu pleroma /opt/pleroma/bin/pleroma_ctl instance gen --output "/etc/pleroma/config.exs" --output-psql "/tmp/setup_otp_db.psql" --uploads-dir "/var/lib/pleroma/uploads" --static-dir "/var/lib/pleroma/static" --dbname "pleroma" --dbuser "pleroma"
sudo -Hu postgres psql -f "/tmp/setup_otp_db.psql"
sudo -Hu pleroma /opt/pleroma/bin/pleroma_ctl migrate
```
the error log is here
<details>
```
Feb 11 21:54:53 helix pleroma[2934]: crasher:
Feb 11 21:54:53 helix pleroma[2934]: initial call: application_master:init/4
Feb 11 21:54:53 helix pleroma[2934]: pid: <0.3557.0>
Feb 11 21:54:53 helix pleroma[2934]: registered_name: []
Feb 11 21:54:53 helix pleroma[2934]: exception exit: {{shutdown,
Feb 11 21:54:53 helix pleroma[2934]: {failed_to_start_child,kernel_safe_sup,
Feb 11 21:54:53 helix pleroma[2934]: {on_load_function_failed,crypt,
Feb 11 21:54:53 helix pleroma[2934]: {error,
Feb 11 21:54:53 helix pleroma[2934]: {load_failed,
Feb 11 21:54:53 helix pleroma[2934]: "Failed to load NIF library: '/opt/pleroma/lib/crypt-0.4.3/priv/crypt.so: undefined symbol: crypt'"}}}}},
Feb 11 21:54:53 helix pleroma[2934]: {kernel,start,[normal,[]]}}
Feb 11 21:54:53 helix pleroma[2934]: in function application_master:init/4 (application_master.erl, line 142)
Feb 11 21:54:53 helix pleroma[2934]: ancestors: [<0.3556.0>]
Feb 11 21:54:53 helix pleroma[2934]: message_queue_len: 1
Feb 11 21:54:53 helix pleroma[2934]: messages: [{'EXIT',<0.3558.0>,normal}]
Feb 11 21:54:53 helix pleroma[2934]: links: [<0.3556.0>,<0.3555.0>]
Feb 11 21:54:53 helix pleroma[2934]: dictionary: []
Feb 11 21:54:53 helix pleroma[2934]: trap_exit: true
Feb 11 21:54:53 helix pleroma[2934]: status: running
Feb 11 21:54:53 helix pleroma[2934]: heap_size: 987
Feb 11 21:54:53 helix pleroma[2934]: stack_size: 28
Feb 11 21:54:53 helix pleroma[2934]: reductions: 182
Feb 11 21:54:53 helix pleroma[2934]: neighbours:
Feb 11 21:54:53 helix pleroma[2934]:
Feb 11 21:54:53 helix pleroma[2934]: =INFO REPORT==== 11-Feb-2023::21:54:53.824740 ===
Feb 11 21:54:53 helix pleroma[2934]: application: kernel
Feb 11 21:54:53 helix pleroma[2934]: exited: {{shutdown,
Feb 11 21:54:53 helix pleroma[2934]: {failed_to_start_child,kernel_safe_sup,
Feb 11 21:54:53 helix pleroma[2934]: {on_load_function_failed,crypt,
Feb 11 21:54:53 helix pleroma[2934]: {error,
Feb 11 21:54:53 helix pleroma[2934]: {load_failed,
Feb 11 21:54:53 helix pleroma[2934]: "Failed to load NIF library: '/opt/pleroma/lib/crypt-0.4.3/priv/crypt.so: undefined symbol: crypt'"}}}}},
Feb 11 21:54:53 helix pleroma[2934]: {kernel,start,[normal,[]]}}
Feb 11 21:54:53 helix pleroma[2934]: type: permanent
Feb 11 21:54:53 helix pleroma[2934]:
Feb 11 21:54:54 helix pleroma[2934]: {"Kernel pid terminated",application_controller,"{application_start_failure,kernel,{{shutdown,{failed_to_start_child,kernel_safe_sup,{on_load_function_failed,crypt,{error,{load_failed,\"Failed to load NIF library: '/opt/pleroma/lib/crypt-0.4.3/priv/crypt.so: undefined symbol: crypt'\"}}}}},{kernel,start,[normal,[]]}}}"}
Feb 11 21:54:54 helix pleroma[2934]: Kernel pid terminated (application_controller) ({application_start_failure,kernel,{{shutdown,{failed_to_start_child,kernel_safe_sup,{on_load_function_failed,crypt,{error,{load_failed,"Failed to load NIF library: '/opt/pleroma/lib/crypt-0.4.3/priv/crypt.so: undefined symbol: crypt'"}}}}},{kernel,start,[normal,[]]}}})
Feb 11 21:54:54 helix pleroma[2934]:
Feb 11 21:54:54 helix pleroma[2934]: Crash dump is being written to: erl_crash.dump...done
Feb 11 21:54:54 helix systemd[1]: pleroma.service: Main process exited, code=exited, status=1/FAILURE
Feb 11 21:54:54 helix systemd[1]: pleroma.service: Failed with result 'exit-code'.
Feb 11 21:54:54 helix systemd[1]: pleroma.service: Unit process 450 (epmd) remains running after unit stopped.
Feb 11 21:54:54 helix systemd[1]: pleroma.service: Consumed 5.104s CPU time.
Feb 11 21:54:54 helix systemd[1]: pleroma.service: Scheduled restart job, restart counter is at 37.
Feb 11 21:54:54 helix systemd[1]: Stopped Pleroma social network.
Feb 11 21:54:54 helix systemd[1]: pleroma.service: Consumed 5.104s CPU time.
Feb 11 21:54:54 helix systemd[1]: pleroma.service: Found left-over process 450 (epmd) in control group while starting unit. Ignoring.
Feb 11 21:54:54 helix systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Feb 11 21:54:54 helix systemd[1]: Started Pleroma social network.
Feb 11 21:54:55 helix systemd[1]: Stopping Pleroma social network...
Feb 11 21:54:56 helix pleroma[3065]: --rpc-eval : RPC failed with reason :nodedown
Feb 11 21:54:56 helix systemd[1]: pleroma.service: Control process exited, code=exited, status=1/FAILURE
Feb 11 21:54:58 helix pleroma[3007]: =SUPERVISOR REPORT==== 11-Feb-2023::21:54:58.407014 ===
Feb 11 21:54:58 helix pleroma[3007]: supervisor: {local,kernel_sup}
Feb 11 21:54:58 helix pleroma[3007]: errorContext: start_error
Feb 11 21:54:58 helix pleroma[3007]: reason: {on_load_function_failed,crypt,
Feb 11 21:54:58 helix pleroma[3007]: {error,
Feb 11 21:54:58 helix pleroma[3007]: {load_failed,
Feb 11 21:54:58 helix pleroma[3007]: "Failed to load NIF library: '/opt/pleroma/lib/crypt-0.4.3/priv/crypt.so: undefined symbol: crypt'"}}}
Feb 11 21:54:58 helix pleroma[3007]: offender: [{pid,undefined},
Feb 11 21:54:58 helix pleroma[3007]: {id,kernel_safe_sup},
Feb 11 21:54:58 helix pleroma[3007]: {mfargs,{supervisor,start_link,
Feb 11 21:54:58 helix pleroma[3007]: [{local,kernel_safe_sup},kernel,safe]}},
Feb 11 21:54:58 helix pleroma[3007]: {restart_type,permanent},
Feb 11 21:54:58 helix pleroma[3007]: {significant,false},
Feb 11 21:54:58 helix pleroma[3007]: {shutdown,infinity},
Feb 11 21:54:58 helix pleroma[3007]: {child_type,supervisor}]
Feb 11 21:54:58 helix pleroma[3007]:
Feb 11 21:54:58 helix pleroma[3007]: =CRASH REPORT==== 11-Feb-2023::21:54:58.409484 ===
Feb 11 21:54:58 helix pleroma[3007]: crasher:
Feb 11 21:54:58 helix pleroma[3007]: initial call: supervisor:kernel/1
Feb 11 21:54:58 helix pleroma[3007]: pid: <0.3585.0>
Feb 11 21:54:58 helix pleroma[3007]: registered_name: []
Feb 11 21:54:58 helix pleroma[3007]: exception exit: {on_load_function_failed,crypt,
Feb 11 21:54:58 helix pleroma[3007]: {error,
Feb 11 21:54:58 helix pleroma[3007]: {load_failed,
Feb 11 21:54:58 helix pleroma[3007]: "Failed to load NIF library: '/opt/pleroma/lib/crypt-0.4.3/priv/crypt.so: undefined symbol: crypt'"}}}
Feb 11 21:54:58 helix pleroma[3007]: in function init:run_on_load_handlers/0
Feb 11 21:54:58 helix pleroma[3007]: in call from kernel:init/1 (kernel.erl, line 196)
Feb 11 21:54:58 helix pleroma[3007]: in call from supervisor:init/1 (supervisor.erl, line 330)
Feb 11 21:54:58 helix pleroma[3007]: in call from gen_server:init_it/2 (gen_server.erl, line 851)
Feb 11 21:54:58 helix pleroma[3007]: in call from gen_server:init_it/6 (gen_server.erl, line 814)
Feb 11 21:54:58 helix pleroma[3007]: ancestors: [kernel_sup,<0.3558.0>]
Feb 11 21:54:58 helix pleroma[3007]: message_queue_len: 0
Feb 11 21:54:58 helix pleroma[3007]: messages: []
Feb 11 21:54:58 helix pleroma[3007]: links: [<0.3560.0>]
Feb 11 21:54:58 helix pleroma[3007]: dictionary: []
Feb 11 21:54:58 helix pleroma[3007]: trap_exit: true
Feb 11 21:54:58 helix pleroma[3007]: status: running
Feb 11 21:54:58 helix pleroma[3007]: heap_size: 610
Feb 11 21:54:58 helix pleroma[3007]: stack_size: 28
Feb 11 21:54:58 helix pleroma[3007]: reductions: 213
Feb 11 21:54:58 helix pleroma[3007]: neighbours:
Feb 11 21:54:58 helix pleroma[3007]:
Feb 11 21:54:59 helix pleroma[3007]: =CRASH REPORT==== 11-Feb-2023::21:54:59.412397 ===
Feb 11 21:54:59 helix pleroma[3007]: crasher:
Feb 11 21:54:59 helix pleroma[3007]: initial call: application_master:init/4
Feb 11 21:54:59 helix pleroma[3007]: pid: <0.3557.0>
Feb 11 21:54:59 helix pleroma[3007]: registered_name: []
Feb 11 21:54:59 helix pleroma[3007]: exception exit: {{shutdown,
Feb 11 21:54:59 helix pleroma[3007]: {failed_to_start_child,kernel_safe_sup,
Feb 11 21:54:59 helix pleroma[3007]: {on_load_function_failed,crypt,
Feb 11 21:54:59 helix pleroma[3007]: {error,
Feb 11 21:54:59 helix pleroma[3007]: {load_failed,
Feb 11 21:54:59 helix pleroma[3007]: "Failed to load NIF library: '/opt/pleroma/lib/crypt-0.4.3/priv/crypt.so: undefined symbol: crypt'"}}}}},
Feb 11 21:54:59 helix pleroma[3007]: {kernel,start,[normal,[]]}}
Feb 11 21:54:59 helix pleroma[3007]: in function application_master:init/4 (application_master.erl, line 142)
Feb 11 21:54:59 helix pleroma[3007]: ancestors: [<0.3556.0>]
Feb 11 21:54:59 helix pleroma[3007]: message_queue_len: 1
Feb 11 21:54:59 helix pleroma[3007]: messages: [{'EXIT',<0.3558.0>,normal}]
Feb 11 21:54:59 helix pleroma[3007]: links: [<0.3556.0>,<0.3555.0>]
Feb 11 21:54:59 helix pleroma[3007]: dictionary: []
Feb 11 21:54:59 helix pleroma[3007]: trap_exit: true
Feb 11 21:54:59 helix pleroma[3007]: status: running
Feb 11 21:54:59 helix pleroma[3007]: heap_size: 987
Feb 11 21:54:59 helix pleroma[3007]: stack_size: 28
Feb 11 21:54:59 helix pleroma[3007]: reductions: 182
Feb 11 21:54:59 helix pleroma[3007]: neighbours:
Feb 11 21:54:59 helix pleroma[3007]:
Feb 11 21:54:59 helix pleroma[3007]: =INFO REPORT==== 11-Feb-2023::21:54:59.415243 ===
Feb 11 21:54:59 helix pleroma[3007]: application: kernel
Feb 11 21:54:59 helix pleroma[3007]: exited: {{shutdown,
Feb 11 21:54:59 helix pleroma[3007]: {failed_to_start_child,kernel_safe_sup,
Feb 11 21:54:59 helix pleroma[3007]: {on_load_function_failed,crypt,
Feb 11 21:54:59 helix pleroma[3007]: {error,
Feb 11 21:54:59 helix pleroma[3007]: {load_failed,
Feb 11 21:54:59 helix pleroma[3007]: "Failed to load NIF library: '/opt/pleroma/lib/crypt-0.4.3/priv/crypt.so: undefined symbol: crypt'"}}}}},
Feb 11 21:54:59 helix pleroma[3007]: {kernel,start,[normal,[]]}}
Feb 11 21:54:59 helix pleroma[3007]: type: permanent
Feb 11 21:54:59 helix pleroma[3007]:
Feb 11 21:54:59 helix pleroma[3007]: {"Kernel pid terminated",application_controller,"{application_start_failure,kernel,{{shutdown,{failed_to_start_child,kernel_safe_sup,{on_load_function_failed,crypt,{error,{load_failed,\"Failed to load NIF library: '/opt/pleroma/lib/crypt-0.4.3/priv/crypt.so: undefined symbol: crypt'\"}}}}},{kernel,start,[normal,[]]}}}"}
Feb 11 21:54:59 helix pleroma[3007]: Kernel pid terminated (application_controller) ({application_start_failure,kernel,{{shutdown,{failed_to_start_child,kernel_safe_sup,{on_load_function_failed,crypt,{error,{load_failed,"Failed to load NIF library: '/opt/pleroma/lib/crypt-0.4.3/priv/crypt.so: undefined symbol: crypt'"}}}}},{kernel,start,[normal,[]]}}})
Feb 11 21:54:59 helix pleroma[3007]:
Feb 11 21:55:00 helix pleroma[3007]: Crash dump is being written to: erl_crash.dump...done
Feb 11 21:55:00 helix systemd[1]: pleroma.service: Main process exited, code=exited, status=1/FAILURE
Feb 11 21:55:00 helix systemd[1]: pleroma.service: Failed with result 'exit-code'.
Feb 11 21:55:00 helix systemd[1]: pleroma.service: Unit process 450 (epmd) remains running after unit stopped.
Feb 11 21:55:00 helix systemd[1]: Stopped Pleroma social network.
Feb 11 21:55:00 helix systemd[1]: pleroma.service: Consumed 5.701s CPU time.
```
</details>
I even try to mv official OTP crypt.so to this path, the log is here with web 502
<details>
```
Feb 11 21:57:59 helix systemd[1]: Started Pleroma social network.
Feb 11 21:58:02 helix pleroma[3517]: [notice] :alarm_handler: {:set, {:system_memory_high_watermark, []}}
Feb 11 21:58:03 helix pleroma[3517]: [info] Function passed as a handler with ID "pleroma-logger" is local function.
Feb 11 21:58:03 helix pleroma[3517]: This mean that it is either anonymous function or capture of function without module specified. That may cause performance penalty when calling such handler. For more details see note in `telemetry:attach/4` documentation.
Feb 11 21:58:03 helix pleroma[3517]: https://hexdocs.pm/telemetry/telemetry.html#attach-4
Feb 11 21:58:03 helix pleroma[3517]: [debug] QUERY OK source="columns" db=6.6ms queue=8.2ms idle=0.0ms
Feb 11 21:58:03 helix pleroma[3517]: SELECT TRUE FROM "information_schema"."columns" AS c0 WHERE (c0."table_name" = 'objects') AND (c0."column_name" = 'fts_content') LIMIT 1 []
Feb 11 21:58:03 helix pleroma[3517]: [info] Function passed as a handler with ID "telemetry_web__event_handler" is local function.
Feb 11 21:58:03 helix pleroma[3517]: This mean that it is either anonymous function or capture of function without module specified. That may cause performance penalty when calling such handler. For more details see note in `telemetry:attach/4` documentation.
Feb 11 21:58:03 helix pleroma[3517]: https://hexdocs.pm/telemetry/telemetry.html#attach-4
Feb 11 21:58:03 helix pleroma[3517]: [debug] Elixir.Pleroma.Web.ActivityPub.MRF.MediaProxyWarmingPolicy is excluded from config descriptions, because does not implement `config_description/0` method.
Feb 11 21:58:03 helix pleroma[3517]: [debug] Elixir.Pleroma.Web.ActivityPub.MRF.ForceMentionsInContent is excluded from config descriptions, because does not implement `config_description/0` method.
Feb 11 21:58:03 helix pleroma[3517]: [debug] Elixir.Pleroma.Web.ActivityPub.MRF.DropPolicy is excluded from config descriptions, because does not implement `config_description/0` method.
Feb 11 21:58:03 helix pleroma[3517]: [debug] Elixir.Pleroma.Web.ActivityPub.MRF.TagPolicy is excluded from config descriptions, because does not implement `config_description/0` method.
Feb 11 21:58:03 helix pleroma[3517]: [debug] Elixir.Pleroma.Web.ActivityPub.MRF.NoPlaceholderTextPolicy is excluded from config descriptions, because does not implement `config_description/0` method.
Feb 11 21:58:03 helix pleroma[3517]: [debug] Elixir.Pleroma.Web.ActivityPub.MRF.ForceBotUnlistedPolicy is excluded from config descriptions, because does not implement `config_description/0` method.
Feb 11 21:58:03 helix pleroma[3517]: [debug] Elixir.Pleroma.Web.ActivityPub.MRF.EnsureRePrepended is excluded from config descriptions, because does not implement `config_description/0` method.
Feb 11 21:58:03 helix pleroma[3517]: [debug] Elixir.Pleroma.Web.ActivityPub.MRF.AntiLinkSpamPolicy is excluded from config descriptions, because does not implement `config_description/0` method.
Feb 11 21:58:03 helix pleroma[3517]: [debug] Elixir.Pleroma.Web.ActivityPub.MRF.AntiFollowbotPolicy is excluded from config descriptions, because does not implement `config_description/0` method.
Feb 11 21:58:03 helix pleroma[3517]: [debug] Elixir.Pleroma.Web.ActivityPub.MRF.FollowBotPolicy is excluded from config descriptions, because does not implement `config_description/0` method.
Feb 11 21:58:03 helix pleroma[3517]: [debug] Elixir.Pleroma.Web.ActivityPub.MRF.NoEmptyPolicy is excluded from config descriptions, because does not implement `config_description/0` method.
Feb 11 21:58:03 helix pleroma[3517]: [debug] Elixir.Pleroma.Web.ActivityPub.MRF.UserAllowListPolicy is excluded from config descriptions, because does not implement `config_description/0` method.
Feb 11 21:58:03 helix pleroma[3517]: [debug] Elixir.Pleroma.Web.ActivityPub.MRF.NoOpPolicy is excluded from config descriptions, because does not implement `config_description/0` method.
Feb 11 21:58:03 helix pleroma[3517]: [debug] QUERY OK source="config" db=6.0ms queue=28.0ms idle=0.0ms
Feb 11 21:58:03 helix pleroma[3517]: SELECT c0."id", c0."key", c0."group", c0."value", c0."inserted_at", c0."updated_at" FROM "config" AS c0 []
Feb 11 21:58:03 helix pleroma[3517]: [info] Function passed as a handler with ID "oban-monitor-failure" is local function.
Feb 11 21:58:03 helix pleroma[3517]: This mean that it is either anonymous function or capture of function without module specified. That may cause performance penalty when calling such handler. For more details see note in `telemetry:attach/4` documentation.
Feb 11 21:58:03 helix pleroma[3517]: https://hexdocs.pm/telemetry/telemetry.html#attach-4
Feb 11 21:58:03 helix pleroma[3517]: [info] Function passed as a handler with ID "oban-monitor-success" is local function.
Feb 11 21:58:03 helix pleroma[3517]: This mean that it is either anonymous function or capture of function without module specified. That may cause performance penalty when calling such handler. For more details see note in `telemetry:attach/4` documentation.
Feb 11 21:58:03 helix pleroma[3517]: https://hexdocs.pm/telemetry/telemetry.html#attach-4
Feb 11 21:58:03 helix pleroma[3517]: [debug] QUERY OK source="data_migrations" db=0.8ms queue=1.3ms idle=45.2ms
Feb 11 21:58:03 helix pleroma[3517]: SELECT d0."id", d0."name", d0."state", d0."feature_lock", d0."params", d0."data", d0."inserted_at", d0."updated_at" FROM "data_migrations" AS d0 WHERE (d0."name" = $1) ["populate_hashtags_table"]
Feb 11 21:58:03 helix pleroma[3517]: [info] Gopher server disabled
Feb 11 21:58:03 helix pleroma[3517]: [debug] QUERY OK db=0.2ms queue=0.3ms idle=44.1ms
Feb 11 21:58:03 helix pleroma[3517]: show server_version []
Feb 11 21:58:03 helix pleroma[3517]: [debug] QUERY OK source="data_migrations" db=2.5ms queue=2.5ms idle=42.8ms
Feb 11 21:58:03 helix pleroma[3517]: SELECT d0."id", d0."name", d0."state", d0."feature_lock", d0."params", d0."data", d0."inserted_at", d0."updated_at" FROM "data_migrations" AS d0 WHERE (d0."name" = $1) ["delete_context_objects"]
Feb 11 21:58:03 helix pleroma[3517]: [debug] QUERY OK source="data_migrations" db=1.8ms queue=0.3ms idle=44.2ms
Feb 11 21:58:03 helix pleroma[3517]: SELECT d0."id", d0."name", d0."state", d0."feature_lock", d0."params", d0."data", d0."inserted_at", d0."updated_at" FROM "data_migrations" AS d0 WHERE (d0."name" = $1) ["delete_context_objects"]
Feb 11 21:58:03 helix pleroma[3517]: [debug] QUERY OK source="data_migrations" db=5.2ms queue=0.5ms idle=44.5ms
Feb 11 21:58:03 helix pleroma[3517]: SELECT d0."id", d0."name", d0."state", d0."feature_lock", d0."params", d0."data", d0."inserted_at", d0."updated_at" FROM "data_migrations" AS d0 WHERE (d0."name" = $1) ["populate_hashtags_table"]
Feb 11 21:58:04 helix pleroma[3517]: [debug] QUERY OK source="users" db=469.7ms decode=0.2ms queue=1.9ms idle=24.7ms
Feb 11 21:58:04 helix pleroma[3517]: SELECT distinct split_part(u0."nickname", '@', 2) FROM "users" AS u0 WHERE (u0."local" != $1) [true]
Feb 11 21:58:04 helix pleroma[3517]: [debug] QUERY OK source="users" db=7.1ms queue=1.9ms idle=486.4ms
Feb 11 21:58:04 helix pleroma[3517]: SELECT sum(u0."note_count") FROM "users" AS u0 WHERE (NOT (u0."nickname" IS NULL)) AND (NOT (u0."nickname" LIKE 'internal.%')) AND (u0."local" = $1) [true]
Feb 11 21:58:04 helix pleroma[3517]: [debug] QUERY OK source="users" db=2.3ms queue=1.1ms idle=494.4ms
Feb 11 21:58:04 helix pleroma[3517]: SELECT count(u0."id") FROM "users" AS u0 WHERE (u0."is_active" = TRUE) AND (u0."local" = TRUE) AND (NOT (u0."nickname" IS NULL)) AND (NOT (u0."invisible")) []
Feb 11 21:58:08 helix pleroma[3517]: [debug] QUERY OK source="users" db=95.5ms queue=1.2ms idle=1068.6ms
Feb 11 21:58:08 helix pleroma[3517]: SELECT u0."id", u0."bio", u0."raw_bio", u0."email", u0."name", u0."nickname", u0."password_hash", u0."keys", u0."public_key", u0."ap_id", u0."avatar", u0."local", u0."follower_address", u0."following_address", u0."featured_address", u0."tags", u0."last_refreshed_at", u0."last_digest_emailed_at", u0."banner", u0."background", u0."note_count", u0."follower_count", u0."following_count", u0."is_locked", u0."is_confirmed", u0."password_reset_pending", u0."is_approved", u0."registration_reason", u0."confirmation_token", u0."default_scope", u0."domain_blocks", u0."is_active", u0."no_rich_text", u0."ap_enabled", u0."is_moderator", u0."is_admin", u0."show_role", u0."uri", u0."hide_followers_count", u0."hide_follows_count", u0."hide_followers", u0."hide_follows", u0."hide_favorites", u0."email_notifications", u0."mascot", u0."emoji", u0."pleroma_settings_store", u0."fields", u0."raw_fields", u0."is_discoverable", u0."invisible", u0."allow_following_move", u0."skip_thread_containment", u0."actor_type", u0."also_known_as", u0."inbox", u0."shared_inbox", u0."accepts_chat_messages", u0."last_active_at", u0."disclose_client", u0."pinned_objects", u0."is_suggested", u0."last_status_at", u0."birthday", u0."show_birthday", u0."language", u0."notification_settings", u0."blocks", u0."mutes", u0."muted_reblogs", u0."muted_notifications", u0."subscribers", u0."multi_factor_authentication_settings", u0."inserted_at", u0."updated_at" FROM "users" AS u0 WHERE (u0."ap_id" = $1) ["https://social.malacology.net/internal/fetch"]
Feb 11 21:59:04 helix pleroma[3517]: [debug] QUERY OK source="users" db=418.4ms queue=0.1ms idle=888.4ms
Feb 11 21:59:04 helix pleroma[3517]: SELECT distinct split_part(u0."nickname", '@', 2) FROM "users" AS u0 WHERE (u0."local" != $1) [true]
Feb 11 21:59:04 helix pleroma[3517]: [debug] QUERY OK source="users" db=5.3ms idle=952.2ms
Feb 11 21:59:04 helix pleroma[3517]: SELECT sum(u0."note_count") FROM "users" AS u0 WHERE (NOT (u0."nickname" IS NULL)) AND (NOT (u0."nickname" LIKE 'internal.%')) AND (u0."local" = $1) [true]
Feb 11 21:59:04 helix pleroma[3517]: [debug] QUERY OK source="users" db=2.4ms idle=957.8ms
Feb 11 21:59:04 helix pleroma[3517]: SELECT count(u0."id") FROM "users" AS u0 WHERE (u0."is_active" = TRUE) AND (u0."local" = TRUE) AND (NOT (u0."nickname" IS NULL)) AND (NOT (u0."invisible")) []
Feb 11 22:00:05 helix pleroma[3517]: [debug] QUERY OK source="users" db=428.4ms idle=1960.1ms
Feb 11 22:00:05 helix pleroma[3517]: SELECT distinct split_part(u0."nickname", '@', 2) FROM "users" AS u0 WHERE (u0."local" != $1) [true]
Feb 11 22:00:05 helix pleroma[3517]: [debug] QUERY OK source="users" db=3.0ms idle=1390.0ms
Feb 11 22:00:05 helix pleroma[3517]: SELECT sum(u0."note_count") FROM "users" AS u0 WHERE (NOT (u0."nickname" IS NULL)) AND (NOT (u0."nickname" LIKE 'internal.%')) AND (u0."local" = $1) [true]
Feb 11 22:00:05 helix pleroma[3517]: [debug] QUERY OK source="users" db=2.8ms idle=1393.2ms
Feb 11 22:00:05 helix pleroma[3517]: SELECT count(u0."id") FROM "users" AS u0 WHERE (u0."is_active" = TRUE) AND (u0."local" = TRUE) AND (NOT (u0."nickname" IS NULL)) AND (NOT (u0."invisible")) []
Feb 11 22:01:05 helix pleroma[3517]: [debug] QUERY OK source="users" db=411.1ms decode=0.2ms idle=1397.9ms
Feb 11 22:01:05 helix pleroma[3517]: SELECT distinct split_part(u0."nickname", '@', 2) FROM "users" AS u0 WHERE (u0."local" != $1) [true]
Feb 11 22:01:05 helix pleroma[3517]: [debug] QUERY OK source="users" db=4.9ms idle=1810.6ms
Feb 11 22:01:05 helix pleroma[3517]: SELECT sum(u0."note_count") FROM "users" AS u0 WHERE (NOT (u0."nickname" IS NULL)) AND (NOT (u0."nickname" LIKE 'internal.%')) AND (u0."local" = $1) [true]
Feb 11 22:01:05 helix pleroma[3517]: [debug] QUERY OK source="users" db=2.6ms queue=0.1ms idle=1815.7ms
Feb 11 22:01:05 helix pleroma[3517]: SELECT count(u0."id") FROM "users" AS u0 WHERE (u0."is_active" = TRUE) AND (u0."local" = TRUE) AND (NOT (u0."nickname" IS NULL)) AND (NOT (u0."invisible")) []
Feb 11 22:02:05 helix pleroma[3517]: [debug] QUERY OK source="users" db=457.2ms queue=0.2ms idle=1818.0ms
Feb 11 22:02:05 helix pleroma[3517]: SELECT distinct split_part(u0."nickname", '@', 2) FROM "users" AS u0 WHERE (u0."local" != $1) [true]
Feb 11 22:02:05 helix pleroma[3517]: [debug] QUERY OK source="users" db=3.1ms idle=1278.5ms
Feb 11 22:02:05 helix pleroma[3517]: SELECT sum(u0."note_count") FROM "users" AS u0 WHERE (NOT (u0."nickname" IS NULL)) AND (NOT (u0."nickname" LIKE 'internal.%')) AND (u0."local" = $1) [true]
Feb 11 22:02:05 helix pleroma[3517]: [debug] QUERY OK source="users" db=1.3ms idle=1210.7ms
Feb 11 22:02:05 helix pleroma[3517]: SELECT count(u0."id") FROM "users" AS u0 WHERE (u0."is_active" = TRUE) AND (u0."local" = TRUE) AND (NOT (u0."nickname" IS NULL)) AND (NOT (u0."invisible")) []
Feb 11 22:03:06 helix pleroma[3517]: [debug] QUERY OK source="users" db=407.3ms queue=0.1ms idle=957.8ms
Feb 11 22:03:06 helix pleroma[3517]: SELECT distinct split_part(u0."nickname", '@', 2) FROM "users" AS u0 WHERE (u0."local" != $1) [true]
Feb 11 22:03:06 helix pleroma[3517]: [debug] QUERY OK source="users" db=2.8ms idle=691.6ms
Feb 11 22:03:06 helix pleroma[3517]: SELECT sum(u0."note_count") FROM "users" AS u0 WHERE (NOT (u0."nickname" IS NULL)) AND (NOT (u0."nickname" LIKE 'internal.%')) AND (u0."local" = $1) [true]
Feb 11 22:03:06 helix pleroma[3517]: [debug] QUERY OK source="users" db=0.6ms idle=694.4ms
Feb 11 22:03:06 helix pleroma[3517]: SELECT count(u0."id") FROM "users" AS u0 WHERE (u0."is_active" = TRUE) AND (u0."local" = TRUE) AND (NOT (u0."nickname" IS NULL)) AND (NOT (u0."invisible")) []
Feb 11 22:04:06 helix pleroma[3517]: [debug] QUERY OK source="users" db=477.1ms idle=695.7ms
Feb 11 22:04:06 helix pleroma[3517]: SELECT distinct split_part(u0."nickname", '@', 2) FROM "users" AS u0 WHERE (u0."local" != $1) [true]
Feb 11 22:04:06 helix pleroma[3517]: [debug] QUERY OK source="users" db=3.3ms queue=0.2ms idle=1174.4ms
Feb 11 22:04:06 helix pleroma[3517]: SELECT sum(u0."note_count") FROM "users" AS u0 WHERE (NOT (u0."nickname" IS NULL)) AND (NOT (u0."nickname" LIKE 'internal.%')) AND (u0."local" = $1) [true]
Feb 11 22:04:06 helix pleroma[3517]: [debug] QUERY OK source="users" db=1.3ms queue=0.1ms idle=1177.9ms
Feb 11 22:04:06 helix pleroma[3517]: SELECT count(u0."id") FROM "users" AS u0 WHERE (u0."is_active" = TRUE) AND (u0."local" = TRUE) AND (NOT (u0."nickname" IS NULL)) AND (NOT (u0."invisible")) []
Feb 11 22:05:07 helix pleroma[3517]: [debug] QUERY OK source="users" db=412.5ms queue=0.1ms idle=1180.5ms
Feb 11 22:05:07 helix pleroma[3517]: SELECT distinct split_part(u0."nickname", '@', 2) FROM "users" AS u0 WHERE (u0."local" != $1) [true]
Feb 11 22:05:07 helix pleroma[3517]: [debug] QUERY OK source="users" db=1.1ms idle=1595.5ms
Feb 11 22:05:07 helix pleroma[3517]: SELECT sum(u0."note_count") FROM "users" AS u0 WHERE (NOT (u0."nickname" IS NULL)) AND (NOT (u0."nickname" LIKE 'internal.%')) AND (u0."local" = $1) [true]
Feb 11 22:05:07 helix pleroma[3517]: [debug] QUERY OK source="users" db=0.9ms idle=1596.8ms
Feb 11 22:05:07 helix pleroma[3517]: SELECT count(u0."id") FROM "users" AS u0 WHERE (u0."is_active" = TRUE) AND (u0."local" = TRUE) AND (NOT (u0."nickname" IS NULL)) AND (NOT (u0."invisible")) []
Feb 11 22:06:07 helix pleroma[3517]: [debug] QUERY OK source="users" db=733.7ms decode=0.1ms queue=0.1ms idle=1594.2ms
Feb 11 22:06:07 helix pleroma[3517]: SELECT distinct split_part(u0."nickname", '@', 2) FROM "users" AS u0 WHERE (u0."local" != $1) [true]
Feb 11 22:06:07 helix pleroma[3517]: [debug] QUERY OK source="users" db=1.3ms idle=1329.9ms
Feb 11 22:06:07 helix pleroma[3517]: SELECT sum(u0."note_count") FROM "users" AS u0 WHERE (NOT (u0."nickname" IS NULL)) AND (NOT (u0."nickname" LIKE 'internal.%')) AND (u0."local" = $1) [true]
Feb 11 22:06:07 helix pleroma[3517]: [debug] QUERY OK source="users" db=0.9ms idle=1331.5ms
Feb 11 22:06:07 helix pleroma[3517]: SELECT count(u0."id") FROM "users" AS u0 WHERE (u0."is_active" = TRUE) AND (u0."local" = TRUE) AND (NOT (u0."nickname" IS NULL)) AND (NOT (u0."invisible")) []
Feb 11 22:07:08 helix pleroma[3517]: [debug] QUERY OK source="users" db=417.2ms queue=0.1ms idle=1333.6ms
Feb 11 22:07:08 helix pleroma[3517]: SELECT distinct split_part(u0."nickname", '@', 2) FROM "users" AS u0 WHERE (u0."local" != $1) [true]
Feb 11 22:07:08 helix pleroma[3517]: [debug] QUERY OK source="users" db=1.3ms idle=1752.4ms
Feb 11 22:07:08 helix pleroma[3517]: SELECT sum(u0."note_count") FROM "users" AS u0 WHERE (NOT (u0."nickname" IS NULL)) AND (NOT (u0."nickname" LIKE 'internal.%')) AND (u0."local" = $1) [true]
Feb 11 22:07:08 helix pleroma[3517]: [debug] QUERY OK source="users" db=1.1ms idle=1753.9ms
Feb 11 22:07:08 helix pleroma[3517]: SELECT count(u0."id") FROM "users" AS u0 WHERE (u0."is_active" = TRUE) AND (u0."local" = TRUE) AND (NOT (u0."nickname" IS NULL)) AND (NOT (u0."invisible")) []
Feb 11 22:08:08 helix pleroma[3517]: [debug] QUERY OK source="users" db=414.1ms idle=1754.7ms
Feb 11 22:08:08 helix pleroma[3517]: SELECT distinct split_part(u0."nickname", '@', 2) FROM "users" AS u0 WHERE (u0."local" != $1) [true]
Feb 11 22:08:08 helix pleroma[3517]: [debug] QUERY OK source="users" db=3.2ms idle=1170.9ms
Feb 11 22:08:08 helix pleroma[3517]: SELECT sum(u0."note_count") FROM "users" AS u0 WHERE (NOT (u0."nickname" IS NULL)) AND (NOT (u0."nickname" LIKE 'internal.%')) AND (u0."local" = $1) [true]
Feb 11 22:08:08 helix pleroma[3517]: [debug] QUERY OK source="users" db=1.3ms idle=1174.4ms
Feb 11 22:08:08 helix pleroma[3517]: SELECT count(u0."id") FROM "users" AS u0 WHERE (u0."is_active" = TRUE) AND (u0."local" = TRUE) AND (NOT (u0."nickname" IS NULL)) AND (NOT (u0."invisible")) []
Feb 11 22:09:09 helix pleroma[3517]: [debug] QUERY OK source="users" db=459.7ms idle=1175.7ms
Feb 11 22:09:09 helix pleroma[3517]: SELECT distinct split_part(u0."nickname", '@', 2) FROM "users" AS u0 WHERE (u0."local" != $1) [true]
Feb 11 22:09:09 helix pleroma[3517]: [debug] QUERY OK source="users" db=1.4ms queue=0.1ms idle=1636.6ms
Feb 11 22:09:09 helix pleroma[3517]: SELECT sum(u0."note_count") FROM "users" AS u0 WHERE (NOT (u0."nickname" IS NULL)) AND (NOT (u0."nickname" LIKE 'internal.%')) AND (u0."local" = $1) [true]
Feb 11 22:09:09 helix pleroma[3517]: [debug] QUERY OK source="users" db=1.2ms idle=1638.2ms
Feb 11 22:09:09 helix pleroma[3517]: SELECT count(u0."id") FROM "users" AS u0 WHERE (u0."is_active" = TRUE) AND (u0."local" = TRUE) AND (NOT (u0."nickname" IS NULL)) AND (NOT (u0."invisible")) []
Feb 11 22:10:09 helix pleroma[3517]: [debug] QUERY OK source="users" db=413.7ms decode=1.1ms queue=0.1ms idle=1453.2ms
Feb 11 22:10:09 helix pleroma[3517]: SELECT distinct split_part(u0."nickname", '@', 2) FROM "users" AS u0 WHERE (u0."local" != $1) [true]
Feb 11 22:10:09 helix pleroma[3517]: [debug] QUERY OK source="users" db=1.7ms idle=1056.5ms
Feb 11 22:10:09 helix pleroma[3517]: SELECT sum(u0."note_count") FROM "users" AS u0 WHERE (NOT (u0."nickname" IS NULL)) AND (NOT (u0."nickname" LIKE 'internal.%')) AND (u0."local" = $1) [true]
Feb 11 22:10:09 helix pleroma[3517]: [debug] QUERY OK source="users" db=0.9ms idle=1058.5ms
Feb 11 22:10:09 helix pleroma[3517]: SELECT count(u0."id") FROM "users" AS u0 WHERE (u0."is_active" = TRUE) AND (u0."local" = TRUE) AND (NOT (u0."nickname" IS NULL)) AND (NOT (u0."invisible")) []
Feb 11 22:11:10 helix pleroma[3517]: [debug] QUERY OK source="users" db=405.9ms queue=0.1ms idle=1060.6ms
Feb 11 22:11:10 helix pleroma[3517]: SELECT distinct split_part(u0."nickname", '@', 2) FROM "users" AS u0 WHERE (u0."local" != $1) [true]
Feb 11 22:11:10 helix pleroma[3517]: [debug] QUERY OK source="users" db=2.0ms idle=1468.7ms
Feb 11 22:11:10 helix pleroma[3517]: SELECT sum(u0."note_count") FROM "users" AS u0 WHERE (NOT (u0."nickname" IS NULL)) AND (NOT (u0."nickname" LIKE 'internal.%')) AND (u0."local" = $1) [true]
Feb 11 22:11:10 helix pleroma[3517]: [debug] QUERY OK source="users" db=1.0ms idle=1470.9ms
Feb 11 22:11:10 helix pleroma[3517]: SELECT count(u0."id") FROM "users" AS u0 WHERE (u0."is_active" = TRUE) AND (u0."local" = TRUE) AND (NOT (u0."nickname" IS NULL)) AND (NOT (u0."invisible")) []
Feb 11 22:12:10 helix pleroma[3517]: [debug] QUERY OK source="users" db=431.1ms decode=0.1ms queue=0.1ms idle=1472.4ms
Feb 11 22:12:10 helix pleroma[3517]: SELECT distinct split_part(u0."nickname", '@', 2) FROM "users" AS u0 WHERE (u0."local" != $1) [true]
Feb 11 22:12:10 helix pleroma[3517]: [debug] QUERY OK source="users" db=3.3ms idle=1905.6ms
Feb 11 22:12:10 helix pleroma[3517]: SELECT sum(u0."note_count") FROM "users" AS u0 WHERE (NOT (u0."nickname" IS NULL)) AND (NOT (u0."nickname" LIKE 'internal.%')) AND (u0."local" = $1) [true]
Feb 11 22:12:10 helix pleroma[3517]: [debug] QUERY OK source="users" db=0.9ms idle=1909.2ms
Feb 11 22:12:10 helix pleroma[3517]: SELECT count(u0."id") FROM "users" AS u0 WHERE (u0."is_active" = TRUE) AND (u0."local" = TRUE) AND (NOT (u0."nickname" IS NULL)) AND (NOT (u0."invisible")) []
Feb 11 22:13:10 helix pleroma[3517]: [debug] QUERY OK source="users" db=411.0ms queue=0.3ms idle=1911.6ms
Feb 11 22:13:10 helix pleroma[3517]: SELECT distinct split_part(u0."nickname", '@', 2) FROM "users" AS u0 WHERE (u0."local" != $1) [true]
Feb 11 22:13:10 helix pleroma[3517]: [debug] QUERY OK source="users" db=1.7ms idle=1324.4ms
Feb 11 22:13:10 helix pleroma[3517]: SELECT sum(u0."note_count") FROM "users" AS u0 WHERE (NOT (u0."nickname" IS NULL)) AND (NOT (u0."nickname" LIKE 'internal.%')) AND (u0."local" = $1) [true]
Feb 11 22:13:10 helix pleroma[3517]: [debug] QUERY OK source="users" db=0.9ms idle=1326.3ms
Feb 11 22:13:10 helix pleroma[3517]: SELECT count(u0."id") FROM "users" AS u0 WHERE (u0."is_active" = TRUE) AND (u0."local" = TRUE) AND (NOT (u0."nickname" IS NULL)) AND (NOT (u0."invisible")) []
Feb 11 22:14:11 helix pleroma[3517]: [debug] QUERY OK source="users" db=404.2ms idle=1328.0ms
Feb 11 22:14:11 helix pleroma[3517]: SELECT distinct split_part(u0."nickname", '@', 2) FROM "users" AS u0 WHERE (u0."local" != $1) [true]
Feb 11 22:14:11 helix pleroma[3517]: [debug] QUERY OK source="users" db=1.1ms queue=0.1ms idle=1733.6ms
Feb 11 22:14:11 helix pleroma[3517]: SELECT sum(u0."note_count") FROM "users" AS u0 WHERE (NOT (u0."nickname" IS NULL)) AND (NOT (u0."nickname" LIKE 'internal.%')) AND (u0."local" = $1) [true]
Feb 11 22:14:11 helix pleroma[3517]: [debug] QUERY OK source="users" db=0.9ms idle=1735.0ms
Feb 11 22:14:11 helix pleroma[3517]: SELECT count(u0."id") FROM "users" AS u0 WHERE (u0."is_active" = TRUE) AND (u0."local" = TRUE) AND (NOT (u0."nickname" IS NULL)) AND (NOT (u0."invisible")) []
Feb 11 22:15:11 helix pleroma[3517]: [debug] QUERY OK source="users" db=433.1ms idle=1737.3ms
Feb 11 22:15:11 helix pleroma[3517]: SELECT distinct split_part(u0."nickname", '@', 2) FROM "users" AS u0 WHERE (u0."local" != $1) [true]
Feb 11 22:15:11 helix pleroma[3517]: [debug] QUERY OK source="users" db=1.0ms idle=1171.8ms
Feb 11 22:15:11 helix pleroma[3517]: SELECT sum(u0."note_count") FROM "users" AS u0 WHERE (NOT (u0."nickname" IS NULL)) AND (NOT (u0."nickname" LIKE 'internal.%')) AND (u0."local" = $1) [true]
Feb 11 22:15:11 helix pleroma[3517]: [debug] QUERY OK source="users" db=0.8ms queue=0.2ms idle=1173.0ms
Feb 11 22:15:11 helix pleroma[3517]: SELECT count(u0."id") FROM "users" AS u0 WHERE (u0."is_active" = TRUE) AND (u0."local" = TRUE) AND (NOT (u0."nickname" IS NULL)) AND (NOT (u0."invisible")) []
Feb 11 22:16:02 helix systemd[1]: Stopping Pleroma social network...
Feb 11 22:16:03 helix pleroma[3517]: [notice] SIGTERM received - shutting down
Feb 11 22:16:03 helix pleroma[3580]: [os_mon] memory supervisor port (memsup): Erlang has closed
Feb 11 22:16:03 helix pleroma[3517]: [notice] :alarm_handler: {:clear, :system_memory_high_watermark}
Feb 11 22:16:03 helix pleroma[3581]: [os_mon] cpu supervisor port (cpu_sup): Erlang has closed
Feb 11 22:16:17 helix systemd[1]: pleroma.service: Deactivated successfully.
Feb 11 22:16:17 helix systemd[1]: pleroma.service: Unit process 3549 (epmd) remains running after unit stopped.
Feb 11 22:16:17 helix systemd[1]: Stopped Pleroma social network.
Feb 11 22:16:17 helix systemd[1]: pleroma.service: Consumed 26.472s CPU time.
```
</details>https://git.pleroma.social/pleroma/pleroma/-/issues/3061ActivityPub C2S: Replies for an Activity are not returned2023-02-20T22:24:50ZGuilherme DellagustinActivityPub C2S: Replies for an Activity are not returned<!--
### Precheck
* For support use https://git.pleroma.social/pleroma/pleroma-support or [community channels](https://git.pleroma.social/pleroma/pleroma#community-channels).
* Please do a quick search to ensure no similar bug has been ...<!--
### Precheck
* For support use https://git.pleroma.social/pleroma/pleroma-support or [community channels](https://git.pleroma.social/pleroma/pleroma#community-channels).
* Please do a quick search to ensure no similar bug has been reported before. If the bug has not been addressed after 2 weeks, it's fine to bump it.
* Try to ensure that the bug is actually related to the Pleroma backend. For example, if a bug happens in Pleroma-FE but not in Mastodon-FE or mobile clients, it's likely that the bug should be filed in [Pleroma-FE](https://git.pleroma.social/pleroma/pleroma-fe/issues/new) repository.
-->
### Environment
* Installation type (OTP or From Source):
* Pleroma version (could be found in the "Version" tab of settings in Pleroma-FE):
* Elixir version (`elixir -v` for from source installations, N/A for OTP):
* Operating system:
* PostgreSQL version (`psql -V`):
I can't fill those, as I am not running the servers, only consuming their API
### Bug description
If I fetch the data for a message using ActivityPub, it does not bring back replies.
I tested with https://blob.cat/objects/246b71cf-3f03-4ba1-b996-58711c031abf, it comes back with an empty `replies` array, and two different properties for replies count:
```
"replies": [],
"repliesCount": 2,
"replies_count": 0,
```
I tested with https://cawfee.club/objects/0c120201-3242-4739-af62-3f846ccbc56d, it comes back with no `replies` property and a single `repliesCount`.https://git.pleroma.social/pleroma/pleroma/-/issues/3060Reply filter broken on Home timeline after fetching new posts (with streaming...2023-05-02T12:30:54ZLady GagaReply filter broken on Home timeline after fetching new posts (with streaming API enabled only)I run the latest develop branch
How to replicate:
-Set reply filter to "follows only" or "self".
-At first, it works correctly after the initial page load or refresh
-Wait for new posts to fetch.
-Click "Show New"
-New posts...I run the latest develop branch
How to replicate:
-Set reply filter to "follows only" or "self".
-At first, it works correctly after the initial page load or refresh
-Wait for new posts to fetch.
-Click "Show New"
-New posts will show all replies, ignoring the filter
This only seems to be the case on the Home timelinehttps://git.pleroma.social/pleroma/pleroma/-/issues/3059Report content incorrectly cached2023-02-09T19:52:04ZtusooaReport content incorrectly cachedThe activity id is always rendered as "pleroma:fake" so it's messing up with the cache. Should use the ap id as clue.The activity id is always rendered as "pleroma:fake" so it's messing up with the cache. Should use the ap id as clue.https://git.pleroma.social/pleroma/pleroma/-/issues/3058v2.5.0 ecto.migrate error: function associated_object_id(jsonb) does not exist2023-01-26T02:11:10ZNyx Landv2.5.0 ecto.migrate error: function associated_object_id(jsonb) does not existI'm trying to migrate to v2.5.0 on Debian 10 and running into the following error that is making the database migration fail:
```
00:23:07.391 [info] == Running 20210205145000 Pleroma.Repo.Migrations.MovePinnedActivitiesIntoPinnedObjec...I'm trying to migrate to v2.5.0 on Debian 10 and running into the following error that is making the database migration fail:
```
00:23:07.391 [info] == Running 20210205145000 Pleroma.Repo.Migrations.MovePinnedActivitiesIntoPinnedObjects.up/0 forward
** (Postgrex.Error) ERROR 42883 (undefined_function) function associated_object_id(jsonb) does not exist
query: SELECT a0."id", a0."data", a0."local", a0."actor", a0."recipients", a0."inserted_at", a0."updated_at", o1."id", o1."data", o1."inserted_at", o1."updated_at" FROM "activities" AS a0 INNER JOIN "objects" AS o1 ON (o1."data"->>'id') = associated_object_id(a0."data") WHERE (a0."id" = ANY($1))
hint: No function matches the given name and argument types. You might need to add explicit type casts.
(ecto_sql 3.9.0) lib/ecto/adapters/sql.ex:905: Ecto.Adapters.SQL.raise_sql_call_error/1
(ecto_sql 3.9.0) lib/ecto/adapters/sql.ex:820: Ecto.Adapters.SQL.execute/6
(ecto 3.9.2) lib/ecto/repo/queryable.ex:229: Ecto.Repo.Queryable.execute/4
(ecto 3.9.2) lib/ecto/repo/queryable.ex:19: Ecto.Repo.Queryable.all/3
_build/prod/lib/pleroma/priv/repo/migrations/20210205145000_move_pinned_activities_into_pinned_objects.exs:18: anonymous fn/1 in Pleroma.Repo.Migrations.MovePinnedActivitiesIntoPinnedObjects.up/0
(elixir 1.11.2) lib/stream.ex:441: anonymous fn/4 in Stream.each/2
(elixir 1.11.2) lib/enum.ex:3764: Enumerable.List.reduce/3
(elixir 1.11.2) lib/stream.ex:931: Stream.do_list_transform/7
```
The Postgres version is 12.13. I was on 11.9 before and had seen a similar issue about this when running versions older than 12, thought maybe updating to a newer version of Postgres would help but it's the same issue I was getting before.
I haven't found any information anywhere about an error like this but I also am not super knowledgeable about Postgres so I don't know if it's some simple thing or if the database is screwed up somehow. I hadn't touched Pleroma since installing it in Feb 2021.https://git.pleroma.social/pleroma/pleroma/-/issues/3056HTTP 500 error on viewing home timeline, related to PostgreSQL timeouts2023-01-27T08:38:25ZSimon VolpertHTTP 500 error on viewing home timeline, related to PostgreSQL timeouts<!--
### Precheck
* For support use https://git.pleroma.social/pleroma/pleroma-support or [community channels](https://git.pleroma.social/pleroma/pleroma#community-channels).
* Please do a quick search to ensure no similar bug has been ...<!--
### Precheck
* For support use https://git.pleroma.social/pleroma/pleroma-support or [community channels](https://git.pleroma.social/pleroma/pleroma#community-channels).
* Please do a quick search to ensure no similar bug has been reported before. If the bug has not been addressed after 2 weeks, it's fine to bump it.
* Try to ensure that the bug is actually related to the Pleroma backend. For example, if a bug happens in Pleroma-FE but not in Mastodon-FE or mobile clients, it's likely that the bug should be filed in [Pleroma-FE](https://git.pleroma.social/pleroma/pleroma-fe/issues/new) repository.
-->
### Environment
* Installation type (OTP or From Source): OTP, migrated from Source several years ago.
* Pleroma version (could be found in the "Version" tab of settings in Pleroma-FE): 2.4.5
* Elixir version (`elixir -v` for from source installations, N/A for OTP): N/A
* Operating system: Ubuntu 20.04.5 LTS
* PostgreSQL version (`psql -V`): 12.13
* Hardware: DigitalOcean 14$ general-purpose droplet (was 6$ originally)
* Instance type: small, under 10 local users, infrequent posting
* The database size, as reported by PostgreSQL, is about 1177 MB
### Bug description
Opening the home timeline in Preroma-FE as a logged in admin user causes a time out with a 500 error. While the timeline is loading, the CPU use jumps to 100%, with the most active process being PostgreSQL. If the timeline is left alone, it eventually loads some "new" statuses, which then can be displayed and read. The user account has several content filters active, but does not have a permanent effect. The log for the failed transaction contains the following message:
```
Jan 23 06:52:11 zombienet.org pleroma[79998]: [error] #PID<0.12817.4> running Pleroma.Web.Endpoint (connection #PID<0.12816.4>, stream id 1) terminated
Server: zombienet.org:80 (http)
Request: GET /api/v1/timelines/home?max_id=ARukhBgzdDCrDwdBS4&with_muted=false&limit=20
** (exit) an exception was raised:
** (DBConnection.ConnectionError) tcp recv: closed (the connection was closed by the pool, possibly due to a timeout or because the pool has been terminated)
(ecto_sql 3.6.2) lib/ecto/adapters/sql.ex:760: Ecto.Adapters.SQL.raise_sql_call_error/1
(ecto_sql 3.6.2) lib/ecto/adapters/sql.ex:693: Ecto.Adapters.SQL.execute/5
(ecto3.6.2) lib/ecto/repo/queryable.ex:224: Ecto.Repo.Queryable.execute/4
(ecto3.6.2) lib/ecto/repo/queryable.ex:19: Ecto.Repo.Queryable.all/3
(pleroma 2.4.5-2-gd8e32646) lib/pleroma/pagination.ex:40: Pleroma.Pagination.fetch_paginated/4(pleroma 2.4.5-2-gd8e32646) lib/pleroma/web/activity_pub/activity_pub.ex:484: Pleroma.Web.ActivityPub.ActivityPub.fetch_activities/3
(pleroma 2.4.5-2-gd8e32646) lib/pleroma/web/mastodon_api/controllers/timeline_controller.ex:56: Pleroma.Web.MastodonAPI.TimelineController.home/2
(pleroma 2.4.5-2-gd8e32646) lib/pleroma/web/mastodon_api/controllers/timeline_controller.ex:5: Pleroma.Web.MastodonAPI.TimelineController.action/2
```
Trying to load the timeline in toot and Fedilab also fails, so this is not limited to Pleroma-FE.
Trying to load any other timeline, including the local and federated timelines for both logged in users and guests produces erratic results.
The instance used to work fine for several years, before becoming unresponsive.
Things i have attempted so far to solve the issue:
* Upgrading to a newer Pleroma release
* Applying tweaks from pgtune
* VACUUM FULL
* Increasing the server's resources (from 6$ to 14$ worth)
* ./bin/pleroma_ctl database prune_objects --vacuum
* Optimizing the BEAM as suggested by the manual
What kind of steps might i take to further diagnose the issue, and, eventually, return to a fully working, responsive instance?https://git.pleroma.social/pleroma/pleroma/-/issues/3055Able to customize languages field in /api/v1/instance2023-02-09T19:23:30ZtusooaAble to customize languages field in /api/v1/instancecurrently, /api/v1/instance has hardcoded `languages` to be `["en"]`. one should be able to change this.currently, /api/v1/instance has hardcoded `languages` to be `["en"]`. one should be able to change this.