pleroma issueshttps://git.pleroma.social/pleroma/pleroma/-/issues2023-05-26T22:16:26Zhttps://git.pleroma.social/pleroma/pleroma/-/issues/3030v2.5.0 crypt library requires GLIBC_2.252023-05-26T22:16:26Zdebulav2.5.0 crypt library requires GLIBC_2.25TLDR: hang, restart, hang, restart...
I'm running a small Pleroma instance on an 1C1G tiny VPS and everything works fine. The memory consumed by the Pleroma process fluctuates roughly around 160-240MB.
But today when I update to v2.5.0...TLDR: hang, restart, hang, restart...
I'm running a small Pleroma instance on an 1C1G tiny VPS and everything works fine. The memory consumed by the Pleroma process fluctuates roughly around 160-240MB.
But today when I update to v2.5.0, it can't be started again. Here are some sample logs:
```
Dec 24 12:08:51 constance systemd[1]: Started Pleroma social network.
Dec 24 12:08:56 constance pleroma[1647]: 2022-12-24 12:08:56.440861 supervisor_report #{label=>{supervisor,start_error},report=>[{supervisor,{local,kernel_sup}},{errorContext,start_error},{reason,{on_load_function_failed,crypt}},{offender,[{pid,undefined},{id,kernel_safe_sup},{mfargs,{supervisor,start_link,[{local,kernel_safe_sup},kernel,safe]}},{restart_type,permanent},{shutdown,infinity},{child_type,supervisor}]}]}
Dec 24 12:08:56 constance pleroma[1647]: 2022-12-24 12:08:56.440951 crash_report #{label=>{proc_lib,crash},report=>[[{initial_call,{supervisor,kernel,['Argument__1']}},{pid,<0.3543.0>},{registered_name,[]},{error_info,{exit,{on_load_function_failed,crypt},[{init,run_on_load_handlers,0,[]},{kernel,init,1,[{file,"kernel.erl"},{line,189}]},{supervisor,init,1,[{file,"supervisor.erl"},{line,301}]},{gen_server,init_it,2,[{file,"gen_server.erl"},{line,417}]},{gen_server,init_it,6,[{file,"gen_server.erl"},{line,385}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,226}]}]}},{ancestors,[kernel_sup,<0.3516.0>]},{message_queue_len,0},{messages,[]},{links,[<0.3518.0>]},{dictionary,[]},{trap_exit,true},{status,running},{heap_size,610},{stack_size,28},{reductions,262}],[]]}
Dec 24 12:08:57 constance pleroma[1647]: 2022-12-24 12:08:57.458325 crash_report #{label=>{proc_lib,crash},report=>[[{initial_call,{application_master,init,['Argument__1','Argument__2','Argument__3','Argument__4']}},{pid,<0.3515.0>},{registered_name,[]},{error_info,{exit,{{shutdown,{failed_to_start_child,kernel_safe_sup,{on_load_function_failed,crypt}}},{kernel,start,[normal,[]]}},[{application_master,init,4,[{file,"application_master.erl"},{line,138}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,226}]}]}},{ancestors,[<0.3514.0>]},{message_queue_len,1},{messages,[{'EXIT',<0.3516.0>,normal}]},{links,[<0.3514.0>,<0.3513.0>]},{dictionary,[]},{trap_exit,true},{status,running},{heap_size,376},{stack_size,28},{reductions,190}],[]]}
Dec 24 12:08:57 constance pleroma[1647]: 2022-12-24 12:08:57.468156 std_info #{label=>{application_controller,exit},report=>[{application,kernel},{exited,{{shutdown,{failed_to_start_child,kernel_safe_sup,{on_load_function_failed,crypt}}},{kernel,start,[normal,[]]}}},{type,permanent}]}
Dec 24 12:08:57 constance pleroma[1647]: {"Kernel pid terminated",application_controller,"{application_start_failure,kernel,{{shutdown,{failed_to_start_child,kernel_safe_sup,{on_load_function_failed,crypt}}},{kernel,start,[normal,[]]}}}"}
Dec 24 12:08:57 constance pleroma[1647]: Kernel pid terminated (application_controller) ({application_start_failure,kernel,{{shutdown,{failed_to_start_child,kernel_safe_sup,{on_load_function_failed,crypt}}},{kernel,start,[normal,[]]}}})
Dec 24 12:08:57 constance pleroma[1647]: #015
Dec 24 12:08:58 constance pleroma[1647]: Crash dump is being written to: erl_crash.dump...done
Dec 24 12:08:58 constance systemd[1]: pleroma.service: Main process exited, code=exited, status=1/FAILURE
Dec 24 12:08:58 constance pleroma[1697]: --rpc-eval : RPC failed with reason :nodedown
Dec 24 12:08:58 constance systemd[1]: pleroma.service: Control process exited, code=exited status=1
Dec 24 12:08:58 constance systemd[1]: pleroma.service: Unit entered failed state.
Dec 24 12:08:58 constance systemd[1]: pleroma.service: Failed with result 'exit-code'.
Dec 24 12:08:58 constance systemd[1]: pleroma.service: Service hold-off time over, scheduling restart.
Dec 24 12:08:58 constance systemd[1]: Stopped Pleroma social network.
Dec 24 12:08:58 constance systemd[1]: Started Pleroma social network.
...
```
Since it was killed at start time, I guess the culprit might be the new version of Elixir.
Now I'm trying to roll back to [v2.4.5](https://git.pleroma.social/pleroma/pleroma/-/pipelines/42739). Fortunately, a database backup was made before the upgrade.https://git.pleroma.social/pleroma/pleroma/-/issues/3029Unable to register user2022-12-21T20:41:59ZSean KingUnable to register user### Environment
* Installation type (OTP or From Source): from source (develop branch
* Pleroma version (could be found in the "Version" tab of settings in Pleroma-FE):
* Elixir version (`elixir -v` for from source installations, N/A f...### Environment
* Installation type (OTP or From Source): from source (develop branch
* 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): 1.13.4 (OTP 25)
* Operating system: Linux Mint 20
* PostgreSQL version (`psql -V`): 15.1
### Bug description
Whenever I go to register a user on the registration page, I register a test user. But it shows the password confirmation should be the same as the password for the error after clicking "Register". However, both fields are the same. Not sure what's going on.
![image](/uploads/137bf60865721c79b671d757a13a07d1/image.png)2.5.0https://git.pleroma.social/pleroma/pleroma/-/issues/3028search only finds users who start with the search term2023-05-08T00:45:35Zrobinsearch only finds users who start with the search termWhen you search for a user, it only finds results that start with your search term; it would be much more useful (at least to me) if it found results that contain the term.
The specific example that inspired me to open an issue was sear...When you search for a user, it only finds results that start with your search term; it would be much more useful (at least to me) if it found results that contain the term.
The specific example that inspired me to open an issue was searching for an account I'd just added to the instance I use to mirror Twitter accounts so they can be followed from the fediverse (https://twitter.oksocial.net); the account is "PlayARKMobile", but all I could remember was that it was related to Ark.
Searching for "ark" on that instance finds no users, but searching for "play" does find it.
(I had to look back at the the mirror config for the username. :-)https://git.pleroma.social/pleroma/pleroma/-/issues/3027Should dedupe poll options2023-04-13T08:40:06ZtusooaShould dedupe poll optionsStep to reproduce:
- Post a poll with only two identical options from glitch-lily
Expected:
- Get an error saying "too few different choices"
Actual:
- The poll is posted, and whenever someone votes, it is counted towards both choices....Step to reproduce:
- Post a poll with only two identical options from glitch-lily
Expected:
- Get an error saying "too few different choices"
Actual:
- The poll is posted, and whenever someone votes, it is counted towards both choices.
Note: dedupe is implemented in Pleroma-FE, but it really should be implemented in BE. I'm not sure how federation behaves.https://git.pleroma.social/pleroma/pleroma/-/issues/3025Not getting all emoji when downloading pack from remote instance2023-05-08T00:46:46ZHJNot getting all emoji when downloading pack from remote instanceImporting remote emoji pack seem to download first 30 of the pack and fails the rest, emoji are still created but have no files for them.Importing remote emoji pack seem to download first 30 of the pack and fails the rest, emoji are still created but have no files for them.https://git.pleroma.social/pleroma/pleroma/-/issues/3024Backup: Better representation of status2023-06-27T12:08:13ZtusooaBackup: Better representation of statusWe should have notation of "not processed," "in progress," "success," and "failed."We should have notation of "not processed," "in progress," "success," and "failed."https://git.pleroma.social/pleroma/pleroma/-/issues/3023Web interface not detecting video properly2022-12-19T17:22:57ZmellofoneWeb interface not detecting video properly* Installation type (OTP or From Source): OTP binary via Arch Linux AUR package.
* Pleroma version (could be found in the "Version" tab of settings in Pleroma-FE): Backend version 2.4.4, Frontend version b13d8f7e.
* Elixir version (`elix...* Installation type (OTP or From Source): OTP binary via Arch Linux AUR package.
* Pleroma version (could be found in the "Version" tab of settings in Pleroma-FE): Backend version 2.4.4, Frontend version b13d8f7e.
* Elixir version (`elixir -v` for from source installations, N/A for OTP): Elixir 1.14.0 (compiled with Erlang/OTP 25)
* Operating system: Arch Linux
* PostgreSQL version (`psql -V`): psql (PostgreSQL) 14.5
### Bug description
I posted several mp4 files and somewhere that file is detected incorrectly, but only on the web frontend. Example URL: https://oddprocess.social/notice/AQdWvbrteuvGx2T6VE If I right click on the file link, it has nothing regarding video, only audio. I downloaded the mp4 from the post and it plays fine locally. If I also go to a mastodon instance and view the post there, the video plays fine. I have tried both Firefox and Chrome, and the results are the same. If I use the same account/instance on an app such as Tusky or Fedilab, the video plays as expected.https://git.pleroma.social/pleroma/pleroma/-/issues/3022URLs ending in ..mp3 are not detected as URLs2023-02-09T21:25:18ZJeff CliffURLs ending in ..mp3 are not detected as URLs# Environment info
<!-- Everything is optional and where applicable but the more information the better. -->
* Browser, version, OS, platform: Version 107.0.5304.110 (Official Build) snap (64-bit), Ubuntu 20.04 LTS
* Instance URL: shitp...# Environment info
<!-- Everything is optional and where applicable but the more information the better. -->
* Browser, version, OS, platform: Version 107.0.5304.110 (Official Build) snap (64-bit), Ubuntu 20.04 LTS
* Instance URL: shitposter.club es.shitposter.club
* Frontend version (see settings -> about): pleroma-fe@c807254d3eadbd57de292360c5200358261cbc0f pleroma-fe@b13d8f7e6339e877a38a28008630dc8ec64abcdf
* Backend version (see settings -> about): 2.4.53-9048-g0f77643d-shitposterclub 2.4.3
* Browser extensions (ublock, rikaichamp etc): uBlock Origin
* Known instance/user customizations (i.e. pleromafe mods/forks, instance styles etc) -> whatever moon uses
# Bug description & reproduction steps
https://example.to/something.mp3 is detected as a URL
https://example.to/something..mp3 is not
# Bug seriousness
* How annoying it is: not very
* How often does it happen: every time
* How many people does it affect: probably quite a few, but very infrequently
* Is there a workaround for it: hack into the website and change the filename of the remote file
Rationale: RFC 1738 's grammar seems to allow for this ie because it's a url -> httpurl -> hpath -> uchar -> unreserved -> .tusooatusooahttps://git.pleroma.social/pleroma/pleroma/-/issues/3021500 when registering on an instance with approval required2022-12-15T23:07:50Ztusooa500 when registering on an instance with approval required```
staging-pleroma_pleroma.1.hbfzmogn7f69@ruiko | 05:34:11.485 [error] #PID<0.18175.63> running Pleroma.Web.Endpoint (connection #PID<0.18288.63>, stream id 1) terminated
staging-pleroma_pleroma.1.hbfzmogn7f69@ruiko | Server: lm.k...```
staging-pleroma_pleroma.1.hbfzmogn7f69@ruiko | 05:34:11.485 [error] #PID<0.18175.63> running Pleroma.Web.Endpoint (connection #PID<0.18288.63>, stream id 1) terminated
staging-pleroma_pleroma.1.hbfzmogn7f69@ruiko | Server: lm.kazv.moe:80 (http)
staging-pleroma_pleroma.1.hbfzmogn7f69@ruiko | Request: POST /api/v1/accounts
staging-pleroma_pleroma.1.hbfzmogn7f69@ruiko | ** (exit) an exception was raised:
staging-pleroma_pleroma.1.hbfzmogn7f69@ruiko | ** (ArgumentError) Unexpected tuple format, {"test", nil} cannot be formatted into a Recipeint.
staging-pleroma_pleroma.1.hbfzmogn7f69@ruiko |
staging-pleroma_pleroma.1.hbfzmogn7f69@ruiko | The expected format is {name :: String.t() | nil, address :: String.t()}, where address cannot be empty.
staging-pleroma_pleroma.1.hbfzmogn7f69@ruiko |
staging-pleroma_pleroma.1.hbfzmogn7f69@ruiko | (swoosh 1.3.11) lib/swoosh/email/recipient.ex:101: Swoosh.Email.Recipient.Tuple.format/1
staging-pleroma_pleroma.1.hbfzmogn7f69@ruiko | (elixir 1.10.4) lib/enum.ex:1396: Enum."-map/2-lists^map/1-0-"/2
staging-pleroma_pleroma.1.hbfzmogn7f69@ruiko | (swoosh 1.3.11) lib/swoosh/email.ex:359: Swoosh.Email.to/2
staging-pleroma_pleroma.1.hbfzmogn7f69@ruiko | (pleroma 2.4.52-0-g55e37ba80) lib/pleroma/emails/user_email.ex:199: anonymous fn/1 in Pleroma.Emails.UserEmail.approval_pending_email/1
staging-pleroma_pleroma.1.hbfzmogn7f69@ruiko | (pleroma 2.4.52-0-g55e37ba80) lib/pleroma/web/gettext.ex:115: Pleroma.Web.Gettext.with_locales_func/2
staging-pleroma_pleroma.1.hbfzmogn7f69@ruiko | (pleroma 2.4.52-0-g55e37ba80) lib/pleroma/user.ex:910: Pleroma.User.send_user_approval_email/1
staging-pleroma_pleroma.1.hbfzmogn7f69@ruiko | (pleroma 2.4.52-0-g55e37ba80) lib/pleroma/user.ex:890: Pleroma.User.post_register_action/1
staging-pleroma_pleroma.1.hbfzmogn7f69@ruiko | (pleroma 2.4.52-0-g55e37ba80) lib/pleroma/web/twitter_api/twitter_api.ex:53: Pleroma.Web.TwitterAPI.TwitterAPI.create_user/2
staging-pleroma_pleroma.1.hbfzmogn7f69@ruiko |
```tusooatusooahttps://git.pleroma.social/pleroma/pleroma/-/issues/3020SearchController search error on certain users2022-12-14T04:04:53ZRenn AkazaSearchController search error on certain users### Environment
* Installation type (OTP or From Source): OTP
* Pleroma version (could be found in the "Version" tab of settings in Pleroma-FE): v2.4.0, v2.4.4, v2.4.5-2
* Elixir version (`elixir -v` for from source installations, N/A f...### Environment
* Installation type (OTP or From Source): OTP
* Pleroma version (could be found in the "Version" tab of settings in Pleroma-FE): v2.4.0, v2.4.4, v2.4.5-2
* Elixir version (`elixir -v` for from source installations, N/A for OTP): N/A
* Operating system: Alpine Linux
* PostgreSQL version (`psql -V`): 15.1
### Bug description
Certain users cannot be found by searching the full name in the search bar like `@username@instance.tld` (Mastodon v3.5.2). Posting with `@username@instance.tld` mentioned will result in a 500 error. The replies from another user mentioning `@username@instance.tld` WILL present in my timeline, but clicking the username will bring me to the profile page in `instance.tld`.
To filter out the cause, I've tried the followings:
* From same local instance, try searching another user at the same remote instance: working
* From blob.cat (v2.2), trying searching `@username@instance.tld`: working
* From bae.st (v2.4), trying searching `@username@instance.tld`: working
* From a brand new instance I setup in another VPS, try searching `@username@instance.tld`: not working
* Upgrade my instance from v2.4.4 to v2.4.5-2, try searching: not working
* Upgrade PostgreSQL from 14 to 15.5: not working
* Downgrade my instace from v2.4.5-2 to v2.4.0: not working
Here are the logs generated by my server when trying to interact with the user:
Searching:
```
22:41:22.355 [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}
```
Mentioning:
```
22:52:20.531 request_id=xxxxxxxxxxxxxxxxxxxxxx[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"}
22:52:20.531 request_id=xxxxxxxxxxxxxxxxxxxxxx[info] Sent 500 in 1104ms
22:52:20.534 [error] #PID<0.7890.0> running Pleroma.Web.Endpoint (connection #PID<0.7889.0>, stream id 1) terminated
Server: my.server.tld: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.5-2-gd8e32646) 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/-/issues/3017Public Timeline is showing random ancient posts2022-12-25T21:05:53ZLummy ShinePublic Timeline is showing random ancient posts<!--
### 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
* From Source (the MIX_ENV one)
* Pleroma 2.4.3
* ELIXIR 1.13.0
* Debian
* PostgreSQL 11.16
### Bug description
The public timeline is showing posts far older than the recent posts it should be, they dont appear as new, so I dont think the DB is finding them fresh, and they are only in the public timeline.
I had initially assumed that it was a bug that would sort itself out once it caught up but there is no order to it that I can tell, theyre just random 1mo 4mo 1yo etc posts. It puts these old posts above newer posts, after about 4hrs of posts it jumps to an ancient one.
Viewing profiles directly does not have this issue, home timeline doesnt, and neither does TWKN.
I have restarted, updated and such and still have the issue.
(husky shows the same issue, so im assuming its a BE issue)
any help would be appreciated, thankshttps://git.pleroma.social/pleroma/pleroma/-/issues/3016Infinite app registration2023-05-08T00:52:25ZRenat EskeninInfinite app registrationHi, all. I read Pleroma use Mastodon API contract. So, may be it be interested for developers
https://github.com/mastodon/mastodon/issues/21991
I can fill my instance postgres by unconfirmed accounts and spam by confirmation emails. An...Hi, all. I read Pleroma use Mastodon API contract. So, may be it be interested for developers
https://github.com/mastodon/mastodon/issues/21991
I can fill my instance postgres by unconfirmed accounts and spam by confirmation emails. And can fill postgres by creating registered applications (1.5kk apps on mastodon.social now). I didn't find methods to purge this spam from db for Mastodon or any retention policy, but this API has rate limit.https://git.pleroma.social/pleroma/pleroma/-/issues/3015Form for managing blocked / muted shows only 20 accounts2022-12-15T02:25:48ZpiggoForm for managing blocked / muted shows only 20 accountsProbably related to the DOS mitigation that nerfed search, with no way to load more than 20? Now the form is kinda unusable.
Also, oddly, when looking at blocked users, there is a button labelled Block rather than Unblock (same on the m...Probably related to the DOS mitigation that nerfed search, with no way to load more than 20? Now the form is kinda unusable.
Also, oddly, when looking at blocked users, there is a button labelled Block rather than Unblock (same on the mutes page)
this is stable 2.4.4 with stock fe
![Screenshot_20221203_122218](/uploads/519ef02111c160b437f7ff68211bc225/Screenshot_20221203_122218.png)https://git.pleroma.social/pleroma/pleroma/-/issues/3014Jsonrs issues2023-06-07T15:26:27ZZeroJsonrs issues### Environment
* Installation type: Source
* Pleroma version: 2.4.5 stable
* Elixir version: Elixir 1.13.0 (compiled with Erlang/OTP 24)
* Operating system: Ubuntu
* PostgreSQL version: 12.12
### Bug description
So I was looking for...### Environment
* Installation type: Source
* Pleroma version: 2.4.5 stable
* Elixir version: Elixir 1.13.0 (compiled with Erlang/OTP 24)
* Operating system: Ubuntu
* PostgreSQL version: 12.12
### Bug description
So I was looking for ways to speed up Pleroma, and I found [Jsonrs](https://hexdocs.pm/jsonrs/readme.html), the authors claim it to be much faster than Jason and even Jiffy, you can see the graphs in their page.
So anyway, I added it to mix.exs and used the following in my config:
```
config :phoenix, :format_encoders, json: Jsonrs, "activity+json": Jsonrs
config :phoenix, :json_library, Jsonrs
config :postgrex, :json_library, Jsonrs
```
To my surprise, everything seemed to work or so I thought, later I found out anything under the "Settings" menu for admin-fe doesn't seem to work properly when using Jsonrs.
I _think_ I traced the issue to Phoenix not being able to decode the JSON for the settings' descriptions Pleroma sends to it when using Jsonrs, but thats as far I was able to go on my own.
I managed to get a full log of the error by adding `config :logger, truncate: :infinity` to my config, as it was too long and got truncated otherwise.
The log file was upload [here](https://git.pleroma.social/-/snippets/7642/raw/main/jsonrs.log) as it would probably be too long to include in the post.
So what I'm asking is if someone knows how to solve or even work around this issue, because if this Json library is that much faster, it could benefit everyone using Pleroma.https://git.pleroma.social/pleroma/pleroma/-/issues/3012Upgrade Swoosh dependency2022-12-31T06:04:26ZZhuoyun WeiUpgrade Swoosh dependencyNewer version of Swoosh ships a useful adapter [ExAwsAmazonSES](https://hexdocs.pm/swoosh/Swoosh.Adapters.ExAwsAmazonSES.html), which wraps AmazonSES to use dynamic credentials fetched from IAM role. This is particular useful if Pleroma ...Newer version of Swoosh ships a useful adapter [ExAwsAmazonSES](https://hexdocs.pm/swoosh/Swoosh.Adapters.ExAwsAmazonSES.html), which wraps AmazonSES to use dynamic credentials fetched from IAM role. This is particular useful if Pleroma is running in an AWS environment.
Currently the OTP release of Pleroma ships Swoosh 1.3.11, which does not include this adapter. Please consider upgrading Swoosh to a newer version.https://git.pleroma.social/pleroma/pleroma/-/issues/3009TLS issue with remote instance?2022-11-29T17:44:42ZrobinTLS issue with remote instance?My Pleroma instances cannot lookup users on the Mastodon instance at defcon.social, and an account there can lookup but not follow users on my Pleroma instances.
This appears to be a TLS version issue; the following shows up in /var/log...My Pleroma instances cannot lookup users on the Mastodon instance at defcon.social, and an account there can lookup but not follow users on my Pleroma instances.
This appears to be a TLS version issue; the following shows up in /var/log/messages on my instance when one of their users tries to follow one of mine:
`Nov 28 12:09:06 bakunin mix[505650]: 12:09:06.367 [info] POST /users/spike/inbox
Nov 28 12:09:06 bakunin mix[505650]: 12:09:06.381 request_id=FyvYg4vbjf0Vby4AASS
B [warning] Description: 'Authenticity is not established by certificate path va
lidation'
Nov 28 12:09:06 bakunin mix[505650]: Reason: 'Option {verify, verify_peer} a
nd cacertfile/cacerts is missing'
Nov 28 12:09:06 bakunin mix[505650]: 12:09:06.463 [notice] TLS :client: In state
:hello received SERVER ALERT: Fatal - Protocol Version
Nov 28 12:09:06 bakunin mix[505650]: 12:09:06.463 request_id=FyvYg4vbjf0Vby4AASS
B [error] Could not decode user at fetch https://defcon.social/users/us3r1d, {:t
ls_alert, {:protocol_version, 'TLS client: In state hello received SERVER ALERT:
Fatal - Protocol Version\n'}}
Nov 28 12:09:06 bakunin mix[505650]: 12:09:06.466 request_id=FyvYg4vbjf0Vby4AASS
B [info] Sent 400 in 98ms`
The following shows up in /var/log/messages on my instance when one of my users tries to find one of theirs:
`Nov 28 12:18:02 bakunin mix[506229]: 12:18:02.889 [warning] Description: 'Authenticity is not established by certificate path validation'
Nov 28 12:18:02 bakunin mix[506229]: Reason: 'Option {verify, verify_peer} and cacertfile/cacerts is missing'
Nov 28 12:18:02 bakunin mix[506229]: 12:18:02.968 [notice] TLS :client: In state :hello received SERVER ALERT: Fatal - Protocol Version
Nov 28 12:18:02 bakunin mix[506229]: 12:18:02.970 [warning] Description: 'Authenticity is not established by certificate path validation'
Nov 28 12:18:02 bakunin mix[506229]: Reason: 'Option {verify, verify_peer} and cacertfile/cacerts is missing'
Nov 28 12:18:03 bakunin mix[506229]: 12:18:03.042 [notice] TLS :client: In state :hello received SERVER ALERT: Fatal - Protocol Version
Nov 28 12:18:03 bakunin mix[506229]: 12:18:03.210 request_id=FyvY_0hs7zT46yAAAStR [info] Sent 200 in 5397ms`https://git.pleroma.social/pleroma/pleroma/-/issues/3007Current "develop" OTP: Exec format error2022-12-06T09:02:02ZAndreas GroschangCurrent "develop" OTP: Exec format errorI recently updated my instance to develop branch because of constant 500 timeline fetching errors in 2.4.x that appear to have been fixed in develop. I tried out 2.4.5 to see if i still get the problem in that release. It was still broke...I recently updated my instance to develop branch because of constant 500 timeline fetching errors in 2.4.x that appear to have been fixed in develop. I tried out 2.4.5 to see if i still get the problem in that release. It was still broken so i upgraded to develop again. Unfortunately with the latest develop OTP amd64 release i get the dreaded `Exec format error`. As far as i understand, that usually means some CPU architecture mixup. Could you check if all is right with the OTP pleroma.zip ?https://git.pleroma.social/pleroma/pleroma/-/issues/3005Migrate from Mastodon 42022-11-25T21:50:17ZAhmad DakhlallahMigrate from Mastodon 4Hello,
I've tried to migrate from Mastodon to Pleroma but it failed.
I know it's because I'm using a newer Mastodon and Pleroma versions.
Does anyone know of a script that can do so? Or are anyone here ready to do it for me as a paid ...Hello,
I've tried to migrate from Mastodon to Pleroma but it failed.
I know it's because I'm using a newer Mastodon and Pleroma versions.
Does anyone know of a script that can do so? Or are anyone here ready to do it for me as a paid gig?
I belive now that I've made a mistake starting with Mastodon (The most famous one for some reason), but when I tried Pleroma I've knew for sure it was a mistake. Now I have +160 users who trusts my server and they're asking for the things that Pleroma offers without anyway for me to migrate without setting them back to zero.
Anyway, I need a script, or someone to do it as paid service.
Thank you for the wonderful script and thank you, the community people!https://git.pleroma.social/pleroma/pleroma/-/issues/3004Turn emoji react to mention when reacting to a Mastodon post2023-05-08T00:52:48ZpiggoTurn emoji react to mention when reacting to a Mastodon postProvided pleroma knows what server it's federating to and that server is running a software known to not support emoji reacts, how about the react was turned either into a favourite, or to a mention with just the emoji as text?
now you'...Provided pleroma knows what server it's federating to and that server is running a software known to not support emoji reacts, how about the react was turned either into a favourite, or to a mention with just the emoji as text?
now you'd have to check who is running what before reacting
this could be an optional MRF or somethinghttps://git.pleroma.social/pleroma/pleroma/-/issues/3003Move an account from Peroma to Mastodon2022-11-24T10:25:53ZoptikfluffelMove an account from Peroma to MastodonHey there, I found #1526 and wondered wether Pleroma can also do it the other way around.Hey there, I found #1526 and wondered wether Pleroma can also do it the other way around.