Describe the bug

When I try to backup Friendica, there is an error message and the backup stopps
WARNING - Source path '/etc/cron.d/friendica' does not exist

Manually creating a friendica directory or file in that path doesn't help to backup successfully.

Context

• Hardware: VPS bought online
• YunoHost version: 11.2.4 (stable).
• 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

Steps to reproduce

1.start Friendica backup
2. error message appears

Expected behavior

Backup successful

Logs

WARNING - Source path '/etc/cron.d/friendica' does not exist

https://paste.yunohost.org/raw/gunonofepe

Describe the bug

The problem is, that the worker queue is not getting triggered/executed anymore...
It used to work perfectly fine, but now systemctl status says the following:

var/www/friendica# systemctl status friendica-daemon.service 
● friendica-daemon.service - Friendica daemon
     Loaded: loaded (/etc/systemd/system/friendica-daemon.service; disabled; vendor preset: enabled)
     Active: failed (Result: start-limit-hit) since Wed 2023-06-21 00:38:01 CEST; 5 days ago
   Main PID: 1516554 (code=exited, status=0/SUCCESS)
        CPU: 259ms

Jun 21 00:38:01 tromdienste.de systemd[1]: friendica-daemon.service: Scheduled restart job, restart counter is at 15.
Jun 21 00:38:01 tromdienste.de systemd[1]: Stopped Friendica daemon.
Jun 21 00:38:01 tromdienste.de systemd[1]: friendica-daemon.service: Start request repeated too quickly.
Jun 21 00:38:01 tromdienste.de systemd[1]: friendica-daemon.service: Failed with result 'start-limit-hit'.
Jun 21 00:38:01 tromdienste.de systemd[1]: Failed to start Friendica daemon.
Jun 21 02:53:18 tromdienste.de systemd[1]: /etc/systemd/system/friendica-daemon.service:11: Failed to parse output specifier, ignoring: journalctl

The admin-panel in friendica says the following things:

There is a new version of Friendica. You are currently using version 2023.01, the current version is 2023.09-dev.

The background process (worker) was last executed at 2023-06-20 09:53:39 UTC. That was more than an hour ago. Please check your crontab settings.

The log file 'log/friendica.log' is not writable. Currently no logging is possible (Error: 'Directory "" cannot get created: Invalid path').

Context

• Hardware: VPS bought online
• YunoHost version: 11.1.21.4 (stable)
• 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
  • If yes, please explain:
• Using friendica package version/branch: Friendica 'Giant Rhubarb' 2023.01 - 1502
• Version Friendica 'Giant Rhubarb' 2023.01 - 1502

Steps to reproduce

I installed friendica a while ago and did set up the friendica daemon via the following tutorial: https://nequalsonelifestyle.com/2022/08/04/setting-up-friendica-daemon-systemd-service/

then I also did set up the cronjob as described in the tutorial https://wiki.friendi.ca/docs/install:
*/10 * * * * cd /var/www/friendica; /usr/bin/php bin/worker.php

the current friendica-daemon.service is configured as such:

[Unit]
Description=Friendica daemon
After=network.target mariadb.service
Requires=network.target remote-fs.target nss-lookup.target

[Service]
User=www-data
Group=www-data
WorkingDirectory=/var/www/friendica
Type=simple
StandardError=journalctl
ExecStart=/usr/bin/php ./bin/daemon.php start
ExecStop=/usr/bin/php ./bin/daemon.php stop
PIDFile=friendica/daemon.pid
PrivateTmp=true
InaccessibleDirectories=/home /root /boot /opt /mnt /media
ReadOnlyDirectories=/etc /usr
Restart=always
StartLimitBurst=15
# Restart but not more than once every 10 minutes 
# StartLimitInteraval=600
# Restart, but not more than once every 30s (for testing puropses)
StartLimitInterval=30


[Install]
WantedBy=multi-user.target

Expected behavior

The worker queue to be executed.

Logs

I don't really know why the friendica daemon stopped working. What I found in the logs is the following:

