Tweaking Apache configuration to allow overrides so dynamic pages can built correctly:

This step comes after "Activating" .htaccess in the tutorial.

This step didn't work out as described as the let's encrypt certbot step wasn't completed fully as it should.

Editing 000-default-le-ssl.conf:
sudo nano /etc/apache2/sites-available/000-default-le-ssl.conf

The file 000-default-le-ssl.conf didn't exist so nano created it as a blank file.
I copy/pasted the text from the tutorial as it should be displayed "at the time of it's writing".

<IfModule mod_ssl.c>
<VirtualHost *:443>
	# The ServerName directive sets the request scheme, hostname and port that
	# the server uses to identify itself. This is used when creating
	# redirection URLs. In the context of virtual hosts, the ServerName
	# specifies what hostname must appear in the request's Host: header to
	# match this virtual host. For the default virtual host (this file) this
	# value is not decisive as it is used as a last resort host regardless.
	# However, you must set it for any further virtual host explicitly.
	#ServerName www.example.com
## I wonder if the following line is correct ##
	[b]ServerAdmin webmaster@localhost[/b]
##??##
	DocumentRoot /var/www/html
    <Directory /var/www/html>
        AllowOverride All
    </Directory>
	# Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
	# error, crit, alert, emerg.
	# It is also possible to configure the loglevel for particular
	# modules, e.g.
	#LogLevel info ssl:warn

	ErrorLog ${APACHE_LOG_DIR}/error.log
	CustomLog ${APACHE_LOG_DIR}/access.log combined

	# For most configuration files from conf-available/, which are
	# enabled or disabled at a global level, it is possible to
	# include a line for only one particular virtual host. For example the
	# following line enables the CGI configuration for this host only
	# after it has been globally disabled with "a2disconf".
	#Include conf-available/serve-cgi-bin.conf


ServerName mydoman.com
SSLCertificateFile /etc/letsencrypt/live/mydoman.com/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/mydoman.com/privkey.pem
Include /etc/letsencrypt/options-ssl-apache.conf
</VirtualHost>
</IfModule>

As the certbot step will have to be executed later on again, we'll have to see if the fact that this file will exist creates some "trouble" in the installation process.

A recheck of this file after executing the certbot again will be necessary.

@Hank G ☑️
When the idea is to prepare a VPS-migration of an existing friendica node, should the certbot step and the edit of this file be executed in a different moment (later on) in the installation process?

This part of the installation process took me like another hour.

…ᘛ⁐̤ᕐᐷ jesuisatire bitPickup

2023-10-17 15:46:49

"Activating" .htaccess:
cp .htaccess-dist .htaccess

The creation of th DB apparently worked as expected.

The problem I now ran into is that I can't upload the backup sql DB I donwloaded from the old hosting.

I did this using the hints of the following stackoverflow description: importing-a-database-using-ssh but somehow this doesn't work.

I created a folder in my home directory for to log into the VPS via ssh where I placed the privkey.pem and the backupname.sql

This is the command sequence I execute:
cd hostingfolder
/hostingfolder ssh -i privkey.pem root@00.000.00.000
Enter passphrase for key 'privkey.pem':
Welcome to Ubuntu ..
..
rootname@ubuntu:~# mysql -u friendica@localhost -ppassword friendicadb < backupname.sql

The response by the server is:
-bash: backupname.sql: No such file or directory

I also tried:
rootname@ubuntu:~# mysql -u friendica -ppassword friendicadb < backupname.sql
with the same result

Of course the file backupname.sql does exist and is located in /hostingfolder
I also copied it to the folder /home/username/ just to make sure.

I searched the error message to and found:
stackoverflow.com/questions/42…

so I tried:
mysql -u 'friendica'@'localhost' -ppassword friendicadb < '/home/username/hostingfolder/backupname.sql'
and
mysql -u tupambaeorg'@'localhost -pSnMAVMY4McXAKq tupambaeorgdb < "/home/bitpickup/hosting172_16_9_5.sql"
but that didn't do the trick either.

Any ideas?