yunohost-apps / lemmy_ynh

A link aggregator for the fediverse.

Lemmy for YunoHost

Read this README in other languages.

This package allows you to install Lemmy quickly and simply on a YunoHost server.
If you don't have YunoHost, please consult the guide to learn how to install it.

Overview

Lemmy is similar to sites like Reddit, Lobste.rs, or Hacker News: you subscribe to forums you're interested in, post links and discussions, then vote, and comment on them. Behind the scenes, it is very different; anyone can easily run a server, and all these servers are federated (think email), and connected to the same universe, called the Fediverse.

Shipped version: 0.18.2~ynh3

Demo: https://lemmy.ml/

Screenshots

Documentation and resources

• Official app website: https://join-lemmy.org/
• Official admin documentation: https://join-lemmy.org/docs/en/
• Upstream app code repository: https://github.com/LemmyNet/lemmy
• YunoHost Store: https://apps.yunohost.org/app/lemmy
• Report a bug: https://github.com/YunoHost-Apps/lemmy_ynh/issues

Developer info

Please send your pull request to the testing branch.

To try the testing branch, please proceed like that:

sudo yunohost app install https://github.com/YunoHost-Apps/lemmy_ynh/tree/testing --debug
or
sudo yunohost app upgrade lemmy -u https://github.com/YunoHost-Apps/lemmy_ynh/tree/testing --debug

More info regarding app packaging: https://yunohost.org/packaging_apps

lemmy_ynh's Issues

Error after upgrading to 0.18.1 & 0.18.2

After upgrading to latest 0.18.1 Lemmy Yunohost version, my Lemmy server look like this:

Please update

Currently this is on version 0.18.2. While I don't see 0.18.2 on the official Lemmy repository, 0.18.3 was released nearly a year ago. I'd say this repository is overdue for an update.

We need at least 0.19.0 to get access to third party tools like Voyager and Photon

Thank you for your consideration.

Couldn't Update site error

"Couldn't update site" error when trying to update the Admin Settings in the Site Configuration section of the website as an administrator (to allow federation and which instances to federate with)

Cannot view posts in any mobile app

Describe the bug

When I attempt to log in via Jerboa or Connect for Lemmy on Android (Samsung S21+), I am met with an error when trying to load my posts/feed. The feed remains blank and is unable to be loaded.

Context

• Hardware: Digital Ocean VPN
• YunoHost version: 11.1.21.4 (stable)
• I have access to my server: Through SSH
• Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: no
• Using, or trying to install package version/branch: 0.16.7~ynh2

Steps to reproduce

1. Open up third party lemmy app on phone
2. Log in to your account
3. Try to load any post/community
4. Recieve error message related to BOOLEAN

Expected behavior

I should be able to view and use the app.

Unable to link lemmy instance to other lemmy instances

Describe the bug

There is no documentation or menu item to link my lemmy_ynh instance to other lemmy instances

Context

• Hardware: VM
• YunoHost version: 11.1.20
• I have access to my server: Through SSH | through the webadmin | direct access via keyboard / screen
• Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: no
  • If yes, please explain:
• Using, or trying to install package version/branch: lemmy_ynh 0.16.7~ynh1
• If upgrading, current package version: N/A

Steps to reproduce

1. Try to link lemmy_ynh instance to other instances.
2. No menu GUI items exist to do this.
3. No documentation exists to do this.

Expected behavior

Be able to link my lemmy_ynh instance to other Lemmy instances since it's a federated service using ActivityPub protocol.

Logs

N/A

Other information

Upstream describes how to do this here, https://join-lemmy.org/docs/en/administration/federation_getting_started.html, but it's not working with the yunohost implementation.

ARM support

Currently the YunoHost package only supports amd64, but Lemmy can be compiled and does run on ARM
Potentially useful references:
LemmyNet/lemmy#3102
LemmyNet/lemmy#3972
LemmyNet/lemmy#3180

Lemmy can be installed without Docker, instructions are in its docs now.

https://forum.yunohost.org/t/lemmy-federated-reddit-alternative/14697/5

Lemmy fails to start up automatically after server boots

Describe the bug

This issue is a crosspost from Lemmy fails to start up automatically after server boots. Basically, every time I (re)start my server, I have to start Lemmy manually, either from the services page in the Yunohost admin or the command line. It does not start automatically. It has been at least three weeks since it has started automatically. Start on boot is enabled; at least, that's what it says on the Lemmy service page.

