hi @dosch, please don’t remove anything yet, your data is not lost but inside the postgresql database.
Did you do a backup before your first upgrade ?
Would you mind retrying the same command again ? I still didn’t understand your password authentication failed for user "outline" error while everything seems to be OK for the identification
Thanks and sorry for the late feedback, I’ll try to stay connected to the forum today
Using “outline” as server, “outline” as database, and “THISISTHEKEYTHATWASOUTPUT” as the password ?
You should be able to get in and access your outline database.
This is to check whether there is an issue with it or not.
OK, we are getting there. The “production” environment is now well triggered.
However, there is apparently an issue with your database.
I’ll check for you what should be the next step.
Shall I assume that you didn’t make any backup before starting the upgrade ?
Can you open the command line and type su postgres
then psql
then \l
then \du
And copy here the output of these last two commands please ?
Here are mine for reference
postgres-# \du
List of roles
Role name | Attributes | Member of
-----------+------------------------------------------------------------+-----------
nextcloud | | {}
outline | | {}
postgres | Superuser, Create role, Create DB, Replication, Bypass RLS | {}
I suspect that for some reason your “outline” role was deleted, which shouldn’t be a big deal. I just hope that the “outline” database by itself is still there…
postgres-# \du
List of roles
Role name | Attributes | Member of
-----------+------------------------------------------------------------+-----------
hedgedoc | | {}
odoo | Create DB | {}
postgres | Superuser, Create role, Create DB, Replication, Bypass RLS | {}
Outline seems totally absent indeed…
No, I did make a backup. Or, better said, YNH made the pre-upgrade backup.
Well, now I understand your problem that is rather simple, your outline database is gone indeed. It’s very probably a bad consequence of your instance running out of space while installing at that time.
If the pre-upgrade backup was when you upgraded here the I think the best is clearly to remove your outline app from the web admin and then restore Outline from that pre-upgrade backup. You’ll get all your previous data !
HOWEVER, before doing so, please copy-paste carefully somewhere the content of your /var/www/outline/.env file, as it contains important encryption keys. This is just in case as the pre-upgrade archive should have it too, but we can’t be too prudent !
Once restored if you aren’t fed-up, which I would fully understand… You can attempt another upgrade again !
Sorry again for the time lost and all hassle involved…
I’m not sure if you have the same issue I ran into but I started getting this auth failure message recently after an update, and it related to Outline not accepting the token from Dex when using self-signed cert (I’m not sure why this is, as I have a valid cert installed).
The solution was to add the following line in /var/www/outline/.env:
NODE_TLS_REJECT_UNAUTHORIZED=0
After restarting the Outline service I could then authenticate.
Me neither! For me I found the LE cert autorenew had failed for that subdomain (due to Cloudflare Proxy being on); I was able to get the cert renewed and remove that line in the env file, and auth continued to work fine. This was with Dex 2.39.1~ynh1 and Outline 0.76.1~ynh1 just for reference.