[Forum] update changelogs

kralizec/forum11/README.md

@@ -18,29 +18,13 @@ VMID: 119
 `/var/discourse_docker/discourse_doctor`
 
 
-## Docker rebuild errors
+Latest update:
-
-`/var/discourse_docker/launcher rebuild web_only`
-
-
-```
-Plugin name is 'ldap', but plugin directory is named 'discourse-ldap-auth'
-rake aborted!
-ActiveRecord::NoDatabaseError: We could not find your database: discoursedb. Available database configurations can be found in config/database.yml. (ActiveRecord::NoDatabaseError)
-
-```
-
-
-```
-FAILED
---------------------
-Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #<Process::Status: pid 593 exit 1>
-Location of failure: /usr/local/lib/ruby/gems/3.3.0/gems/pups-1.3.0/lib/pups/exec_command.rb:131:in `spawn'
-exec failed with the params {"cd"=>"$home", "tag"=>"migrate", "hook"=>"db_migrate", "cmd"=>["su discourse -c 'bundle exec rake db:migrate'"]}
-bootstrap failed with exit code 1
-** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one.
-./discourse-doctor may help diagnose the problem.
-a9a704b1ee166487d8cd2acd5bd9bcc050ed0ec93fc065f58440e4ae208e1937
-```
-
 
+- The forum has been restored; images should load when clicked but may not display immediately.
+- Resolved several problems sequentially: admin panel and updates were failing, Docker builds failed due to PostgreSQL 13, upgraded to 15.
+- Restored from backup and created a new backup from the old SQL server, transferring data via PostgreSQL 15.
+- Manually enabled the required vector extension on the new database because Discourse could not do it automatically.
+- Docker container rebuild succeeded only after disabling the SSL template in the Docker configuration.
+- After rebuild, the forum returned with new posts but login failed and media/files were missing.
+- Uploaded files after May 1 were lost; database and uploads backups were found in the shared folder.
+- Login issue was caused by a missing SSL template; resolved by setting up an Nginx reverse‑proxy with a self‑signed certificate on the forum VM, allowing SSL access through the main HTTP VM.