May 13 13:02:53 tromdienste.de php[2643603]: PHP Warning:  Invalid argument supplied for foreach() in /var/www/friendica/src/Worker/UpdateServerDirectory.php on line 96
May 14 01:12:12 tromdienste.de systemd[1]: Stopping Friendica daemon...
May 14 01:12:14 tromdienste.de systemd[1]: friendica-daemon.service: Succeeded.
May 14 01:12:14 tromdienste.de systemd[1]: Stopped Friendica daemon.
May 14 01:12:14 tromdienste.de systemd[1]: friendica-daemon.service: Consumed 1d 3h 8min 56.504s CPU time.
-- Boot 18ee3c68146b441c8df818d697379963 --
May 14 01:16:45 tromdienste.de systemd[1]: Started Friendica daemon.
May 16 03:29:20 tromdienste.de php[962970]: PHP Warning:  Invalid argument supplied for foreach() in /var/www/friendica/src/Worker/UpdateServerDirectory.php on line 96
May 16 13:06:06 tromdienste.de php[1124165]: PHP Warning:  Invalid argument supplied for foreach() in /var/www/friendica/src/Worker/UpdateServerDirectory.php on line 96
May 18 21:23:16 tromdienste.de systemd[1]: /etc/systemd/system/friendica-daemon.service:12: Standard output type syslog is obsolete, automatically updating to journal. Please update yo>
May 19 21:53:17 tromdienste.de php[2801409]: PHP Warning:  Invalid argument supplied for foreach() in /var/www/friendica/src/Worker/UpdateServerDirectory.php on line 96
May 22 22:26:54 tromdienste.de php[175712]: PHP Warning:  Invalid argument supplied for foreach() in /var/www/friendica/src/Worker/UpdateServerDirectory.php on line 96
May 24 21:00:02 tromdienste.de systemd[1]: /etc/systemd/system/friendica-daemon.service:12: Standard output type syslog is obsolete, automatically updating to journal. Please update yo>
May 24 21:00:03 tromdienste.de systemd[1]: /etc/systemd/system/friendica-daemon.service:12: Standard output type syslog is obsolete, automatically updating to journal. Please update yo>
May 27 07:41:31 tromdienste.de php[2257406]: PHP Warning:  Invalid argument supplied for foreach() in /var/www/friendica/src/Worker/UpdateServerDirectory.php on line 96
May 27 07:58:56 tromdienste.de php[2262327]: PHP Warning:  Invalid argument supplied for foreach() in /var/www/friendica/src/Worker/UpdateServerDirectory.php on line 96
May 27 14:46:47 tromdienste.de systemd[1]: Stopping Friendica daemon...
May 27 14:46:48 tromdienste.de systemd[1]: friendica-daemon.service: Succeeded.
May 27 14:46:48 tromdienste.de systemd[1]: Stopped Friendica daemon.
May 27 14:46:48 tromdienste.de systemd[1]: friendica-daemon.service: Consumed 1d 21h 52min 45.016s CPU time.
-- Boot 7d800d72e1134fbab2b2876895be51d3 --
May 27 14:48:08 tromdienste.de systemd[1]: Started Friendica daemon.
May 30 01:01:30 tromdienste.de php[1175059]: PHP Warning:  Invalid argument supplied for foreach() in /var/www/friendica/src/Worker/UpdateServerDirectory.php on line 96
Jun 02 01:30:40 tromdienste.de systemd[1]: /etc/systemd/system/friendica-daemon.service:12: Standard output type syslog is obsolete, automatically updating to journal. Please update yo>
Jun 02 01:30:56 tromdienste.de systemd[1]: /etc/systemd/system/friendica-daemon.service:12: Standard output type syslog is obsolete, automatically updating to journal. Please update yo>
Jun 02 01:33:22 tromdienste.de systemd[1]: /etc/systemd/system/friendica-daemon.service:12: Standard output type syslog is obsolete, automatically updating to journal. Please update yo>
Jun 02 01:33:58 tromdienste.de systemd[1]: /etc/systemd/system/friendica-daemon.service:12: Standard output type syslog is obsolete, automatically updating to journal. Please update yo>
Jun 02 01:34:00 tromdienste.de systemd[1]: /etc/systemd/system/friendica-daemon.service:12: Standard output type syslog is obsolete, automatically updating to journal. Please update yo>
Jun 02 01:34:00 tromdienste.de systemd[1]: /etc/systemd/system/friendica-daemon.service:12: Standard output type syslog is obsolete, automatically updating to journal. Please update yo>
Jun 02 14:55:11 tromdienste.de php[2855047]: PHP Warning:  Invalid argument supplied for foreach() in /var/www/friendica/src/Worker/UpdateServerDirectory.php on line 96

and here is where the worker queue stopped getting executed:

Jun 07 00:06:48 tromdienste.de systemd[1]: /etc/systemd/system/friendica-daemon.service:12: Standard output type syslog is obsolete, automatically updating to journal. Please update yo>
Jun 07 00:06:50 tromdienste.de systemd[1]: /etc/systemd/system/friendica-daemon.service:12: Standard output type syslog is obsolete, automatically updating to journal. Please update yo>
Jun 07 00:06:50 tromdienste.de systemd[1]: /etc/systemd/system/friendica-daemon.service:12: Standard output type syslog is obsolete, automatically updating to journal. Please update yo>
Jun 07 02:15:56 tromdienste.de systemd[1]: Stopping Friendica daemon...
Jun 07 02:15:57 tromdienste.de systemd[1]: friendica-daemon.service: Succeeded.
Jun 07 02:15:57 tromdienste.de systemd[1]: Stopped Friendica daemon.
Jun 07 02:15:57 tromdienste.de systemd[1]: friendica-daemon.service: Consumed 3h 9min 35.189s CPU time.
-- Boot 0f50635c110943f8a8831f6c7300c3c1 --
Jun 07 02:17:30 tromdienste.de systemd[1]: Started Friendica daemon.
Jun 07 02:17:32 tromdienste.de systemd[1]: friendica-daemon.service: Succeeded.
Jun 07 02:17:32 tromdienste.de systemd[1]: friendica-daemon.service: Consumed 1.012s CPU time.
Jun 07 02:17:33 tromdienste.de systemd[1]: friendica-daemon.service: Scheduled restart job, restart counter is at 1.
Jun 07 02:17:33 tromdienste.de systemd[1]: Stopped Friendica daemon.
Jun 07 02:17:33 tromdienste.de systemd[1]: friendica-daemon.service: Consumed 1.012s CPU time.
Jun 07 02:17:33 tromdienste.de systemd[1]: Started Friendica daemon.
Jun 07 02:17:33 tromdienste.de systemd[1]: friendica-daemon.service: Succeeded.
Jun 07 02:17:33 tromdienste.de systemd[1]: friendica-daemon.service: Scheduled restart job, restart counter is at 2.
Jun 07 02:17:33 tromdienste.de systemd[1]: Stopped Friendica daemon.
Jun 07 02:17:33 tromdienste.de systemd[1]: Started Friendica daemon.
Jun 07 02:17:34 tromdienste.de systemd[1]: friendica-daemon.service: Succeeded.
Jun 07 02:17:34 tromdienste.de systemd[1]: friendica-daemon.service: Scheduled restart job, restart counter is at 3.
Jun 07 02:17:34 tromdienste.de systemd[1]: Stopped Friendica daemon.
Jun 07 02:17:34 tromdienste.de systemd[1]: Started Friendica daemon.
Jun 07 02:17:34 tromdienste.de systemd[1]: friendica-daemon.service: Succeeded.
Jun 07 02:17:35 tromdienste.de systemd[1]: friendica-daemon.service: Scheduled restart job, restart counter is at 4.
Jun 07 02:17:35 tromdienste.de systemd[1]: Stopped Friendica daemon.
Jun 07 02:17:35 tromdienste.de systemd[1]: Started Friendica daemon.
Jun 07 02:17:35 tromdienste.de systemd[1]: friendica-daemon.service: Succeeded.
Jun 07 02:17:35 tromdienste.de systemd[1]: friendica-daemon.service: Scheduled restart job, restart counter is at 5.
Jun 07 02:17:35 tromdienste.de systemd[1]: Stopped Friendica daemon.
Jun 07 02:17:35 tromdienste.de systemd[1]: friendica-daemon.service: Start request repeated too quickly.
Jun 07 02:17:35 tromdienste.de systemd[1]: friendica-daemon.service: Failed with result 'start-limit-hit'.
Jun 07 02:17:35 tromdienste.de systemd[1]: Failed to start Friendica daemon.

If anyone can help, I would be so glad, because my posts are not getting sent out at the moment I think.

Today I saw the the update to 2022-12-ynh1 and did it.

• My theme was removed
• Addons I added where removed too
• I am no admin anymore (local config was reverted)

Why are these things done while upgrading?

But I am missing features from 2022-12.

• When I look into the yunohost application list, Friendica is listed as 2022.12~ynh1.
• But when I look into the admin menu of the installed friendica it shows version "Friendica 'Giant Rhubarb' 2023.03-dev - 1502"
  What is happening here? What version is that? 2023-03? A time traveler? :-D

does someone understand this log please ?
and how to fix it ?

have a good day o/

# tail -f /var/log/friendica.log

2021-12-29T08:50:04Z worker [ERROR]: DB Error {"code":1264,"error":"Out of range value for column 'registered-users' at row 1","callstack":"DBA::update, GServer::detect, GServer::check, UpdateGServer::execute, Worker::execFunction, Worker::execute, Worker::processQueue","params":"UPDATE `gserver` SET `detection-method` = 16, `site_name` = 'The Entire World', `info` = 'You think your fake numbers are impressive? Well, this instance contains all living humans.', `platform` = 'mastodon', `version` = '2.9.2+antifa', `network` = 'apub', `registered-users` = 7823881432, `directory-type` = 0, `poco` = '', `url` = 'https:\/\/you-think-your-fake-numbers-are-impressive.well-this-instance-contains-all-living-humans.lubar.me', `nurl` = 'http:\/\/you-think-your-fake-numbers-are-impressive.well-this-instance-contains-all-living-humans.lubar.me', `next_contact` = '2022-01-05 08:50:04', `last_contact` = '2021-12-29 08:50:04', `failed` = 0 WHERE (`nurl` = 'http:\/\/you-think-your-fake-numbers-are-impressive.well-this-instance-contains-all-living-humans.lubar.me')"} - {"file":"Database.php","line":766,"function":"e","uid":"26d0aa","process_id":16442}
2021-12-29T09:00:04Z worker [ERROR]: DB Error {"code":1264,"error":"Out of range value for column 'registered-users' at row 1","callstack":"DBA::update, GServer::detect, GServer::check, UpdateGServer::execute, Worker::execFunction, Worker::execute, Worker::processQueue","params":"UPDATE `gserver` SET `detection-method` = 16, `site_name` = 'The Entire World', `info` = 'You think your fake numbers are impressive? Well, this instance contains all living humans.', `platform` = 'mastodon', `version` = '2.9.2+antifa', `network` = 'apub', `registered-users` = 7823882912, `directory-type` = 0, `poco` = '', `url` = 'https:\/\/you-think-your-fake-numbers-are-impressive.well-this-instance-contains-all-living-humans.lubar.me', `nurl` = 'http:\/\/you-think-your-fake-numbers-are-impressive.well-this-instance-contains-all-living-humans.lubar.me', `next_contact` = '2022-01-05 09:00:04', `last_contact` = '2021-12-29 09:00:04', `failed` = 0 WHERE (`nurl` = 'http:\/\/you-think-your-fake-numbers-are-impressive.well-this-instance-contains-all-living-humans.lubar.me')"} - {"file":"Database.php","line":766,"function":"e","uid":"1e69bf","process_id":18200}