Context

• Hardware: Virtualbox on an old desktop running Ubuntu
• YunoHost version: 11.2.4
• I have access to my server: Through the webadmin and direct access via keyboard / screen.
• Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: No
• Using: Lemmy 0.18.2~ynh1

Steps to reproduce

• Reboot server or start from shut down

Expected behavior

The Lemmy service should start on boot just like the other services.

Logs

Here's an updated log, compared to what I originally shared on the Yunohost forms. I actually restored a 9/20 backup because I was having stability issues since then if you noticed the discrepancy in the dates. Not sure if that problem is related. Anyway, I think this part is the relevant sequence:

-- Boot 56a8946f82314737a3d20ad163f4419f --
Oct 02 19:53:09 systemd[1]: Started Lemmy: Link aggregator.
Oct 02 19:53:16 systemd[1]: lemmy.service: Main process exited, code=exited, status=101/n/a
Oct 02 19:53:16 systemd[1]: lemmy.service: Failed with result 'exit-code'.
Oct 02 20:04:27 systemd[1]: Started Lemmy: Link aggregator.

Lemmy forget Password Capability Not Functioning via email

Describe the bug

Unable to use forget password capability despite email being used when registering a user.
On a stock install of Lemmy from the yunohost app store with only the initially made admin account loaded with a Gmail email address.

Context

• Hardware: Linode Server
• YunoHost version: 11.2.5
• I have access to my server: Yes
• Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: No
• Using, or trying to install package version/branch: 0.18.2~ynh1

Steps to reproduce

1. Create an account on Lemmy Server with an email in addition to username
2. Log-out
3. click forget password at login screen
4. enter email used in registration
5. wait and get no response from Lemmy Front end that an email was sent nor any email arriving in inbox

Expected behavior

1. See prompt that an email was sent to reset password and Receive said email with capability to reset a password for a user

Logs

• Unknown what log would be useful here but please let me know and I'll provide it then.

Uploading images is not possible

Describe the bug

An error message is shown when trying to upload any image (post, community icon, instance icon). The message is the following:

SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data

Context

• Hardware: VPS bought online
• YunoHost version: 11.0.9.14
• I have access to my server: Through SSH | through the webadmin
• Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: no
• Lemmy version: 0.16.7

Steps to reproduce

• Install an instance.
• Try to upload instance icon or banner, or try to upload an image to be posted.

Expected behavior

The instance should be able to accept image uploads.

Logs

Lemmy service log here: https://paste.yunohost.org/uhehososov

Integrate lemmyBB frontend

It would be nice to have lemmyBB as an optional additional frontend.

Lemmy version 0.18.3 released

Newest version, 0.18.3, released today https://github.com/LemmyNet/lemmy/releases/tag/0.18.3

Login page shows 404 error

Describe the bug

A fresh install of the app cannot be accessed by the admin account.
The login page shows a 404 error message:
404 Code: TypeError: Cannot read property 'site' of undefined

When the root domain is accesed (installation domain), the Lemmy Instance Setup is shown asking to create a new admin account. Once created, the account is not allowed to setup the instance because it is not ad admin account.

Context

• Hardware: VPS bought online
• YunoHost version: 4.3.6.2
• I have access to my server: Through SSH | through the webadmin
• Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: no
• Using, or trying to install package version/branch: 0.15.2

Steps to reproduce

Install lemmy app, try to set up the instance.

Expected behavior

The instance should be setup by the admin user chosen in the installation process.

Upgrading causes fetch error "request to http://127.0.0.1:8536/api/v3/site"

Describe the bug

Upgraded lemmy to 0.16.7~ynh4

Now getting error on all pages (I assume the API is down)

404: FetchError: request to http://127.0.0.1:8536/api/v3/site

Context

• Hardware: VPS, 3 core, 4gb ram on Debian
• YunoHost version: 11.1.21.4 (stable)
• I have access to my server: SSH / Admin
• Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: no
• Using, or trying to install package version/branch: 0.16.7~ynh4 (latest)

Steps to reproduce

Hit upgrade in yunohost admin panel

Logs

