pleroma issueshttps://git.pleroma.social/pleroma/pleroma/-/issues2019-08-02T19:15:17Zhttps://git.pleroma.social/pleroma/pleroma/-/issues/1140pleroma_ctl arguments --listen-ip --listen-port2019-08-02T19:15:17Zyalh76pleroma_ctl arguments --listen-ip --listen-portWhen using the following command to generate an instance:
```bash
su pleroma -s /bin/bash -lc '/var/www/pleroma/pleroma/bin/pleroma_ctl instance gen --force --output /etc/pleroma/config.exs --output-psql /tmp/setup_db.psql --domain test4...When using the following command to generate an instance:
```bash
su pleroma -s /bin/bash -lc '/var/www/pleroma/pleroma/bin/pleroma_ctl instance gen --force --output /etc/pleroma/config.exs --output-psql /tmp/setup_db.psql --domain test41.yh.yalh.net --instance-name My_Pleroma --admin-email yalh@yh04.yh.yalh.net --notify-email yalh@yh04.yh.yalh.net --dbhost localhost --dbname pleroma --dbuser pleroma --dbpass FrrXzKmAUBUSWa4LMkjMuvFrUKPuvl --rum N --indexable Y --db-configurable Y --uploads-dir /home/yunohost.app/pleroma/storage/uploads --static-dir /home/yunohost.app/pleroma/storage/static --listen-ip 127.0.0.1 --listen-port 8095'
```
There is an error:
```
** (MatchError) no match of right hand side value: {[force: true, output: "/etc/pleroma/config.exs", output_psql: "/tmp/setup_db.psql", domain: "test41.yh.yalh.net", instance_name: "My_Pleroma", admin_email: "yalh@yh04.yh.yalh.net", notify_email: "yalh@yh04.yh.yalh.net", dbhost: "localhost", dbname: "pleroma", dbuser: "pleroma", dbpass: "FrrXzKmAUBUSWa4LMkjMuvFrUKPuvl", rum: "N", indexable: "Y", db_configurable: "Y", uploads_dir: "/home/yunohost.app/pleroma/storage/uploads", static_dir: "/home/yunohost.app/pleroma/storage/static"], [], [{"--listen-ip", nil}, {"--listen-port", nil}]}
(pleroma) lib/mix/tasks/pleroma/instance.ex:40: Mix.Tasks.Pleroma.Instance.run/1
(stdlib) erl_eval.erl:680: :erl_eval.do_apply/6
(elixir) lib/code.ex:240: Code.eval_string/3
```
The error is not present when removing `--listen-ip 127.0.0.1 --listen-port 8095`
And there is still and error when only using `--listen-ip 127.0.0.1` or `--listen-port 8095`https://git.pleroma.social/pleroma/pleroma/-/issues/1139pleroma_ctl argument --uploads-dir2019-08-02T18:46:15Zyalh76pleroma_ctl argument --uploads-dirWhen generating the `config.exs` using :
`su pleroma -s /bin/bash -lc '/var/www/pleroma/pleroma/bin/pleroma_ctl instance gen --force --output /etc/pleroma/config.exs --output-psql /tmp/setup_db.psql --domain test41.yh.yalh.net --instance...When generating the `config.exs` using :
`su pleroma -s /bin/bash -lc '/var/www/pleroma/pleroma/bin/pleroma_ctl instance gen --force --output /etc/pleroma/config.exs --output-psql /tmp/setup_db.psql --domain test41.yh.yalh.net --instance-name My_Pleroma --admin-email yalh@yh04.yh.yalh.net --notify-email yalh@yh04.yh.yalh.net --dbhost localhost --dbname pleroma --dbuser pleroma --dbpass FrrXzKmAUBUSWa4LMkjMuvFrUKPuvl --rum N --indexable Y --db-configurable Y --uploads-dir /home/yunohost.app/pleroma/storage/uploads --static-dir /home/yunohost.app/pleroma/storage/static'`
The generator asks:
`What directory should media uploads go in (when using the local uploader)? [/var/lib/pleroma/uploads]`
I can press `return` and the generation continue using `/var/lib/pleroma/uploads` for uploads in the config.exs
But uploads-dir is provided so it seems that pleroma_ctl doesn't use the argument providedhttps://git.pleroma.social/pleroma/pleroma/-/issues/1136Issue with the streaming API2020-01-28T16:10:19Ztom79Issue with the streaming APII have been warned that live notifications don't work.
I tested two endpoints which both fail:
`wss://pleroma.fedilab.app/api/v1/streaming/?stream=user:notification&access_token=xxxxxxxxx`
`wss://pleroma.fedilab.app/api/v1/streaming/?...I have been warned that live notifications don't work.
I tested two endpoints which both fail:
`wss://pleroma.fedilab.app/api/v1/streaming/?stream=user:notification&access_token=xxxxxxxxx`
`wss://pleroma.fedilab.app/api/v1/streaming/?stream=user&access_token=xxxxxxxxx`
I only noticed from the reply:
`emitter: HTTP/1.1 500 Internal Server Error`
I tried to check logs with
`journalctl -u pleroma -r`
But there is nothing about this error 500. How could I debug it deeper from the server side?https://git.pleroma.social/pleroma/pleroma/-/issues/1134Pruning the database. What will be pruned?2019-08-04T18:37:26ZRoelof PieterPruning the database. What will be pruned?Hi. If I understood correctly it is now possible to run something like: **mix pleroma.database prune_objects** to "prune" the database. I assume that this removes old and/or irrelevant objects from the database. Is this correct? And if s...Hi. If I understood correctly it is now possible to run something like: **mix pleroma.database prune_objects** to "prune" the database. I assume that this removes old and/or irrelevant objects from the database. Is this correct? And if so, what will be removed? I assume not my own posts, but I am unable to find any info on this. I also assume the setting: **remote_post_retention_days** has something to do with this?https://git.pleroma.social/pleroma/pleroma/-/issues/1131nginx proxy doesn't seem to cache correctly2022-12-24T21:12:04Zricknginx proxy doesn't seem to cache correctlyHi,
i recently configured the mediaproxy and the nginx cache.
Pleroma mediaproxy seems to work fine cause all images are no served throuh pl.n0id.space/proxy
But i have a problem with the nginx cache.. i set my configs according to htt...Hi,
i recently configured the mediaproxy and the nginx cache.
Pleroma mediaproxy seems to work fine cause all images are no served throuh pl.n0id.space/proxy
But i have a problem with the nginx cache.. i set my configs according to https://git.pleroma.social/pleroma/pleroma/blob/develop/installation/pleroma.nginx
outside server block:
```
proxy_cache_path /tmp/pleroma-media levels=1:2 keys_zone=pleroma_media_cache:10m max_size=3g inactive=720m use_temp_path=off;
```
inside:
```
## Media Proxy
location ~ ^/(media|proxy) {
proxy_cache pleroma_media_cache;
slice 1m;
proxy_cache_key $host$uri$is_args$args$slice_range;
proxy_set_header Range $slice_range;
proxy_http_version 1.1;
proxy_cache_valid 200 206 301 304 1h;
proxy_cache_lock on;
proxy_ignore_client_abort on;
proxy_buffering on;
chunked_transfer_encoding on;
proxy_ignore_headers Cache-Control;
proxy_hide_header Cache-Control;
proxy_pass http://localhost:4000;
}
```
But the directory `/tmp/pleroma-media` stays empty.. there are also no erros logged to nginx.error
I also checked the permission for the nginx user on the cachedir. I can create files with the nginx user in `/tmp/pleroma-media`
Currently i run develop with commit d1e891062e3c6c34ca7940a476917beea2822ca2
Sadly i'm not an nginx guru, so am i missing something or is this a bug?https://git.pleroma.social/pleroma/pleroma/-/issues/1130Refactor subscription functionality2019-09-27T03:51:26ZfeldRefactor subscription functionalitySubscription functionality was hacked in as an extension which piggybacks on the notifications. This feature works great for what it is, but it adds too much noise to your notifications/mentions and you can't see things that were directe...Subscription functionality was hacked in as an extension which piggybacks on the notifications. This feature works great for what it is, but it adds too much noise to your notifications/mentions and you can't see things that were directed at you.
Propose the following changes:
1) Subscription notifications should be stored in a separate table from normal notifications
2) Create a new timeline to view them / MastoAPI extension to notifications to view them
3) After marking read they should be cleared. I see little value in keeping this history. If you want to see the history... go look at the user's profile and see their statuses.
4) We'll build a way to flip between notifications and subscriptions in FE
Users of clients that don't support this feature will still get push notifications for these messages. I don't think we can fix that because it's just the nature of diverse clients in this open ecosystem. Such is life.Roman ChvanikovRoman Chvanikovhttps://git.pleroma.social/pleroma/pleroma/-/issues/1129Certain notifications are dropped from stream2020-03-08T13:42:23ZnikCertain notifications are dropped from streamCertain notifications are dropped from the MastoAPI stream, I'm having trouble discerning a clear pattern but today all DMs from tindall@cybre.space have only streamed into my timeline, not my notifications, and I also had a pattern of d...Certain notifications are dropped from the MastoAPI stream, I'm having trouble discerning a clear pattern but today all DMs from tindall@cybre.space have only streamed into my timeline, not my notifications, and I also had a pattern of dropped new follow notifications.
amy@pl.knotteye.cc reported having the same issuehttps://git.pleroma.social/pleroma/pleroma/-/issues/1128Credentials problems, and no recovery capability ?2019-07-27T12:14:14ZMars EyeCredentials problems, and no recovery capability ?Hello Lain,
I just complained to my sysadmin at soteria.mastodon.host that my creadentials are rejected. Since my account still exists (and was not modified), I presume that my password only has a problem. But I never changed it... I t...Hello Lain,
I just complained to my sysadmin at soteria.mastodon.host that my creadentials are rejected. Since my account still exists (and was not modified), I presume that my password only has a problem. But I never changed it... I tried both front-ends (PleromaFE and MastoFE) : same rejection.
And since my sysadmin found nothing wrong on his side, I'm feeling lonely now.
Seems there's no password recovery function around ?
Any help welcome. Thank you.https://git.pleroma.social/pleroma/pleroma/-/issues/1127HTTP 303 causing errors on user fetch2019-07-28T20:24:40ZfeldHTTP 303 causing errors on user fetch> Could not decode user at fetch https://social.mayfirst.org/user/26962, {:error, {:error, {:invalid_redirection, {:ok, 303, [{"Date", "Wed, 24 Jul 2019 21:16:24 GMT"}, {"Server", "Apache/2.4.25 (Debian)"}, {"Connection", "close"}, {"Loc...> Could not decode user at fetch https://social.mayfirst.org/user/26962, {:error, {:error, {:invalid_redirection, {:ok, 303, [{"Date", "Wed, 24 Jul 2019 21:16:24 GMT"}, {"Server", "Apache/2.4.25 (Debian)"}, {"Connection", "close"}, {"Location", "https://social.mayfirst.org/davehunt"}, {"Transfer-Encoding", "chunked"}, {"Content-Type", "text/html; charset=UTF-8"}], {:client, {1564, 2984, 682054}, {:metrics_ng, :metrics_dummy}, :hackney_ssl, 'social.mayfirst.org', 443, "social.mayfirst.org", [connect_timeout: 10000, recv_timeout: 20000, follow_redirect: true, pool: :federation, ssl_options: [partial_chain: &:hackney_connect.partial_chain/1, versions: [:tlsv1, :"tlsv1.1", :"tlsv1.2"]], proxy: nil], {:sslsocket, {:gen_tcp, #Port<0.47843>, :tls_connection, :undefined}, [#PID<0.11332.17>, #PID<0.11331.17>]}, {:federation, #Reference<0.3291865379.1246756867.249633>, {'social.mayfirst.org', 443, :hackney_ssl}, #PID<0.545.0>, :hackney_ssl}, #Reference<0.3291865379.1246756867.249633>, true, :hackney_pool, 20000, true, 5, false, 5, nil, nil, {:hparser, :response, 4096, 10, 0, :on_body, "f1\r\n<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<!DOCTYPE a\nPUBLIC \"-//W3C//DTD XHTML 1.0 Strict//EN\"\n \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd\">\n<a href=\"https://social.mayfirst.org/davehunt\">https://social.mayfirst.org/davehunt</a>\n\r\n0\r\n\r\n", {1, 1}, "", [], :undefined, "chunked", "close", "text/html; charset=utf-8", "https://social.mayfirst.org/davehunt", :waiting}, {6, {:dict, 6, 16, 16, 8, 80, 48, {[], [], [], [], [], [], [], [], ...}, {{[], [["location", {3, ...}]], [["date", {...}]], [], [], [...], ...}}}}, :connected, :waiting, nil, :normal, false, false, false, :undefined, false, &:hackney_request.send/2, :waiting, nil, 4096, "", [], {1, 1}, :undefined, "chunked", ...}}}}}
Seems that we're failing to follow HTTP 303s correctlySergey SuprunenkoSergey Suprunenkohttps://git.pleroma.social/pleroma/pleroma/-/issues/1126If Pleroma.Upload has a custom base_url, don't prefix path with "media"2019-07-25T14:34:25ZfeldIf Pleroma.Upload has a custom base_url, don't prefix path with "media"As seen in `lib/pleroma/upload.ex`:
```
defp url_from_spec(%__MODULE__{name: name}, base_url, {:file, path}) do
path =
URI.encode(path, &char_unescaped?/1) <>
if Pleroma.Config.get([__MODULE__, :link_name], false) do...As seen in `lib/pleroma/upload.ex`:
```
defp url_from_spec(%__MODULE__{name: name}, base_url, {:file, path}) do
path =
URI.encode(path, &char_unescaped?/1) <>
if Pleroma.Config.get([__MODULE__, :link_name], false) do
"?name=#{URI.encode(name, &char_unescaped?/1)}"
else
""
end
[base_url, "media", path]
|> Path.join()
end
```
"media" is always hardcoded in here which requires you to have a "media" dir in your storage. That's not required for S3 buckets normally when you don't have a different base_url; the "/media" is only there for Pleroma's routing.feldfeldhttps://git.pleroma.social/pleroma/pleroma/-/issues/1125Pleroma 1.0.2 backport requests2019-08-03T22:26:43ZkaniiniPleroma 1.0.2 backport requestsPlease comment on this bug with changes you'd like backported from develop. We are only backporting fixes and minor features for the 1.0.2 release.Please comment on this bug with changes you'd like backported from develop. We are only backporting fixes and minor features for the 1.0.2 release.https://git.pleroma.social/pleroma/pleroma/-/issues/1124errors while installing2022-09-25T09:09:03ZMason Hockerrors while installingHi. I'm trying to install Pleroma on a Debian based distro following [these instructions](https://docs.pleroma.social/otp_en.html), and I'm stuck at
```
# su pleroma -s $SHELL -lc "./bin/pleroma_ctl instance gen --output /etc/pleroma/co...Hi. I'm trying to install Pleroma on a Debian based distro following [these instructions](https://docs.pleroma.social/otp_en.html), and I'm stuck at
```
# su pleroma -s $SHELL -lc "./bin/pleroma_ctl instance gen --output /etc/pleroma/config.exs --output-psql /tmp/setup_db.psql"
```
I get
```
!!! /etc/pleroma/config.exs not found! Please ensure it exists and that PLEROMA_CONFIG_PATH is unset or points to an existing file
```
am them prompted to answer questions, and then after answering "What is the user used to connect to your database?" get
```
13:54:13.530 [error] Unable to load crypto library. Failed with error:
":load_failed, Failed to load NIF library /opt/pleroma/lib/crypto-4.4.2/priv/lib/crypto: 'libcrypto.so.1.1: cannot open shared object file: No such file or directory'"
OpenSSL might not be installed on this system.
13:54:13.541 [warn] The on_load function for module crypto returned:
{:error, {:load_failed, 'Failed to load NIF library /opt/pleroma/lib/crypto-4.4.2/priv/lib/crypto: \'libcrypto.so.1.1: cannot open shared object file: No such file or directory\''}}
** (UndefinedFunctionError) function :crypto.strong_rand_bytes/1 is undefined (module :crypto is not available)
:crypto.strong_rand_bytes(64)
(pleroma) lib/mix/tasks/pleroma/instance.ex:137: Mix.Tasks.Pleroma.Instance.run/1
(stdlib) erl_eval.erl:680: :erl_eval.do_apply/6
(elixir) lib/code.ex:240: Code.eval_string/3
```
The package `openssl` is installed.https://git.pleroma.social/pleroma/pleroma/-/issues/1123Error with pleroma_ctl migrate on a fresh installation2019-07-27T07:22:22ZfhcError with pleroma_ctl migrate on a fresh installationHi,
On a fresh Ubuntu 18.04 installation, I had a problem running the following step of the [documentation](https://docs.pleroma.social/otp_en.html#content) :
`su pleroma -s $SHELL -lc "./bin/pleroma_ctl migrate"`
The migration failed...Hi,
On a fresh Ubuntu 18.04 installation, I had a problem running the following step of the [documentation](https://docs.pleroma.social/otp_en.html#content) :
`su pleroma -s $SHELL -lc "./bin/pleroma_ctl migrate"`
The migration failed and I had the following message :
`'08:49:55.659 [info] alter table users
** (Postgrex.Error) ERROR 42P07 (duplicate_table) relation "users_email_index" already exists'`
I found that skipping **20170415141210_add_unique_index_to_email_and_nickname.exs** and applying it at the very end do the job.
If you need any further info, feel free to ask :)https://git.pleroma.social/pleroma/pleroma/-/issues/1122error messages (log)2020-05-04T09:49:24ZJulienerror messages (log)Can anybody help me understanding this error message ?
pleroma keeps crashing after 5 minutes...
Jul 23 08:27:30 saturne pleroma: [error] Task #PID<0.25280.2> started from PleromaJobQueue.Worker terminating#012** (ArgumentError) argum...Can anybody help me understanding this error message ?
pleroma keeps crashing after 5 minutes...
Jul 23 08:27:30 saturne pleroma: [error] Task #PID<0.25280.2> started from PleromaJobQueue.Worker terminating#012** (ArgumentError) argument error#012 (stdlib) :ets.lookup(:cachex_overseer_table, :user_cache)#012 (cachex) lib/cachex/services/overseer.ex:89: Cachex.Services.Overseer.retrieve/1#012 (cachex) lib/cachex.ex:665: Cachex.fetch/4#012 (cachex) lib/cachex.ex:1: Cachex.fetch!/3#012 (pleroma) lib/pleroma/web/federator/federator.ex:140: Pleroma.Web.Federator.ap_enabled_actor/1#012 (pleroma) lib/pleroma/web/federator/federator.ex:103: Pleroma.Web.Federator.perform/2#012 (elixir) lib/task/supervised.ex:90: Task.Supervised.invoke_mfa/2#012 (stdlib) proc_lib.erl:249: :proc_lib.init_p_do_apply/3#012Function: #Function<2.25193041/0 in PleromaJobQueue.Worker.maybe_start_job/4>#012 Args: []
thanks !https://git.pleroma.social/pleroma/pleroma/-/issues/1121Notifications break, log shows (Ecto.MultipleResultsError) expected at most o...2020-05-07T09:15:51Zfl0wnNotifications break, log shows (Ecto.MultipleResultsError) expected at most one result but got 2 in queryI'm not sure what's going on but I've had this happen twice in two days. When it does, notifications fail with a 500 error until the offending account can be deactivated.
Thread when I hit the error yesterday: https://take.iteasy.club/n...I'm not sure what's going on but I've had this happen twice in two days. When it does, notifications fail with a 500 error until the offending account can be deactivated.
Thread when I hit the error yesterday: https://take.iteasy.club/notice/9l4pdlditC6IZCR9aS
Thread from today: https://take.iteasy.club/notice/9l7Ku1QbRSML3uS0dEhttps://git.pleroma.social/pleroma/pleroma/-/issues/1119Is your usage of priv / static / instance / panel.html different from documen...2019-07-25T05:39:09ZariesIs your usage of priv / static / instance / panel.html different from documentation?I read this document and decided to change the panel.html of my Pleroma instance.
https://git.pleroma.social/pleroma/pleroma/blob/develop/docs/config/small_customizations.md
But panel.html is currently managed by git, so need to fork, ...I read this document and decided to change the panel.html of my Pleroma instance.
https://git.pleroma.social/pleroma/pleroma/blob/develop/docs/config/small_customizations.md
But panel.html is currently managed by git, so need to fork, branch, merge, etc. (I just want to add a few sentences...)
I gues the option show_instance_panel is gone, is there any better way?
I came up with a way to use git stash, but it feels like it's not a good practice.https://git.pleroma.social/pleroma/pleroma/-/issues/1116:auto_linker shouldn't strip prefix in code blocks2019-07-22T02:50:51ZYour New SJW Waifu:auto_linker shouldn't strip prefix in code blocks:auto_linker strips prefix in code blocks. I feel it should also not hyperlink URLs in code blocks but that's likely debatable so maybe make that behavior configurable.:auto_linker strips prefix in code blocks. I feel it should also not hyperlink URLs in code blocks but that's likely debatable so maybe make that behavior configurable.https://git.pleroma.social/pleroma/pleroma/-/issues/1115HTML when composing2020-05-23T15:08:36Ztom79HTML when composingI implemented a wysiwyg for Pleroma with the app. But only some elements are working.
<details><summary>Screen shot from the app</summary>
![Screenshot_20190720_172018](/uploads/c78e5c13b7960279ce89d55d0f7cfc30/Screenshot_20190720_1720...I implemented a wysiwyg for Pleroma with the app. But only some elements are working.
<details><summary>Screen shot from the app</summary>
![Screenshot_20190720_172018](/uploads/c78e5c13b7960279ce89d55d0f7cfc30/Screenshot_20190720_172018.jpg)
</details>
<details><summary>Screen shot from of the result</summary>
![result_wysiwyg](/uploads/b53e786f3f3e59535662c476e2e00a3b/result_wysiwyg.png)
</details>
Is it possible to take into account:
- inline style: like `style="color:#f3f3f3;"`
- `<hr/>`
Here is an example of what the application sends:
```html
<h1 data-tag="input" style="color:#f3f3f3;">Bonjour</h1>
<p data-tag="input" style="color:#f3f3f3;">
<b><i>Une liste</i></b>
</p>
<ul data-tag="ul">
<li data-tag="list-item-ul"><span style="color:#f3f3f3;">Élément 1</span></li>
<li data-tag="list-item-ul"><span style="color:#f3f3f3;">Élément 2</span></li>
<li data-tag="list-item-ul"><span style="color:#f3f3f3;">Élément 3</span></li>
</ul>
<hr data-tag="hr"/>
<p data-tag="input" style="color:#FF002D;">Rouge</p>
<p data-tag="input" style="color:#00FF29;">Vert</p>
<blockquote data-tag="input" style="color:#000000;">Citation</blockquote>
<p data-tag="input" style="color:#f3f3f3;">Ok</p>
<p data-tag="input" style="color:#f3f3f3;"></p>
```https://git.pleroma.social/pleroma/pleroma/-/issues/1114Tests failing hard on MacOS2020-05-25T19:25:16ZfeldTests failing hard on MacOSNew sha512 hash thing fails on MacOS. crypt(3) on MacOS is quite legacy and only implements DES. We fixed this for an older test in e9c075d05
```
* test checkpw/2 check sha512-crypt hash (0.6ms)
1) test checkpw/2 check sha512-cryp...New sha512 hash thing fails on MacOS. crypt(3) on MacOS is quite legacy and only implements DES. We fixed this for an older test in e9c075d05
```
* test checkpw/2 check sha512-crypt hash (0.6ms)
1) test checkpw/2 check sha512-crypt hash (Pleroma.Plugs.AuthenticationPlugTest)
test/plugs/authentication_plug_test.exs:67
Expected truthy, got false
code: assert AuthenticationPlug.checkpw("password", hash)
arguments:
# 1
"password"
# 2
"$6$9psBWV8gxkGOZWBz$PmfCycChoxeJ3GgGzwvhlgacb9mUoZ.KUXNCssekER4SJ7bOK53uXrHNb2e4i8yPFgSKyzaW9CcmrDXWIEMtD1"
stacktrace:
test/plugs/authentication_plug_test.exs:71: (test)
```Sergey SuprunenkoSergey Suprunenkohttps://git.pleroma.social/pleroma/pleroma/-/issues/1112Error when using /api/v2/search endpoint2019-07-20T14:59:45Ztom79Error when using /api/v2/search endpointWhen I use the API endpoint `/api/v2/search` I got errors when fetching an account with its URL:
`/api/v2/search?q=https%3A%2F%2Fframapiaf.org%2F%40fedilab&resolve=true&limit=20`
Trace logs:
```
Jul 18 18:24:15 fedilab-server mix[1288...When I use the API endpoint `/api/v2/search` I got errors when fetching an account with its URL:
`/api/v2/search?q=https%3A%2F%2Fframapiaf.org%2F%40fedilab&resolve=true&limit=20`
Trace logs:
```
Jul 18 18:24:15 fedilab-server mix[1288]: (pleroma) lib/pleroma/user.ex:1151: Pleroma.User.insert_or_update_user/1
Jul 18 18:24:15 fedilab-server mix[1288]: (db_connection) lib/db_connection.ex:1415: DBConnection.run_transaction/4
Jul 18 18:24:15 fedilab-server mix[1288]: (ecto_sql) lib/ecto/adapters/sql.ex:887: anonymous fn/3 in Ecto.Adapters.SQL.checkout_or_transaction/4
Jul 18 18:24:15 fedilab-server mix[1288]: (ecto) lib/ecto/repo/schema.ex:914: anonymous fn/3 in Ecto.Repo.Schema.wrap_in_transaction/6
Jul 18 18:24:15 fedilab-server mix[1288]: (ecto) lib/ecto/repo/schema.ex:274: anonymous fn/15 in Ecto.Repo.Schema.do_insert/4
Jul 18 18:24:15 fedilab-server mix[1288]: (ecto) lib/ecto/repo/schema.ex:672: Ecto.Repo.Schema.constraints_to_errors/3
Jul 18 18:24:15 fedilab-server mix[1288]: (elixir) lib/enum.ex:1327: Enum."-map/2-lists^map/1-0-"/2
Jul 18 18:24:15 fedilab-server mix[1288]: (ecto) lib/ecto/repo/schema.ex:687: anonymous fn/4 in Ecto.Repo.Schema.constraints_to_errors/3
Jul 18 18:24:15 fedilab-server mix[1288]: * users_nickname_index (unique_constraint)
Jul 18 18:24:15 fedilab-server mix[1288]: The changeset defined the following constraints:
Jul 18 18:24:15 fedilab-server mix[1288]: `:name` as an option.
Jul 18 18:24:15 fedilab-server mix[1288]: call `foreign_key_constraint/3` on your changeset with the constraint
Jul 18 18:24:15 fedilab-server mix[1288]: exception and instead add it as an error to your changeset, please
Jul 18 18:24:15 fedilab-server mix[1288]: If you would like to stop this constraint violation from raising an
Jul 18 18:24:15 fedilab-server mix[1288]: * conversation_participations_user_id_fkey (foreign_key_constraint)
Jul 18 18:24:15 fedilab-server mix[1288]: ** (Ecto.ConstraintError) constraint error when attempting to insert struct:
Jul 18 18:24:15 fedilab-server mix[1288]: ** (exit) an exception was raised:
Jul 18 18:24:15 fedilab-server mix[1288]: Request: GET /api/v2/search?q=https%3A%2F%2Fframapiaf.org%2F%40fedilab&resolve=true&limit=20
Jul 18 18:24:15 fedilab-server mix[1288]: Server: pleroma.fedilab.app:80 (http)
Jul 18 18:24:15 fedilab-server mix[1288]: 18:24:15.647 [error] #PID<0.23573.3> running Pleroma.Web.Endpoint (connection #PID<0.23572.3>, stream id 1) terminated
Jul 18 18:24:15 fedilab-server mix[1288]: 18:24:15.643 request_id=FbKNAN5uyhkqNKcAAujy [error] Internal server error: %Ecto.ConstraintError{constraint: "conversation_partipations_user_id_fkey", message: "constraint error when attempting to insert struct:\n\n * conversation_participations_user_id_fkey (foreign_key_constraint)\n\nIf you would like to stop this constraint violation from raising an\nexception and instead add it as an error to your changeset, please\ncall `foreign_key_constraint/3` on your changeset with the constraint\n`:name` as an option.\n\nThe changeset defined the following constraints:\n\n * users_nickname_index (unique_constraint)\n", type: :foreign_key}
```