pleroma-support issueshttps://git.pleroma.social/pleroma/pleroma-support/-/issues2023-08-22T15:35:37Zhttps://git.pleroma.social/pleroma/pleroma-support/-/issues/89Request failed with status code 500 - [object Object] on every page in Plerom...2023-08-22T15:35:37ZMorris SilvyaRequest failed with status code 500 - [object Object] on every page in Pleroma/AdminI'm not sure what setting I clicked but navigating to any page on the Admin page is showing the 'Request failed with status code 500 - [object Object]' toast message.
I followed the steps outlined here: https://soapbox.pub/install/ and...I'm not sure what setting I clicked but navigating to any page on the Admin page is showing the 'Request failed with status code 500 - [object Object]' toast message.
I followed the steps outlined here: https://soapbox.pub/install/ and it's installed on Ubuntu.
Attaching the video, which better describes the issue. I am logged in as Admin.
![Request_failed_with_status_code_500_-__object_Object_](/uploads/9163f8f0edcad690e5a7df79dbbbf0dd/Request_failed_with_status_code_500_-__object_Object_.mp4)https://git.pleroma.social/pleroma/pleroma-support/-/issues/87[error] Unable to load crypto library. Failed with error2022-11-26T00:26:25ZBob Ross[error] Unable to load crypto library. Failed with errorget an error when running the config generator and after getting to the hostname part:
[error] Unable to load crypto library. Failed with error:
":load_failed, Failed to load NIF library /opt/pleroma/lib/crypto-4.6.5.4/priv/lib/crypto: ...get an error when running the config generator and after getting to the hostname part:
[error] Unable to load crypto library. Failed with error:
":load_failed, Failed to load NIF library /opt/pleroma/lib/crypto-4.6.5.4/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.
when i install openssl, its says its already installed, i run ubuntu 20.04 on a vps. how would i fix this? thanks!https://git.pleroma.social/pleroma/pleroma-support/-/issues/35Can't get TagPolicy to work2020-07-13T18:41:06ZLykonCan't get TagPolicy to workHello,
I am having trouble getting TagPolicy to work.
Both TagPolicy and SimplePolicy appear to be enabled to the site's "transparency" section, even listing the blocked domains by SimplePolicy.
However, adding a tag to a local user ...Hello,
I am having trouble getting TagPolicy to work.
Both TagPolicy and SimplePolicy appear to be enabled to the site's "transparency" section, even listing the blocked domains by SimplePolicy.
However, adding a tag to a local user via Admin Panel does does nothing. They are added and removed, but they never have any effect and the user is still able, for example, to upload attachments or to be followed by other users.
Am I missing something? Do I need to somehow enable the individual tags?
Is there any way I can troubleshoot this issue?
Thank you!https://git.pleroma.social/pleroma/pleroma-support/-/issues/18MRF request: drop DM deletes2023-05-10T21:18:53ZMew MewMRF request: drop DM deletesI'd like a way to drop deletes of direct messages, so old private conversations aren't lost. Thanks!I'd like a way to drop deletes of direct messages, so old private conversations aren't lost. Thanks!https://git.pleroma.social/pleroma/pleroma-support/-/issues/15How to update adminfe?2019-12-07T15:30:57ZMew MewHow to update adminfe?I build my own PleromaFE, so don't use the included files. AdminFE has recently made some changes, how can I build it and install it in the instance/ folder?I build my own PleromaFE, so don't use the included files. AdminFE has recently made some changes, how can I build it and install it in the instance/ folder?https://git.pleroma.social/pleroma/pleroma-support/-/issues/106federation with threads.net2024-03-21T21:48:03ZLuca Sironifederation with threads.netwith OTP release 2.6.2 it's still not possible to follow threads.net user, given that known and fixed 'outbox issue'.
Is it possible to have that fix on a OTP release ?with OTP release 2.6.2 it's still not possible to follow threads.net user, given that known and fixed 'outbox issue'.
Is it possible to have that fix on a OTP release ?https://git.pleroma.social/pleroma/pleroma-support/-/issues/102browser notification for migrated users has incorrect instance displayed2023-07-02T01:06:59ZJohn Mizerekbrowser notification for migrated users has incorrect instance displayedwhen someone i follow migrates to a new instance, the chrome browser message displays my instance name as the instance that the user migrated to, not the instance name they actually migrated to.when someone i follow migrates to a new instance, the chrome browser message displays my instance name as the instance that the user migrated to, not the instance name they actually migrated to.https://git.pleroma.social/pleroma/pleroma-support/-/issues/101Tab focus not always present2023-06-13T20:35:15ZBilly WolfeTab focus not always presentWhen navigating PleromaFE using just the keyboard with tab, focus is not always apparent. It does come back, but it is apparently somewhat difficult to track visually. This also affects screen reader users, because there are some buttons...When navigating PleromaFE using just the keyboard with tab, focus is not always apparent. It does come back, but it is apparently somewhat difficult to track visually. This also affects screen reader users, because there are some buttons that appear to not be labeled, but when I asked which button I had focused, there was nothing visually there either. I wonder if some of these buttons are missing aria-hidden? Most of where I tested and where this occurs is around the form for posting, after the subject field, and some after the actual post entry box.
There are 2 after the emoji button for the subject box, and also 2 after the "Just landed in L.A. post entry box.https://git.pleroma.social/pleroma/pleroma-support/-/issues/98config Pleroma.Web.WebFinger doesn't work2023-01-04T15:09:50ZClyde Chiconfig Pleroma.Web.WebFinger doesn't workhttps://docs.pleroma.social/backend/configuration/how_to_serve_another_domain_for_webfinger/
I host pleroma at like pleroma.example.org and want users identified by user@example.org.
I followed these instructions, changed Pleroma.Web.W...https://docs.pleroma.social/backend/configuration/how_to_serve_another_domain_for_webfinger/
I host pleroma at like pleroma.example.org and want users identified by user@example.org.
I followed these instructions, changed Pleroma.Web.WebFinger to example.org and kept Pleroma.Web.Endpoint as pleroma.example.org.
Then I find users still identified by user@pleroma.example.org and seems Pleroma.Web.WebFinger config didn't work.
Not sure if I have the right configuration.https://git.pleroma.social/pleroma/pleroma-support/-/issues/97Permissions issue accessing spool file when sending emails2023-01-12T01:14:00ZKamja ImoPermissions issue accessing spool file when sending emailsUsing OTP release 2.5.0 on Debian 11 (bullseye)
Mailer configured with Sendmail using exim4 4.94.2
I am unable to get Pleroma to send any emails successfully. Password resets for example do not work.
When I run `pleroma_ctl email test ...Using OTP release 2.5.0 on Debian 11 (bullseye)
Mailer configured with Sendmail using exim4 4.94.2
I am unable to get Pleroma to send any emails successfully. Password resets for example do not work.
When I run `pleroma_ctl email test --to my@email.com`, a success message is printed, but no email actually goes out, and no logs appear in `/var/log/exim4`. However, I do see the following journalctl entry logged several times for each attempt:
`Jan 02 23:25:01 localhost pleroma[507382]: 2023-01-02 23:25:01 1pCUAv-0027za-OH Failed to create spool file /var/spool/exim4//input//1pCUAv-0027za-OH-D: Permission denied`
This seems like maybe something funky going on with my system, and not an actual issue with Pleroma. Although I will point out that emails do send successfully when I run `su pleroma sendmail my@email.com < test-email.txt`.
Here's my mailer config:
`config :pleroma, Pleroma.Emails.Mailer, [
adapter: Swoosh.Adapters.Sendmail,
cmd_path: "/usr/sbin/sendmail",
enabled: true,
cmd_args: ""]`https://git.pleroma.social/pleroma/pleroma-support/-/issues/96Followers and followings of remote users not shown2023-01-02T20:36:47ZEirik ØverbyFollowers and followings of remote users not shownUser information pages for remote users do not show any "following" or "followers" (other than myself). This is regardless of instance, whether the remote user follows me, etc.
This is Pleroma or installation/config specific; doing the ...User information pages for remote users do not show any "following" or "followers" (other than myself). This is regardless of instance, whether the remote user follows me, etc.
This is Pleroma or installation/config specific; doing the same from other instances (running other software) works fine.
Statuses show as usual.https://git.pleroma.social/pleroma/pleroma-support/-/issues/94Unable to install2022-12-31T06:17:28ZGerry BolgerUnable to installI am installing on Debian and get t this section:
Git clone the PleromaBE repository and make the Pleroma user the owner of the directory:
Using this command:
sudo -Hu pleroma git clone -b stable https://git.pleroma.social/pleroma/ple...I am installing on Debian and get t this section:
Git clone the PleromaBE repository and make the Pleroma user the owner of the directory:
Using this command:
sudo -Hu pleroma git clone -b stable https://git.pleroma.social/pleroma/pleroma /opt/pleroma
I get:
fatal: Could not change back to '/root': Permission denied
I cannot get past this.
Please advise
Many thankshttps://git.pleroma.social/pleroma/pleroma-support/-/issues/90Pleroma Apache Config not working2022-12-06T08:43:13ZMichellePleroma Apache Config not workingHello,
I wanted to install Pleroma on my server, but now I can't access the website. Everytime I try to open it, I get an ERR_SSL_PROTOCOL_ERROR. To be honest, before I tried pleroma, I tried installing Mastodon and got the same error w...Hello,
I wanted to install Pleroma on my server, but now I can't access the website. Everytime I try to open it, I get an ERR_SSL_PROTOCOL_ERROR. To be honest, before I tried pleroma, I tried installing Mastodon and got the same error with apache configs I found online. Does anyone have solutions why I have this problem? The LetsEncrypt ceritifcate works just fine under nginx.
```
# Sample Apache config for Pleroma
#
# Simple installation instructions:
# 1. Install your TLS certificate. We recommend using Let's Encrypt via Certbot
# 2. Replace 'example.tld' with your instance's domain.
# 3. This assumes a Debian-style Apache config. Copy this file to
# /etc/apache2/sites-available/ and then activate the site by running
# 'a2ensite pleroma-apache.conf', then restart Apache.
#
# Optional: enable disk-based caching for the media proxy
# For details, see https://git.pleroma.social/pleroma/pleroma/wikis/How%20to%20activate%20mediaproxy
#
# 1. Create a directory as shown below for the CacheRoot and make sure
# the Apache user can write to it.
# 2. Configure Apache's htcacheclean to clean the directory periodically.
# Your OS may provide a service you can enable to do this automatically.
Define servername social.domain.com
<IfModule !proxy_module>
LoadModule proxy_module libexec/apache24/mod_proxy.so
</IfModule>
<IfModule !proxy_http_module>
LoadModule proxy_http_module libexec/apache24/mod_proxy_http.so
</IfModule>
<IfModule !proxy_wstunnel_module>
LoadModule proxy_wstunnel_module libexec/apache24/mod_proxy_wstunnel.so
</IfModule>
<IfModule !rewrite_module>
LoadModule rewrite_module libexec/apache24/mod_rewrite.so
</IfModule>
<IfModule !ssl_module>
LoadModule ssl_module libexec/apache24/mod_ssl.so
</IfModule>
<IfModule !cache_module>
LoadModule cache_module libexec/apache24/mod_cache.so
</IfModule>
<IfModule !cache_disk_module>
LoadModule cache_disk_module libexec/apache24/mod_cache_disk.so
</IfModule>
ServerName ${servername}
ServerTokens Prod
Protocols h2 http/1.1
# If you want Pleroma-specific logs
ErrorLog /var/log/httpd-pleroma-error.log
CustomLog /var/log/httpd-pleroma-access.log combined
<VirtualHost *:80>
RewriteEngine on
RewriteCond %{SERVER_NAME} =${servername}
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
</VirtualHost>
<VirtualHost *:443>
SSLEngine on
SSLCertificateFile /etc/letsencrypt/live/social.domain.com/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/social.domain.com/privkey.pem
# Make sure you have the certbot-apache module installed
Include /etc/letsencrypt/options-ssl-apache.conf
# Uncomment the following to enable MediaProxy caching on disk
#CacheRoot /tmp/pleroma-media-cache/
#CacheDirLevels 1
#CacheDirLength 2
#CacheEnable disk /proxy
#CacheLock on
#CacheHeader on
#CacheDetailHeader on
## 16MB max filesize for caching, configure as desired
#CacheMaxFileSize 16000000
#CacheDefaultExpire 86400
RewriteEngine On
RewriteCond %{HTTP:Connection} Upgrade [NC]
RewriteCond %{HTTP:Upgrade} websocket [NC]
RewriteRule /(.*) ws://127.0.0.1:4000/$1 [P,L]
#ProxyRequests must be off or you open your server to abuse as an open proxy
ProxyRequests off
ProxyPass / http://127.0.0.1:4000/
ProxyPassReverse / http://127.0.0.1:4000/
ProxyPreserveHost On
</VirtualHost>
```
I also get no errors in the "httpd-pleroma-error.log" file.https://git.pleroma.social/pleroma/pleroma-support/-/issues/85Cannot install on a new Arch box2022-11-19T06:39:12ZDaniel JaouenCannot install on a new Arch boxI am seeing the following error on a new Arch install:
```
[root@localhost pleroma]# su pleroma -s $SHELL -c 'MIX_ENV=prod mix pleroma.instance gen'
warning: `config/prod.secret.exs` not found. You may want to create one by running `mix...I am seeing the following error on a new Arch install:
```
[root@localhost pleroma]# su pleroma -s $SHELL -c 'MIX_ENV=prod mix pleroma.instance gen'
warning: `config/prod.secret.exs` not found. You may want to create one by running `mix pleroma.instance gen`
==> prometheus_ex
Compiling 19 files (.ex)
== Compilation error in file lib/prometheus/registry.ex ==
** (UndefinedFunctionError) function Kernel.Utils.defdelegate/2 is undefined or private. Did you mean:
* defdelegate_all/3
* defdelegate_each/2
(elixir 1.14.0) Kernel.Utils.defdelegate({:exists, [line: 21], [{:name, [line: 21], nil}]}, [])
lib/prometheus/registry.ex:21: (module)
could not compile dependency :prometheus_ex, "mix compile" failed. Errors may have been logged above. You can recompile this dependency with "mix deps.compile prometheus_ex", update it with "mix deps.update prometheus_ex" or clean it with "mix deps.clean prometheus_ex"
[]
```
Any help is greatly appreciated. Thanks in advance!https://git.pleroma.social/pleroma/pleroma-support/-/issues/84Incomplete threads2022-12-02T06:40:40ZGerd FlaigIncomplete threadsIn [this thread](https://social.flaig.name/notice/APff8wmD0WKO6F3agi) on my Pleroma instance I only see two messages, while on the [origin instance](https://w3c.social/@w3c/109354770657801566) there's a whole thread with 6 messages.
I ...In [this thread](https://social.flaig.name/notice/APff8wmD0WKO6F3agi) on my Pleroma instance I only see two messages, while on the [origin instance](https://w3c.social/@w3c/109354770657801566) there's a whole thread with 6 messages.
I would expect all replies to be visible on my Pleroma instance.
Backend Version 2.3.0-1-gb221d77a
Frontend Version c3fcbbd9
(via NixOS-22.05)https://git.pleroma.social/pleroma/pleroma-support/-/issues/82Theme export only saves default colours2023-12-13T06:54:25ZAndy PowellTheme export only saves default coloursWhen saving a theme colour changes are not exported, regardless of the 'keep' settings.
Here's the configuration I wanted to save:
![colourssetup](/uploads/124d238ffdd618a519bce81d9072763b/colourssetup.png)
Having added
`/opt/plerom...When saving a theme colour changes are not exported, regardless of the 'keep' settings.
Here's the configuration I wanted to save:
![colourssetup](/uploads/124d238ffdd618a519bce81d9072763b/colourssetup.png)
Having added
`/opt/pleroma/instance/static/themes/styles.json`
```
{
"pleroma-dark": "/static/themes/pleroma-dark.json",
"pleroma-light": "/static/themes/pleroma-light.json",
"pleroma-amoled": [ "Pleroma Dark AMOLED", "#000000", "#111111", "#b0b0b1", "#d8a070", "#aa0000", "#0fa00f", "#0095ff", "#d59500"],
"classic-dark": [ "Classic Dark", "#161c20", "#282e32", "#b9b9b9", "#baaa9c", "#d31014", "#0fa00f", "#0095ff", "#ffa500" ],
"bird": [ "Bird", "#f8fafd", "#e6ecf0", "#14171a", "#0084b8", "#e0245e", "#17bf63", "#1b95e0", "#fab81e"],
"ir-black": [ "Ir Black", "#000000", "#242422", "#b5b3aa", "#ff6c60", "#FF6C60", "#A8FF60", "#96CBFE", "#FFFFB6" ],
"monokai": [ "Monokai", "#272822", "#383830", "#f8f8f2", "#f92672", "#F92672", "#a6e22e", "#66d9ef", "#f4bf75" ],
"redmond-xx": "/static/themes/redmond-xx.json",
"redmond-xx-se": "/static/themes/redmond-xx-se.json",
"redmond-xxi": "/static/themes/redmond-xxi.json",
"breezy-dark": "/static/themes/breezy-dark.json",
"breezy-light": "/static/themes/breezy-light.json",
"mammal": "/static/themes/mammal.json",
"paper": "/static/themes/paper.json",
"mytheme": "/static/themes/mytheme.json"
}
```
and the json file containing downloaded preset, then set the default name as my theme for the site in `admin/#/settings/frontend -> Theme`
This is the result:
![themeres](/uploads/9fd64d8281d36dc3e45bcc0234ff201a/themeres.png)
and the content of the exported theme if not saved in the output...
![notsaving](/uploads/f5125a59654089ef26f39f89866fe072/notsaving.png)https://git.pleroma.social/pleroma/pleroma-support/-/issues/80Remote Follow Fails2022-11-09T11:30:17ZAndy PowellRemote Follow FailsWhen trying to remote follow a user and filling in the remote follow form, my instance returns an error page![tooterror1](/uploads/5ed8fceca551c0cf6d25185f35938e5a/tooterror1.png)
The url used is along the lines of:
`<my-instance>/osta...When trying to remote follow a user and filling in the remote follow form, my instance returns an error page![tooterror1](/uploads/5ed8fceca551c0cf6d25185f35938e5a/tooterror1.png)
The url used is along the lines of:
`<my-instance>/ostatus_subscribe?acct=https://<remote-instance>/users/<remote-user>`
(where <> encapsulated word are replaced with real world values).
I've googled around and this appeared to be an issue years ago that was apparently fixed. I still have this problem wiht a brand new install from stable sources on 9th November 2022.
Is there anything I need to do in the configuration to fix this or has the 'bug' reappeared.
My instance is behind nginx with ssl
Found this in the log
`
Nov 09 11:14:43 toot mix[1615]: 11:14:43.332 [info] GET /ostatus_subscribe
Nov 09 11:14:43 toot mix[1615]: 11:14:43.392 request_id=FyXmU4El9WYaWJMAByBD [error] Could not decode user at fetch https://mastodonapp.uk/users/BarristerSecret, {:ok, %Tesla.Env{__client__: %Tesla.Client{adapter: {Tesla.Adapter.Hackney, :call, [[]]}, fun: nil, post: [], pre: []}, __module__: Tesla, body: "error code: 1010", headers: [{"date", >
`https://git.pleroma.social/pleroma/pleroma-support/-/issues/76Hide unlisted / answers from timelines per default?2022-06-13T10:46:36ZGrischa BrockhausHide unlisted / answers from timelines per default?Hello. I like how mastodon hides "confusing content" w/o context, like answers in TLs that have to be clicked i.o. to see the context.
I know: When logged in I can adjust that with filters in the frontend. But I would like to configure d...Hello. I like how mastodon hides "confusing content" w/o context, like answers in TLs that have to be clicked i.o. to see the context.
I know: When logged in I can adjust that with filters in the frontend. But I would like to configure defaults. In example I would like to hide answers and unlisted posts from my profile timeline when viewed w/o login.
Do I missing some configuration and this is available to configure for defaults? :smile:https://git.pleroma.social/pleroma/pleroma-support/-/issues/73broken SMTP transport with authentication, and SendInBlue Swoosh Adapter is m...2023-12-13T06:55:15ZTassoman Pigibroken SMTP transport with authentication, and SendInBlue Swoosh Adapter is missingHello there, I can't send mails by SMTP SendInBlue configuration but I've just discovered [Swoosh 1.6.6 has SendInBlue Adapter](https://hexdocs.pm/swoosh/Swoosh.Adapters.Sendinblue.html#content), ready.
How Do I can add it to my mix com...Hello there, I can't send mails by SMTP SendInBlue configuration but I've just discovered [Swoosh 1.6.6 has SendInBlue Adapter](https://hexdocs.pm/swoosh/Swoosh.Adapters.Sendinblue.html#content), ready.
How Do I can add it to my mix compiled by sources?
This is the SMTP error:
```sh
pleroma@hostname:/opt/pleroma$ MIX_ENV=prod mix pleroma.email test
** (UndefinedFunctionError) function :crypto.hmac/3 is undefined or private, use crypto:mac/4 instead
(crypto 5.0.4) :crypto.hmac(:md5, "PASSWORD", "<NUMERIC-ID@smtp-relay.sendinblue.com>")
(gen_smtp 0.15.0) /opt/pleroma/deps/gen_smtp/src/smtp_util.erl:73: :smtp_util.compute_cram_digest/2
(gen_smtp 0.15.0) /opt/pleroma/deps/gen_smtp/src/gen_smtp_client.erl:489: :gen_smtp_client.do_AUTH_each/5
(gen_smtp 0.15.0) /opt/pleroma/deps/gen_smtp/src/gen_smtp_client.erl:452: :gen_smtp_client.try_AUTH/3
(gen_smtp 0.15.0) /opt/pleroma/deps/gen_smtp/src/gen_smtp_client.erl:335: :gen_smtp_client.open_smtp_session/2
(gen_smtp 0.15.0) /opt/pleroma/deps/gen_smtp/src/gen_smtp_client.erl:271: :gen_smtp_client.try_smtp_sessions/3
(gen_smtp 0.15.0) /opt/pleroma/deps/gen_smtp/src/gen_smtp_client.erl:258: :gen_smtp_client.send_it/2
(swoosh 1.3.11) lib/swoosh/adapters/smtp.ex:48: Swoosh.Adapters.SMTP.deliver/2
```
My Pleroma installation is made by sources. Inside `deps.exs` I have this: `{:swoosh, "~> 1.0"},`https://git.pleroma.social/pleroma/pleroma-support/-/issues/72Backend/Admin Settings panel invisible/nonfunctional2022-11-30T19:02:14ZEidolonBackend/Admin Settings panel invisible/nonfunctionalWhen clicking the "settings" menu entry in the admin area, the dropdown arrow moves like it should but nothing appears and no settings are accessible. This is an OTP install, but while in the IRC seeking help, another user noted they had...When clicking the "settings" menu entry in the admin area, the dropdown arrow moves like it should but nothing appears and no settings are accessible. This is an OTP install, but while in the IRC seeking help, another user noted they had the same issue when building from source.
**The System:**
- Pleroma OTP
- Backend 2.4.2
- Frontend b13d8f7e
- running on Debian 10 with all packages up to date
The install was originally configured to not allow config from inside of the DB, but this configuration option was changed immediately after installing. It appears to be a single variable in the config and I don't know why that would be the problem.
**What I've Tried:**
- Restarting instance
- Restarting VPS
- Restarting nginx
- Clearing browser caches
- Changing browsers entirely
- Making sure no scripts are blocked
- Looking at the config file
- Looking at the javascript console to make sure no errors were being thrown
A simple (and ultimately probably fairly useless) gif of the issue is available [here](https://imgur.com/utqq6UJ).