Check for updates
10:07:34
Upgrade 'Lemmy' app
1
10:07:57
Now upgrading lemmy...
Creating a safety backup prior to the upgrade
Collecting files to be backed up for lemmy...
Declaring files to be backed up...
Backing up the PostgreSQL database...
Backup script completed for lemmy. (YunoHost will then actually copy those files to the archive).
Creating a backup archive from the collected files...
The archive will contain about 358.8MB of data.
Backup created: lemmy-pre-upgrade1
Updating sources...
Updating ports...
Updating system_user...
Updating install_dir...
Updating data_dir...
Updating permissions...
Updating apt...
Updating database...
Stopping a systemd service...
The service lemmy has correctly executed the action stop.
The service lemmy-ui has correctly executed the action stop.
Ensuring downward compatibility...
'/var/www/lemmy/pict-rs' wasn't deleted because it doesn't exist.
Upgrading dependencies...
Upgrading NGINX web server configuration...
Making upgrade...
Updating a configuration file...
Creating pgcrypto extension if needed...
NOTICE: extension "pgcrypto" already exists, skipping
Upgrading systemd configuration...
Upgrading logrotate configuration...
Integrating service in YunoHost...
Starting a systemd service...
The service lemmy has correctly executed the action start.
The service lemmy-ui has correctly executed the action start.
Upgrade of lemmy completed
lemmy upgraded
Upgrade complete

Full logs: https://paste.yunohost.org/raw/ogopuzadub

Edit Lemmy service now failing:

�[2m2023-07-03T00:09:35.962752Z�[0m �[32m INFO�[0m �[1mWorker�[0m�[1m{�[0m�[3mworker.id�[0m�[2m=�[0mf2a90074-f6d4-4797-ab70-d08c59b198e9 �[3mworker.queue�[0m�[2m=�[0mdefault �[3mworker.operation.id�[0m�[2m=�[0m860fab72-9afb-4dd5-83fa-1e23cbd489e0 �[3mworker.operation.name�[0m�[2m=�[0mclosing�[1m}�[0m�[2m:�[0m �[2mbackground_jobs_actix::worker�[0m�[2m:�[0m Worker closing
�[2m2023-07-03T00:09:35.962768Z�[0m �[33m WARN�[0m �[2mbackground_jobs_actix::worker�[0m�[2m:�[0m Not restarting worker, Arbiter is dead
Error: LemmyError { message: Some("Cannot have both private instance and federation enabled."), inner: Cannot have both private instance and federation enabled., context: "SpanTrace" }

-- Journal begins at Thu 2021-08-19 14:46:25 EDT, ends at Sun 2023-07-02 20:17:08 EDT. --
Jul 01 06:25:49 systemd[1]: Started Lemmy: Link aggregator.
Jul 01 06:28:16 systemd[1]: Stopping Lemmy: Link aggregator...
Jul 01 06:28:16 systemd[1]: lemmy.service: Succeeded.
Jul 01 06:28:16 systemd[1]: Stopped Lemmy: Link aggregator.
Jul 01 06:28:19 systemd[1]: Started Lemmy: Link aggregator.
Jul 02 20:08:49 systemd[1]: Stopping Lemmy: Link aggregator...
Jul 02 20:09:19 systemd[1]: lemmy.service: Succeeded.
Jul 02 20:09:19 systemd[1]: Stopped Lemmy: Link aggregator.
Jul 02 20:09:19 systemd[1]: lemmy.service: Consumed 2min 53.564s CPU time.
Jul 02 20:09:35 systemd[1]: Started Lemmy: Link aggregator.
Jul 02 20:09:35 systemd[1]: lemmy.service: Main process exited, code=exited, status=1/FAILURE
Jul 02 20:09:35 systemd[1]: lemmy.service: Failed with result 'exit-code'.

Avatars of users that are new to my instance do not show up following update to 0.18.2~ynh3.

Describe the bug

Avatars of users that are new to my instance do not show up following update to 0.18.2~ynh3. The problem may have to do with the lemmy-pict-rs and/or lemmy-ui services not running.

Context

• Hardware: Virtualbox running on an older Ubuntu desktop.
• YunoHost version: 11.2.9.1
• I have access to my server: through the webadmin and direct access via keyboard / screen
• Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: No.

Steps to reproduce

• Upgrade Lemmy from the command line using sudo yunohost app upgrade lemmy --no-safety-backup. (Apparently, this particular command is necessary because there's a problem with the backup script.)
• Navigate to instance in browser and start scrolling. Notice that familiar avatars display properly, but new users just have blank boxes.

Expected behavior

All users avatars should show up as they did before the update.

Installation or upgrade from 0.11.3~ynh1 to 0.15.2~ynh3 fails due to missing rust-s3 dependency

Describe the bug

Installing new instance or upgrading from the previous version (0.11.3) to latest 0.15.2 fails with the following error:

646737 INFO DEBUG -     Updating crates.io index
646737 INFO DEBUG -     Updating git repository `https://github.com/asonix/rust-s3`
646737 INFO DEBUG - error: failed to get `rust-s3` as a dependency of package `pict-rs v0.3.0-beta.19 (/var/www/build-pict-rs)`
646737 INFO DEBUG -
646737 INFO DEBUG - Caused by:
646737 INFO DEBUG -   failed to load source for dependency `rust-s3`
646737 INFO DEBUG -
646737 INFO DEBUG - Caused by:
646737 INFO DEBUG -   Unable to update https://github.com/asonix/rust-s3?branch=asonix/generic-client#c91e4eca
646737 INFO DEBUG -
646737 INFO DEBUG - Caused by:
646737 INFO DEBUG -   object not found - no match for id (c91e4ecacc8c5a351ff360df68a3cb00863b62bd); class=Odb (9); code=NotFound (-3)

Context

• Hardware: x86_64 server
• YunoHost version: 4.3.6.2
• I have access to my server: SSH, direct, etc.
• Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: No.
• Using, or trying to install package version/branch: https://github.com/YunoHost-Apps/lemmy_ynh/tree/master
• If upgrading, current package version: 0.11.3~ynh1

Steps to reproduce

• If you performed a command from the CLI, the command itself is enough. For example:

  $ sudo yunohost app install https://github.com/YunoHost-Apps/lemmy_ynh/tree/master --debug

or

$ sudo yunohost app upgrade lemmy -u https://github.com/YunoHost-Apps/lemmy_ynh/tree/master --debug

Expected behavior

Installation or upgrade succeeds.

Logs

Full log: https://paste.yunohost.org/raw/nexahidiju

Can't see Lemmy once it's installed.

Hardware: Thinkpad Laptop – Intel i5 – 4GB RAM
YunoHost version: Latest ISO – fresh install
I have access to my server : SSH & Web Admin
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : No
If yes, please explain:

Description of my issue:
When I make a fresh installation of Lemmy, it installs correctly with no error messages. However, when I go to the app list, it's there, but on the user side there is no tile and when I go the subdomain I have created, nothing loads and nothing appears to be there. Am I doing something wrong? :/

Lemmy 0.19.1

Hello, running into issues with version 0.18.2 and was wondering if it’s possible to update to the newer 0.19.1? Thanks for your efforts put into this yunohost package!

https://github.com/LemmyNet/lemmy/releases/tag/0.19.1

Installs wrong architecture on Raspberry Pi

Describe the bug

A valid fresh install on Raspberry Pi installs the x86 binary

Context

• Hardware: Raspberry Pi at home
• YunoHost version: 11.1.21.4
• I have access to my server: *Through SSH | through the webadmin | direct access via keyboard / screen
• Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: no
• Using, or trying to install package version/branch: 0.16.7~ynh3

Steps to reproduce

This was a fresh install from the web UI on a long-term-stable Yunohost instance. Log is below.

Expected behavior

Listing page says all architectures are supported so I expected the ARM version to be installed.

Logs

Service log: https://paste.yunohost.org/leverurugo

Install log:

Installing lemmy...
Provisionning sources...
Provisionning ports...
Provisionning system_user...
Provisionning install_dir...
Provisionning data_dir...
Provisionning permissions...
Provisionning apt...
Provisionning database...
Installing dependencies...
Creating a PostgreSQL database...
Setting up source files...
Configuring NGINX web server...
Making install...
Adding a configuration file...
Configuring a systemd service...
Configuring log rotation...
Integrating service in YunoHost...
Starting a systemd service...
(this may take some time)
The service lemmy didn't fully executed the action start before the timeout.
Please find here an extract of the end of the log of the service lemmy:
Jul 01 09:48:35 systemd[1]: Started Lemmy: Link aggregator.
Jul 01 09:48:35 systemd[1064808]: lemmy.service: Failed to execute /var/www/lemmy/lemmy/lemmy: Exec format error
Jul 01 09:48:35 systemd[1064808]: lemmy.service: Failed at step EXEC spawning /var/www/lemmy/lemmy/lemmy: Exec format error
Jul 01 09:48:35 systemd[1]: lemmy.service: Main process exited, code=exited, status=203/EXEC
Jul 01 09:48:35 systemd[1]: lemmy.service: Failed with result 'exit-code'.
---
The service lemmy-ui has correctly executed the action start.
Installation of lemmy completed
Installation completed

Update to 0.18.2~ynh2 fails

Describe the bug

I attempted to update from 0.18.2ynh1 to 0.18.2ynh2 using the web admin interface, but the update failed.

Context

• Hardware: Virtualbox running on an older Ubuntu desktop.
• YunoHost version: 11.2.9.1
• I have access to my server: through the webadmin and direct access via keyboard / screen
• Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: No.
• If upgrading, current package version: 0.18.2~ynh1

Steps to reproduce

Either update the app from the web interface or command line (sudo yunohost app upgrade).

Expected behavior

Successfully update the Lemmy app to the latest version.

Logs

Log.

Upgrade breaks app

After upgrading app lemmy service fails to start.
Apparently upgrade script does not create pgcrypto database extension.

Log:
https://paste.yunohost.org/iniguhiqon

Upgrade to the latest version

Describe the bug

Lemmy has released a newer version almost one month ago (announcement)

Context

Lemmy has released v0.17.2, while this YunoHost still in version 0.16.7.

Release 0.18.1 fixes a cross-site scripting vulnerability

Release 0.18.1 fixes a cross-site scripting vulnerability
https://github.com/LemmyNet/lemmy/releases/tag/0.18.1

"Additionally this version includes a fix for another cross-site scripting vulnerability. For these reasons instance admins should upgrade as soon as possible." -- https://lemmy.ml/post/1808829

YunoHost documentation for this app link produces HTTP 404 error

Describe the bug

The link YunoHost documentation for this app on the README.md produces a HTTP 404 not found error.

Context

N/A

Steps to reproduce

N/A

Expected behavior

The link would produce the documentation page

Logs

N/A

Services lemmy-pict-rs and lemmy-ui will not start after upgrading to 0.18.2~ynh3..

Describe the bug

Services lemmy-pict-rs and lemmy-ui will not start after upgrading to 0.18.2~ynh3 from 0.18.2~ynh1.

Context

• Hardware: Virtualbox running on an older Ubuntu desktop.
• YunoHost version: 11.2.9.1
• I have access to my server: through the webadmin and direct access via keyboard / screen
• Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: No.
• If upgrading, current package version: 0.18.2~ynh1

Steps to reproduce

• Upgrade Lemmy from the command line using sudo yunohost app upgrade lemmy --no-safety-backup. Apparently, this particular command is necessary because there's a problem with the backup script.
• The update completes, but the above mentioned services fail to start. Attempting to start them manually, either from the command line of the web interface, is unsuccessful.

Expected behavior

All of the Lemmy services should start normally following an upgrade.

Logs

• Upgrade log: https://paste.yunohost.org/raw/bexahetipe
• lemmy-pict-rs log: https://paste.yunohost.org/oyanupicur
• lemmy-ui log: https://paste.yunohost.org/zorujikofi

New version?

Hi!
Do you plan to update app to newer Lemmy version? There is 0.12 now, and it had some meaningfull changes, i.e. federation

Comment links when using the /comment/1234 path error 404

Describe the bug

Comments I make on my Lemmy instance appear to have two formats:

1. mysite.org/post/1234/comment/5678
2. mysite.org/comment/5678

The former resolves fine on my server, but the latter gives a 404 error. Federated comments link to the /comment URL so all links to my comments from remote instances produce a 404.

Context

• Hardware: VPS with Debian 11
• YunoHost version: 11.1.21.4 (stable)
• I have access to my server: SSH & Web
• Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: no

Steps to reproduce

1. Go to a post on a lemmy_ynh instance
2. Post a comment
3. Click on the "Link icon" button and observe mysite.org/post/1234/comment/5678 works
4. Now click on the "Fediverse icon" button and observe mysite.org/comment/5678 produces a 404 error

Expected behavior

Both styles of links should work.