Check it out https://github.com/friendica/friendica/releases/tag/2022.10 - it fixes some performance issues among other bugs. If you guys could update since this uses the git?

I have upgraded my friendica and upgraded to 2022.12-dev .... despite the package being labeled as 2022.10~ynh1. Please see where the mistake is in pulling the friendica files. You should pull from stable.

Since you changed to git, will a force upgrade update it to the latest Friendica? We are 2 versions behind with Friendica and the devs pushed some very important security updates. Thanks!

Describe the bug

After installation : login url and url shown in email are bad ( no domain)

Context

• Hardware: Old omputer.
• YunoHost version: 11.0.10.1
• 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: Friendica 2022.06~ynh1
• If upgrading, current package version: can be found in the admin

Steps to reproduce

Via admin :

• Set up a new domain
• Set up letsencrypt
• Set up all DNS
• On this domain : setup friendica with a specific admin
• Open a private browser : open the domain link
• Log in with your selected admin user email
• Wait
  • receive an email with Localisation du site : http:// only
  • Get a 504 on browser
  • Reload : try to connect : redirected to https://login/
  • reload : check source : it's the action url

Expected behavior

https:// must be https://friendica.example.org

Partial mail content

Cher Shnoulle,
Merci pour votre inscription sur Friendica Social Network.
Votre compte a été créé.
Les informations de connexion sont les suivantes :

Localisation du site : http://
Nom d'utilisateur : shnoulle
Mot de passe : random1234

Vous pouvez changer votre mot de passe depuis la page "Paramètres" de votre compte après vous êtreconnecté.

The .htconfig has no admin email
$a->config['admin_email'] = '';

You cannot go to administration of your friendica,

Hi,

Please can this be upgraded to the latest version of Friendica... Their site says Jan 2019 is latest stable release.

Describe the bug

When upgrading Friendica via CLI, upgrade fails, saying a 'git' command "returned non-zero exit status 128".

Context

• Hardware: Old computer
• YunoHost version: 11.1.20
• I have access to my server: Through SSH and admin panel, plus direct access to physical server if needed
• 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: friendica_ynh 2023.01~ynh1
• If upgrading, current package version: friendica_ynh 2022.10~ynh1

Steps to reproduce

sudo yunohost app upgrade friendica

Expected behavior

Friendica upgrades to the latest version.

Logs

Info: Now upgrading friendica...
Error: Command '['git', 'ls-remote', '--symref', 'https://github.com/YunoHost-Apps/friendica_ynh', 'HEAD']' returned non-zero exit status 128.
Error: Could not fetch source files, is the URL correct?

Hi everyone,

I have a fresh yunohost install and wanted to try Friendica (again). Still, no chance to login as administrator. How does it exactly work?

Yunohost says:
"For admin rights: When installation is complete, you will need to visit your domain page and login with the admin account username and password which was entered at the time of installation process. You can then create your profile and access the admin panel."

I have tried this several times with variants like email address as username, but it only restarts the page.

Has this still something to do with LDAP auth?

Regards,

Stefan

I just tested with my YNH, all updated, but still installs the old version.

I run an instance with some 800 users and my CPU went from 70% to 30% after we did this change and it is easy to do. Would you be interested?

This is the tutorial about how to do that https://nequalsonelifestyle.com/2022/08/04/setting-up-friendica-daemon-systemd-service/ - we tested it and it is quite easy to do.

The Problems:

Big database equals issues.

If the Friendica instance is very active/big then one cannot backup the database since by the time the database is created it will be modified. So it will fail like here https://paste.yunohost.org/raw/icukubaxiz

