Categories:LAMP, Linux, VPS

rootname@VPShosting:~$ sudo apt update
rootname@VPShosting:~$ sudo apt install apache2 -y

rootname@VPShosting:~$

sudo snap install core; sudo snap refresh core
sudo snap install --classic certbot

rootname@VPShosting:~$ sudo ln -s /snap/bin/certbot /usr/bin/certbot

rootname@VPShosting:~$ sudo certbot --apache

Configure PHP dependencies:
www-data@VPShosting:~$ cd html
www-data@VPShosting:~/html$ bin/composer.phar install --no-dev

rootname@VPShosting:~$ sudo ufw allow ssh
rootname@VPShosting:~$ sudo ufw allow http
rootname@VPShosting:~$ sudo ufw allow https
rootname@VPShosting:~$ sudo ufw enable
rootname@VPShosting:~$ sudo ufw status

rootname@VPShosting:~$

sudo apt install fail2ban -y 
rootname@VPShosting:~$ [code]sudo systemctl enable fail2ban

rootname@VPShosting:~$ systemctl status fail2ban

rootname@VPShosting:~$ sudo reboot

Because of the reboot you will be logged out of your VPS server and will have to log on again to proceed with the installation.

"M" like MySQL/mariaDB and "P" like PHP of "LAMP" installation

rootname@VPShosting:~$ sudo apt update

rootname@VPShosting:~$

sudo apt install mariadb-server php libapache2-mod-php \
     php-common php-gmp php-curl php-intl php-mbstring \
	 php-xmlrpc php-mysql php-gd php-imagick php-xml \
	 php-cli php-zip php-sqlite3 curl git -y

rootname@VPShosting:~$ sudo mysql_secure_installation

MariaDB [(none)]> CREATE DATABASE friendicadb;
Query OK, 1 row affected (0.000 sec)
MariaDB [(none)]> CREATE USER 'friendica'@'localhost' IDENTIFIED BY '<password>';
Query OK, 0 rows affected (0.002 sec)
MariaDB [(none)]> GRANT ALL ON friendicadb.* TO 'friendica'@'localhost';
MariaDB [(none)]> FLUSH PRIVILEGES;
Query OK, 0 rows affected (0.000 sec)
MariaDB [(none)]> EXIT;
Bye

rootname@VPShosting:~#

To log from the console into your DB use the following command:
rootname@VPShosting:~# mysql friendicadb

To exit mariaDB:
MariaDB [friendicadb]> Ctrl-C -- exit!
Aborted
rootname@VPShosting:~#

install automysqlbackup
rootname@VPShosting:~# sudo apt-get install automysqlbackup
rootname@VPShosting:~# sudo automysqlbackup

#debian #linux #friendica #fediVerse #fediTutorial

#bugResearch

Dear Tupambae.org profiles, please add as answers to this post any kind of strange behaviour you might stumble over as inicial notes.

To prevent SPAMing this post please have a look first at the entire post.
Don't create new answers for the same issue, just edit your comment.
thx👍

If possible have a look at the open gitHub issues for #friendica in this link.

#bugResearch
[spoiler=Platform Info: 2023.05 - stable]Friendica Version: 2023.05 - stable
Friendica Source: gitHub 
PHP version: 8.1.2-1ubuntu2.14
SQL version: MySQL / MariaDB
memory_limit	256M
4 Core CPU, 8 GB Ram with 300GB NVME Disk
[/spoiler][hr]I [b]did/n't[/b] have a look at gitHub
[spoiler=Short bug description:]Overall summary of the issue.
Replace the texts inside this and the following spoilers with your description.[/spoiler][spoiler=Details of the buggy behavior:]Try to explain in short sentences and with precise wording what happens.[/spoiler][spoiler=¿Possible to reproduce, if so how:]step one to reproduce the problem
step two
step three[/spoiler][spoiler=Expected result:]¿what should be the correct behavior?
¿what did you expect?[/spoiler][spoiler=Screenshots:][img=]the better and dedicated the screenshot and the info involved the better[/img]
[img=]don't include unnecessary or compromising details in the screenshot[/img][/spoiler][hr]information for dev and server team:[spoiler=php.error.log]LEAVE THIS AS IS, the server team will use this report if possible/necessary[/spoiler]