2023-09-11 00:23:05,769: WARNING - mysqldump: Error 1412: Table definition has changed, please retry transaction when dumping table `post-delivery` at row: 0`.

Currently we tried to put the instance into Maintenance before backing up the databse, see https://github.com/YunoHost-Apps/friendica_ynh/blob/master/scripts/backup (cd $install_dir && ynh_exec_as "$app" php$phpversion bin/console maintenance 1) - but for one it does not work, it won't trigger the maintenance. And second, it is not a good practice to put an instance into maintenance every day, for possibly hours.

We need to backup files too!

Friendica allows admins to store the media files in a folder rather than the database, and this is crucial for big instances. The setting is changed from here:

And it is written in the database as

MariaDB [friendica]> select * from config where cat like '%storage%';
+------+---------+-----------------+-------------------------------+
| id   | cat     | k               | v                             |
+------+---------+-----------------+-------------------------------+
| 6778 | storage | filesystem_path | s:21:"/path/to/storage";      |
| 6796 | storage | name            | s:10:"Filesystem";            |
+------+---------+-----------------+-------------------------------+

Solution:

We need to backup the database properly plus the files.

First, we should use mariadb backups that are incremental so no need to put Friendica in maintenance.

$ mariabackup --backup \
   --target-dir=/var/mariadb/backup/ \
   --user=mariabackup --password=mypassword

More info here https://mariadb.com/kb/en/full-backup-and-restore-with-mariabackup/

Second, we need to define somewhere the file storage path to then include in the backup script.

Any help with this please? I will do my best to test stuff and help, but my knowledge is limited. We desperately need a proper backup solution for friendica!

Hello,

I have tried the branch vFriendica_2018.05 but after that a got this error with baikal :

[06-Jun-2018 20:33:33] WARNING: [pool baikal] child 13920 said into stderr: "NOTICE: Access to the script '/var/www/baikal/html//cal.php/addressbooks/user/callendar/' has been denied (see security.limit_extensions)"

I have temporary moved the file 20-friendica.ini and friendica.conf to fix this issue.

Actually Friendica 3.6 is released. So could you update the package to this version ?

Not a real issue, just wanted to let you know: the Friendica project now has an archive for released versions holding the friendica-full and friendica-addons archives as tar.gz files. Maybe you can use that location for downloading the packages.

The filenames will stay in the current schema friendica-full-[VERSION}.tar.gz and friendica-addons-{VERSION}.tar.gz . Checksums are available in the *.sum256 files.

After upgrading to the lastet version I got the following error in my logs and the page stays white.

https://paste.yunohost.org/oqevafiyid

Currently we use ynh_mysql_dump_db and we put friendica into maintenance before doing that, else for large databases it will fail to backup. However that means if you do daily backups you'll have your network in maintenance mode for 30 min to an hour or more a day. This is not good.

But we can backup with mariadb that does incremental backups - https://mariadb.com/kb/en/full-backup-and-restore-with-mariabackup/

However I do not know how we can do it through YNH.

Hi
As the app have Ldap support its dangerous to use the app without Fail2ban.
Having Fail2ban support would be great addition for the app.

Describe the bug

<path_to_install_root>/log/friendica.log is missing after a fresh install

Context

• Hardware: VPS bought online
• YunoHost version:

yunohost: 
  repo: stable
  version: 4.3.4.2
yunohost-admin: 
  repo: stable
  version: 4.3.2.3
moulinette: 
  repo: stable
  version: 4.3.2.2
ssowat: 
  repo: stable
  version: 4.3.2.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:

name: Friendica
version: 2021.09~ynh1

Steps to reproduce

no log folder in /var/www/friendica/

Expected behavior

/var/www/friendica/log/friendica.log should exists, with ownership friendica:www-data

• it could be a ln -s to /var/log/friendica.log
• it should be managed via logrotate

• Hardware: VPS bought online
• YunoHost version: 4.2.6.1 (stable).
• I have access to my server: Through SSH | through the webadmin | direct access via keyboard / screen | ...

Ok so here are the logs https://paste.yunohost.org/raw/ocadocefiw

After the upgrade a few things happened:

1. I lost the Admin access. As simple as that I had no admin rights.
2. No local photos were displaying, only photos coming from other servers.
3. The custom themes from friendica/view/frio/scheme that I made were deleted

I had to restore to a previous Friendica, the one before the git upgrade.

I discovered in the upgrade script in line 45 at each upgrade we remove everything. Is it a really a good practice because we have some which is useful (by example in $finalpath/proxy and $finalphat/photo ).

Hello,

I did the migration to debian stretch. Actually I have a problem with your package. While I try to a un upgrade the package with the vFriendica_2018.05 branch I get this :

+ pkg_dependencies='php7.0-cli php7.0-imagick php7.0-gd php7.0-mcrypt'
++ lsb_release --codename --short
+ '[' stretch '!=' jessie ']'
+ pkg_dependencies='php7.0-cli php7.0-imagick php7.0-gd php7.0-mcrypt php-xml'
+ ynh_install_app_dependencies php7.0-cli php7.0-imagick php7.0-gd php7.0-mcrypt php-xml
+ local 'dependencies=php7.0-cli php7.0-imagick php7.0-gd php7.0-mcrypt php-xml'
+ local 'dependencies=php7.0-cli, php7.0-imagick, php7.0-gd, php7.0-mcrypt, php-xml'
+ local 'dependencies=php7.0-cli, php7.0-imagick, php7.0-gd, php7.0-mcrypt, php-xml'
+ local manifest_path=../manifest.json
+ '[' '!' -e ../manifest.json ']'
++ cut -d '"' -f 4
++ grep '\"version\": ' ../manifest.json
+ local version=2018.05
+ '[' 7 -eq 0 ']'
+ local dep_app=friendica
+ cat
+ ynh_package_install_from_equivs /tmp/friendica-ynh-deps.control
+ local controlfile=/tmp/friendica-ynh-deps.control
+ ynh_package_is_installed equivs
+ dpkg-query -W -f '${Status}' equivs
+ grep -c 'ok installed'
++ grep '^Package: ' /tmp/friendica-ynh-deps.control
++ cut '-d ' -f 2
+ local pkgname=friendica-ynh-deps
++ grep '^Version: ' /tmp/friendica-ynh-deps.control
++ cut '-d ' -f 2
+ local pkgversion=2018.05
+ [[ -z friendica-ynh-deps ]]
+ [[ -z 2018.05 ]]
+ ynh_package_update
+ ynh_apt update
+ DEBIAN_FRONTEND=noninteractive
+ sudo apt-get -y update
Ign:1 http://ftp.ch.debian.org/debian stretch InRelease
Atteint:2 http://security.debian.org stretch/updates InRelease
Atteint:3 http://forge.yunohost.org/debian stretch InRelease
Atteint:4 http://ftp.ch.debian.org/debian stretch-updates InRelease
Atteint:5 http://ftp.ch.debian.org/debian stretch Release
Lecture des listes de paquets…
++ mktemp -d
+ local TMPDIR=/tmp/tmp.AyXIrOjVg1
+ echo 10
+ cp /tmp/friendica-ynh-deps.control /tmp/tmp.AyXIrOjVg1/control
+ cd /tmp/tmp.AyXIrOjVg1
+ equivs-build ./control
+ sudo dpkg --force-depends -i ./friendica-ynh-deps_2018.05_all.deb
(Lecture de la base de données... 91991 fichiers et répertoires déjà installés.)
Préparation du dépaquetage de .../friendica-ynh-deps_2018.05_all.deb ...
Dépaquetage de friendica-ynh-deps (2018.05) sur (2018.05) ...
dpkg: friendica-ynh-deps : problèmes de dépendances, mais configuration comme demandé :
 friendica-ynh-deps dépend de php7.0-imagick ; cependant :
  Le paquet php7.0-imagick n'est pas installé.

Paramétrage de friendica-ynh-deps (2018.05) ...
+ ynh_package_install -f

I think you need to adapt your dependances for debian stretch maybe. You probably need to replace php5-imagick by php-imagick

Hello

I have tried to upload images in Friendica and I get Nginx 404 not found when I try to open it after upload.

We have asked in a previous post to update to 2021.04 and you did so thank you! It just so happened that Friendica released a new version today which ads support for the Mastodon API, which means Friendica can be used with any Mastodon client. Which is really useful for people who use smartphones. So, if possible to upgrade to the newest one...that'd be great! Thanks again!

https://git.friendi.ca/friendica/friendica/src/branch/stable/CHANGELOG

The app is currently v2020.03.

Friendica v2020.09 has been released, so the install script needs to be updated appropriately.

Apparently, 2020.07 has an issue with PHP 7.0. Newer versions of PHP are apparently supported by Debian Buster, which YunoHost 4.0 now runs on.

Hello,

I saw that when we upgrade friendica to the version 2019.01 we need to update the database. To do that I did it manually in the admin pannel. But I think it could be useful to do that automatically on the upgrade or to add this information in the README.

Hello, had posted on yunohost matrix but was asked to place here. Installed Friendica ensured all php dependencies were present and accounted for. I had restored a DB from a working server but move to a different provider. On the current installation, I am receiving email for a post that I had subscribed to. But i have a number of contacts which I have selected to send email alert. I am no longer receiving those emails. As noted I was provided some guidance on the matrix room but only got to the point where I am able to get the one alert for selected post but not when contacts post. If you can provide a step in the right direction would be more than have to TS further to validate app issue or if this is a config item on my part to help others from making the same mistake . :-)

Thanks in advance!

Hi!
I can't be sure that this problem belongs to Yunohost (rather than Friendica) but it seemed like I should ask here.

I’ve just installed Yunohost (11.2.1) on a Linode VPS (4 GB RAM) running Debian 11. I then installed Friendica (2023.01~ynh1), apparently successfully, on friendica.mydomain.org. Documentation indicates that, as administrator, I should be able to login using my Yunohost admin login (or email address) and password. When I attempt to do so, however, the Friendica login page takes me to https://login/ – which, of course, doesn’t exist. When I attempted to sign up for a new login (providing different login name and email address) the registration page sent me to https://friendica which displayed as a blank page.

Friendica seems to be installed and running – but the login (and registration) screens don’t work. Clicking on the information icon on the login screen shows:

This is Friendica, version 2023.01 that is running at the web location http://. The database version is 1502/1502, the post update version is 1484/1484.

(note that it isn't picking up the web location...)

Installed addons/apps: ldapauth

I checked Services. Yunohost installed Friendica using:

nginx
php7.4-fpm
10.5.19-MariaDB-0+deb11u2

Since 2021.09 install :

• no problem on desktop nor firefox/chrome android version in "desktop mode"
• but either firefox/chrome mobile version gives "502 Bad Gateway" error.

Context

• Hardware: *VPS bought online
• YunoHost version: 4.2.8.3
• 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

New version was released...

please update to 2023.05, because with the release a security fix was played out.

...of Friendica “Giant Rhubarb" 2023.05. This release contains a security fix of a problem @kstrauser pointed out, we strongly encurage all admins to update their nodes.

https://github.com/friendica/friendica/releases/tag/2023.05

Hello !

This is a friendly automatic notice from the Yunohost Apps team : our tool noticed that this app is listed in the community/official app lists - but this app appears to be inactive.

Hence, this issue was created automatically to check if this app is still actively maintained.

You are the current maintainer ? 👷‍♂️ 👷‍♀️

You still actively maintain this app ? 🎉

Please close this issue to signify that you still actively maintain this app. Nothing else, and thank you for your work ❤️ !

You don't intend to maintain this app anymore ? 😢

Either don't do anything, or add a comment to explicitly state that you do not intend / have time / ... to maintain this app (but thanks for your work so far ! 😘). After 15 days, if this issue is still opened, the app will be considered unmaintained.

You wish to become the new maintainer of this app ? 😄

You are welcome and free to comment in this thread that you wish to become the new maintainer, and/or to create the corresponding pull request to fix this issue ! (If you do not already have commit rights on this repo, we can then arrange things with the rest of the app team. 😉) Once this issue is closed, the app will then be flagged again as maintained !

Was happy to see that Friendica is being maintained now. Tried to install it without luck, though. Here are the logs:

https://paste.yunohost.org/raw/xusocobecu

The install is currently failing because of php-mcrypt missing (which probably can be safely remove).

Also I doubt that we need to keep the "php5" stuff, the app is probably not installable on jessie anymore anyway, considering that the upstream now requires php7.x and that the app scripts seem to be using recent helpers ? So the manifest.json should be updated to require Yunohost >= 3.x

The 19.04 version of friendica is out.

Is it possible to upgrade the package

Here's the entire log https://paste.yunohost.org/raw/iqinozabiw

I wanted to let you know that I have upgraded with:

sudo yunohost app upgrade friendica -u https://github.com/YunoHost-Apps/friendica_ynh/tree/testing --debug

All works well. Here is the debug info https://paste.trom.tf/kiruremupo.yaml

The warnings seem to be related to the custom changes I made to some PHP FPM files.

I am monitoring my instance. We have over 500 users. So far it seems fine.

Is there any reason this is using the friendica addons from development?
git clone --quiet https://github.com/friendica/friendica-addons.git -b develop "$final_path/addon"

Steps to reproduce:

1. Install Friendica Application
2. Set User1 as Admin
3. Log in as User1
4. Change e-mail address to a different one
5. The admin settings icon disappears

Tried to change the e-mail back and it gives the error

Cannot change to that email.

Only solution seems to be to uninstall and re-install.

A workaround is to use a dedicated admin user for Friendica and do not change the e-mail address.

Another workaround is to manually change the local.config.php file:

'admin_email' => ...

Describe the bug

An attempt to upgrade from previous version unsuccessful with internal error (cannot backup previous version).

Context

• Hardware: *Old laptop or computer *
• YunoHost version: 11.0.10.2
• 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

Previous version: 2022.06~ynh1

Upgrading to: 2022.10~ynh1

Steps to reproduce

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

  sudo yunohost app upgrade friendica

• If you used the webadmin, please perform the equivalent command from the CLI first.
  DONE

Logs

Logs: https://paste.yunohost.org/raw/uhuhidosid
Error message from GUI

Hello,

When I tried to upgrade friendica I got a corrupt source error : here is my result of my checksum :

➜  /tmp wget -nv -O app.zip https://github.com/friendica/friendica/archive/2018.09.zip
2018-10-09 21:42:15 URL:https://codeload.github.com/friendica/friendica/zip/2018.09 [17761168] -> "app.zip" [1]
➜  /tmp md5sum app.zip 
ab58be32f7bedcc41e124b6b77ebc427  app.zip

Basically it is because the database changes while it is preparing for a backup, from what I understand.

2023-08-19 00:35:12,150: WARNING - mysqldump: Error 1412: Table definition has changed, please retry transaction when dumping table inbox-entry at row: 0

Full log here https://paste.yunohost.org/raw/duceyedari

Can't we do it in a different way? Like put Friendica in maintenance mode then do a backup?

This URL...

https://github.com/friendica/friendica/blob/master/INSTALL.txt

Must be replaced by this one:

https://github.com/friendica/friendica/blob/develop/doc/Install.md

I see this warning in the admin panel:
Your table_definition_cache is too low (400). This can lead to the database error "Prepared statement needs to be re-prepared". Please set it at least to 405 (or -1 for autosizing). See here for more information.

I've been talking to friendica's admins and devs here https://social.trom.tf/display/dbc8dc44-1360-3da1-2dc9-0f7804630652 but it was suggested that I also ask you here since this is a Friendica ynh install. To increase the table_definition_cache what file I should change and how. Can you please help? Cheers!

The app fails when I try to reset my password.

steps

Use the "reset password" link, and click on the link received by mail.

After a while, the page stops loading (still blank) and I have these logs with yunohost service log php7.0-fpm:

- [16-Dec-2019 21:03:24] WARNING: [pool friendica] child 6153, script '/var/www/friendica//index.php' (request: "GET /index.php?pagename=/lostpass/grartaubaixe1731") executing too slow (5.349857 sec), logging
  - [16-Dec-2019 21:03:24] NOTICE: child 6153 stopped for tracing
  - [16-Dec-2019 21:03:24] NOTICE: about to trace 6153
  - [16-Dec-2019 21:03:24] NOTICE: finished trace of 6153
  - [16-Dec-2019 21:03:25] WARNING: [pool friendica] child 6153 said into stderr: "NOTICE: PHP message: PHP Fatal error:  Uncaught ParagonIE\Certainty\Exception\BundleException: No valid bundles were found in the data directory. in /var/www/friendica/vendor/paragonie/certainty/src/Fetch.php:85"
  - [16-Dec-2019 21:03:25] WARNING: [pool friendica] child 6153 said into stderr: "Stack trace:"
  - [16-Dec-2019 21:03:25] WARNING: [pool friendica] child 6153 said into stderr: "#0 /var/www/friendica/vendor/divineomega/password_exposed/src/PasswordExposedChecker.php(72): ParagonIE\Certainty\Fetch->getLatestBundle()"
  - [16-Dec-2019 21:03:25] WARNING: [pool friendica] child 6153 said into stderr: "#1 /var/www/friendica/vendor/divineomega/password_exposed/src/PasswordExposedChecker.php(45): DivineOmega\PasswordExposed\PasswordExposedChecker->getBundleFromCertainty()"
  - [16-Dec-2019 21:03:25] WARNING: [pool friendica] child 6153 said into stderr: "#2 /var/www/friendica/src/Model/User.php(299): DivineOmega\PasswordExposed\PasswordExposedChecker->__construct(Object(GuzzleHttp\Client), Object(DivineOmega\DOFileCachePSR6\CacheItemPool))"
  - [16-Dec-2019 21:03:25] WARNING: [pool friendica] child 6153 said into stderr: "#3 /var/www/friendica/src/Model/User.php(347): Friendica\Model\User::isPasswordExposed('Glalfeat8751')"
  - [16-Dec-2019 21:03:25] WARNING: [pool friendica] child 6153 said into stderr: "#4 /var/www/friendica/mod/lostpass.php(133): Friendica\Model\User::updatePassword(2, 'Glalfeat8751')"
  - [16-Dec-2019 21:03:25] WARNING: [pool friendica] child 6153 said into stderr: "#5 /var/www/friendica/mod/lostpass.php(108): lostpass_generate_password(Array)"
  - [16-Dec-2019 21:03:25] WARNING: [pool friendica] child 6153 said into stderr: "#6 /var/www/f..."

Please let me know if I can provide more info.

Describe the bug

Ater 1st login, try to upload a jpg file for profile
Get an error

Exception produite dans /var/www/friendica/src/Module/Settings/Profile/Photo/Crop.php:175
Stack trace:
#0 /var/www/friendica/src/BaseModule.php(239): Friendica\Module\Settings\Profile\Photo\Crop->content()
#1 /var/www/friendica/src/App.php(712): Friendica\BaseModule->run()
#2 /var/www/friendica/index.php(44): Friendica\App->runFrontend()
#3 {main}

Context

• Hardware: Old omputer.
• YunoHost version: 11.0.10.1
• 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: Friendica 2022.06~ynh1

Steps to reproduce

After log in
Edit profile
Click on top : add a photo to profile
Select a jpg file
Upload
Receive error

Expected behavior

Show crop system