#friendicaBugReport

Clean bug report as seen when you use the code block above

#bugResearch

Platform Info: 2023.05 - stable

Friendica Version: 2023.05 - stable
Friendica Source: gitHub
PHP version: 8.1.2-1ubuntu2.14
SQL version: MySQL / MariaDB
memory_limit 256M
4 Core CPU, 8 GB Ram with 300GB NVME Disk

I did/n't have a look at gitHub

Short bug description:

Overall summary of the issue.
Replace the texts inside this and the following spoilers with your description.

Details of the buggy behavior:

Try to explain in short sentences and with precise wording what happens.

¿Possible to reproduce, if so how:

step one to reproduce the problem
step two
step three

Expected result:

¿what should be the correct behavior?
¿what did you expect?

Screenshots:

information for dev and server team:

php.error.log

LEAVE THIS AS IS, the server team will use this report if possible/necessary

Categories: friendica,VPS,github

friendica installation on the VPS hosting
--
Up to this point we basically performed a standard LAMP installation on a ubuntu 22.04 LTS VPS hosting.

The following steps concern the actual friendica server installation.

creating the directory for friendica and the user www-data

rootname@VPShosting:~# sudo chown -R www-data:www-data /var/www
rootname@VPShosting:~# cd /var/www

rootname@VPShosting:~/var/www# sudo -u www-data bash
www-data@VPShosting:~$
(confirmation check if this is where console changes to www-data@VPShosting:~#)

www-data@VPShosting:~$ mv html html.bak
The new /html folder will be created when we clone the gitHub stable branch of friendica in the next step.

www-data@VPShosting:~$ git clone https://github.com/friendica/friendica.git -b stable html

www-data@VPShosting:~$ cd html
www-data@VPShosting:~/html$ bin/composer.phar install --no-dev
(is this the point the SSL install went wrong?)
https://squeet.me/display/962c3e10-1265-2ea9-912d-3cc762780991

www-data@VPShosting:~/html$ mkdir -p view/smarty3
www-data@VPShosting:~/html$ chmod 775 view/smarty3

www-data@VPShosting:~/html$ git clone https://github.com/friendica/friendica-addons.git -b stable addon

www-data@VPShosting:~/html$ cp .htaccess-dist .htaccess

www-data@VPShosting:~/html$ exit
rootname@VPShosting:~/var/www/html#

#debian #linux #friendica #fediVerse #fediTutorial

…ᘛ⁐̤ᕐᐷ jesuisatire bitPickup

2023-10-17 15:34:41

As of now I skipped this step as I do have already a DB with password and name on the original installation I will have to migrate to this new VPS.

@helpers@forum.friendi.ca

Server specs and friendica version used:
VPS server | Ubuntu 22.04 LTS
PHP Version 8.1.2-1ubuntu2.14
4 Core CPU, 8 GB Ram with 300GB NVME Disk
Friendica [STABLE] | 'Giant Rhubarb' 2023.05 - 1518

…ᘛ⁐̤ᕐᐷ jesuisatire bitPickup

2023-10-17 13:04:10

friendica VPS setup on ubuntu 22.04 LTS

@Friendica Support

Hi,
I'm working on my first #friendica #VPS installation, here you'll find my initial post about general thoughts like what distro to use, size and costs.
I'm using the tutorial "creating a friendica server - ubuntu" by @Hank G ☑️.

As of now I'm doing well in the process and want to start this post to document differences and questions while installing the server.

This server is going to host an already existing friendica node I have to move from another hosting provider. That means that for example the DB doesn't have to be created from scratch but moved and other smaller details.

I will try to address the different steps of installation in answers to this post and appreciate help, ideas and observations.

I'm doing this from a #linux desktop environment from the console but there shouldn't be differences if you want to do this from a #windows machine.

#fediVerse #tutorial #fediHelp #activityPub

Ihr habt vielleicht gemerkt, dass ich seit gestern um die Mittagszeit nicht aktiv war.

Grund ist, dass ich mir einen neuen #vServer #VPS hochgezogen und meine #Friendica #Instanz dorthin migriert habe.

Neben dem Aufwand, den man mit der kompletten #Neuinstallation und #Einrichtung eines Servers from Scratch hat (#SSH mit #Zertifikat, #PHP, #MySQL, #Apache, #LetsEncrypt / #Certbot, #Fail2Ban, #Firewall / #UFW, ...) , kam dann das Backupen von Friendica samt #Datenbank und das Neueinrichten auf dem neuen Server hinzu.

Dabei diverse kleinere Unwegsamkeiten wie dass sich das Datenverzeichnis geändert hat (anderer Apache-Hauptordner) und damit eine weiße Seite beim Aufrufen der Administration --> Speicher kam.
(BTW: Das habe ich durch einen temporären symbolischen Link gelöst).

Und schwups, ist ein guter halber Tag weg 🙈

Übrigens waren nach dem Umzug auf den neuen Server wieder diverse Emoticons aus Profilnamen weg (also lauter ?????).
Durch "Kontaktdaten neu laden" wurden und werden sie wieder korrekt dargestellt.
Dieses Problem verstehe ich noch immer nicht 🤔🤷‍♂️

Was bei den nun ersten Nutzungstests deutlicih besser respektive bislang verschwunden ist, ist das Problem fehlender Profilbilder oder ganzer Fehldarstellung der Seite beim Laden.

Hier war wahrscheinlich mein Webspace, auf dem Friendica bis gestern lief, doch einfach nicht leistungsfähig genug: 1024 MB RAM und 16 Kunden pro CPU-Kern für Mail, 2x #Joomla,1x große #Nextcloud und dann noch Friendica.

Der vServer hat nun 8 Kerne und 12 GB RAM und dümpelt (mit bislang nur Friendica darauf installiert) bei einer Load von < 1.

@Friendica Support

Preparing to move the DB

Changing the #storage backend to reduce DB size.

Admin panel:

Helpers-page information

Moving storage via SSH

¿correct?:

mkdir /var/www/html/storage
./bin/console config storage.name = Filesystem
./bin/console config storage.filesystem_path = storage
./bin/console storage move

Ich teste immer ganz gerne zeitnah, nachdem ich einen neuen Dienst installiert habe, den #Restore. So gerade auch bei meiner frisch aufgesetzen #Friendica #Instanz

Der #Dump der Friendica #Datenbank läuft ohne #Fehlermeldung durch.

Beim Restore in eine neue, leere Datenbank, kommt sehr schnell eine lange Fehlermeldung und der Restore bricht ab. 😞

Hat jemand eine Idee?

Gerne teilen für mehr Reichtweite.

Table 'friendica.contact' doesn't exist

Fehler bei der Anfrage:
CREATE ALGORITHM=UNDEFINED DEFINER=`user`@`localhost:3306` SQL SECURITY DEFINER VIEW `account-user-view` AS select `ucontact`.`id` AS `id`,`contact`.`id` AS `pid`,`ucontact`.`uid` AS `uid`,`contact`.`url` AS `url`,`contact`.`nurl` AS `nurl`,`contact`.`uri-id` AS `uri-id`,`item-uri`.`guid` AS `guid`,`contact`.`addr` AS `addr`,`contact`.`alias` AS `alias`,`contact`.`name` AS `name`,`contact`.`nick` AS `nick`,`contact`.`about` AS `about`,`contact`.`keywords` AS `keywords`,`contact`.`xmpp` AS `xmpp`,`contact`.`matrix` AS `matrix`,`contact`.`avatar` AS `avatar`,`contact`.`photo` AS `photo`,`contact`.`thumb` AS `thumb`,`contact`.`micro` AS `micro`,`contact`.`header` AS `header`,`contact`.`created` AS `created`,`contact`.`updated` AS `updated`,`ucontact`.`self` AS `self`,`ucontact`.`remote_self` AS `remote_self`,`ucontact`.`rel` AS `rel`,`contact`.`network` AS `network`,`ucontact`.`protocol` AS `protocol`,`contact`.`location` AS `location`,`ucontact`.`attag` AS `attag`,`contact`.`pubkey` AS `pubkey`,`contact`.`prvkey` AS `prvkey`,`contact`.`subscribe` AS `subscribe`,`contact`.`last-update` AS `last-update`,`contact`.`success_update` AS `success_update`,`contact`.`failure_update` AS `failure_update`,`contact`.`failed` AS `failed`,`contact`.`last-item` AS `last-item`,`contact`.`last-discovery` AS `last-discovery`,`contact`.`contact-type` AS `contact-type`,`contact`.`manually-approve` AS `manually-approve`,`contact`.`unsearchable` AS `unsearchable`,`contact`.`sensitive` AS `sensitive`,`contact`.`baseurl` AS `baseurl`,`contact`.`gsid` AS `gsid`,`ucontact`.`info` AS `info`,`contact`.`bdyear` AS `bdyear`,`contact`.`bd` AS `bd`,`contact`.`poco` AS `poco`,`contact`.`name-date` AS `name-date`,`contact`.`uri-date` AS `uri-date`,`contact`.`avatar-date` AS `avatar-date`,`contact`.`term-date` AS `term-date`,`contact`.`hidden` AS `global-ignored`,`contact`.`blocked` AS `global-blocked`,`ucontact`.`hidden` AS `hidden`,`ucontact`.`archive` AS `archive`,`ucontact`.`pending` AS `pending`,`ucontact`.`deleted` AS `deleted`,`ucontact`.`notify_new_posts` AS `notify_new_posts`,`ucontact`.`fetch_further_information` AS `fetch_further_information`,`ucontact`.`ffi_keyword_denylist` AS `ffi_keyword_denylist`,`ucontact`.`rating` AS `rating`,`ucontact`.`readonly` AS `readonly`,`ucontact`.`blocked` AS `blocked`,`ucontact`.`block_reason` AS `block_reason`,`ucontact`.`subhub` AS `subhub`,`ucontact`.`hub-verify` AS `hub-verify`,`ucontact`.`reason` AS `reason`,`contact`.`notify` AS `dfrn-notify`,`contact`.`poll` AS `dfrn-poll`,`item-uri`.`guid` AS `diaspora-guid`,`diaspora-contact`.`batch` AS `diaspora-batch`,`diaspora-contact`.`notify` AS `diaspora-notify`,`diaspora-contact`.`poll` AS `diaspora-poll`,`diaspora-contact`.`alias` AS `diaspora-alias`,`diaspora-contact`.`interacting_count` AS `diaspora-interacting_count`,`diaspora-contact`.`interacted_count` AS `diaspora-interacted_count`,`diaspora-contact`.`post_count` AS `diaspora-post_count`,`apcontact`.`uuid` AS `ap-uuid`,`apcontact`.`type` AS `ap-type`,`apcontact`.`following` AS `ap-following`,`apcontact`.`followers` AS `ap-followers`,`apcontact`.`inbox` AS `ap-inbox`,`apcontact`.`outbox` AS `ap-outbox`,`apcontact`.`sharedinbox` AS `ap-sharedinbox`,`apcontact`.`generator` AS `ap-generator`,`apcontact`.`following_count` AS `ap-following_count`,`apcontact`.`followers_count` AS `ap-followers_count`,`apcontact`.`statuses_count` AS `ap-statuses_count`,`gserver`.`site_name` AS `site_name`,`gserver`.`platform` AS `platform`,`gserver`.`version` AS `version`,`gserver`.`blocked` AS `server-blocked`,`gserver`.`failed` AS `server-failed` from (((((`contact` `ucontact` join `contact` on(`contact`.`uri-id` = `ucontact`.`uri-id` and `contact`.`uid` = 0)) left join `item-uri` on(`item-uri`.`id` = `ucontact`.`uri-id`)) left join `apcontact` on(`apcontact`.`uri-id` = `ucontact`.`uri-id`)) left join `diaspora-contact` on(`diaspora-contact`.`uri-id` = `ucontact`.`uri-id`)) left join `gserver` on(`gserver`.`id` = `contact`.`gsid`));

Fatal error: Couldn't create table or view `DEFINER´

@Friendica Support

So sieht es bei mir aus:
Momentan kennt dieser Knoten 4.273 Knoten mit insgesamt 2.120.886 registrierten Nutzern, die die folgenden Plattformen verwenden:

• #Friendica (379/4.024) - 10 Nutzer pro Instanz
• #diaspora (304/628.472) - 2.067 Nutzer pro Instanz
• #red (7/64) - 9 Nutzer pro Instanz
• #hubzilla (264/7.687) - 3 Nutzer pro Instanz
• #GNU Social (136/6.425) - 47 Nutzer pro Instanz
• #StatusNet (9/174) - 19 Nutzer pro Instanz
• #Mastodon (2.722/1.451.747) - 901 Nutzer pro Instanz
• #pleroma (446/21.092) - 47 Nutzer pro Instanz
• #socialhome (4/973) - 243 Nutzer pro Instanz
• #ganggo (2/228) - 114 Nutzer pro Instanz

Bei Diaspora scheint es also am kompliziertesten zu sein, eine eigene Instanz zu betreiben (oder die Nutzer vertrauen den Betreibern am meisten 😉 ) und bei Hubzilla ist es am einfachsten (oder die Nutzer sind am mistrauischsten 😉 ).

Da ich mal wissen wollte, wie sich das über die Zeit entwickelt, habe ich mir das von Zeit zu Zeit mal notiert und so sieht es dan aus:

• 8. Januar : 4.253 / 2.349.200 -> Maximale Anzahl an Nutzern
• 9. Januar : 4.241 / 2.345.669
• 10. Januar : 4.231 / 2.330.945
• 11. Januar : 4.226 / 2.334.113
• 13. Januar : 4.229 / 2.039.934
• 14. Januar : 4.259 / 2.054.374
• 15. Januar : 4.252 / 2.059.012
• 16. Januar : 4.246 / 2.007.713
• 27. Januar : 4.215 / 2.025.384
• 7. Februar: 4.208 / 2.124.247
• 10. Februar: 4.245 / 2.131.417
• 23. Februar: 4.267 / 1.769.948
• 27. Februar: 4.243 / 2.181.948
• 3. März: 4.273 / 2.120.880 -> Maximale Anzahl an Instanzen

Die Anzahl der Instanz korreliert also nicht unbedingt mit der Anzahl der Nutzer, auch interessant.

#föderation #Fediverse

@Friendica Support

Hi,
I'm working on my first #friendica #VPS installation, here you'll find my initial post about general thoughts like what distro to use, size and costs.
I'm using the tutorial "creating a friendica server - ubuntu" by @Hank G ☑️.

As of now I'm doing well in the process and want to start this post to document differences and questions while installing the server.

This server is going to host an already existing friendica node I have to move from another hosting provider. That means that for example the DB doesn't have to be created from scratch but moved and other smaller details.

I will try to address the different steps of installation in answers to this post and appreciate help, ideas and observations.

I'm doing this from a #linux desktop environment from the console but there shouldn't be differences if you want to do this from a #windows machine.

#fediVerse #tutorial #fediHelp #activityPub

…ᘛ⁐̤ᕐᐷ jesuisatire bitPickup

2023-10-12 18:28:38

what VPS offer fits best for a small friendica instance?

@Friendica Support
@Friendica Admins
@Friendica Developers

Hi there,
in the end I want to try to setup my first own hosted friendica VPS on a small setup:
1gig RAM/1 Core/25gig

The idea is kinda single user instance with a few forum pages.

The hosting provider has the following options:

• debian bullsey - vpn server
• debian bookworm - wireguard server
• debian bookworm - bookworm 2023-07-03
• debian bookworm - bookworm 2023-07-03 LEMP (nginx+php8.2+mariaDB10.5)
• debian bookworm - nextcloud
• ubuntu 22.04.01LTS
• CENTOS8.1 - 2020-05-03
• cleanVPS to upload own ISO

I'm used to debian/devuan on PC, so am obviously inclined to go for debian but have no idea what version would be the best choice.

In the first place the debian LEMP option looks like the way to go.
Latest experience with a new friendica installation seemed to be in need of PHP8.1 instead of PHP8.2.
Is it difficult to downgrade that?

Also, I'm kinda worried about security in general, even tho the data exposed will only be my own, so there is no responsibility with others.
Are there more security risks than on a shared hosting with let's say a standard phpBB forum page?

The idea would be to point the IP from my existing hosting provider to the VPS.

• Do we have some general "how to setup" for a VPS setting from scratch?
• Anyone interested in creating such a "how to" in a conversation with me here to have a refence or base to sum that up for the frindica wiki?
• Could it even be of interest to create a "friendica VPS-ISO installation" with the help of git.friendi.ca for example?

@TupambAdmin
@bitPickup mʕ•ﻌ•ʔm