Support intro
Sorry to hear you’re facing problems. 
The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.
If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.
Getting help
In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.
Before clicking submit: Please check if your query is already addressed via the following resources:
- Official documentation (searchable and regularly updated)
- How to topics and FAQs
- Forum search
(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).
Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. ![]()
The Basics
- Nextcloud Server version (e.g., 29.x.x):
11.9.0
- Operating system and version (e.g., Ubuntu 24.04):
TrueNAS 25.04
- Web server and version (e.g, Apache 2.4.25):
no idea
- Reverse proxy and version _(e.g. nginx 1.27.2)
Zoraxy 3.2.5
- PHP version (e.g, 8.3):
no idea
- Is this the first time you’ve seen this error? (Yes / No):
replace me
- When did this problem seem to first start?
Since beginning
- Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
AIO
- Are you using CloudfIare, mod_security, or similar? (Yes / No)
Cloudflare X CrowdSec
Summary of the issue you are facing:
I have backed up PostgreSQL of TrueNAS’s official app with the help of pgAdmin. Now I wish to migrate to AIO. I’m just stuck at the final part is to recover the database to fresh deployed AIO.
If I restore without cleaning is ok-ish. Meaning that all users can log-in, but loosing a lot of content such as theming, branding, contacts, conversations,… those are missing. Activities list is also good. I feel that I’m so close to the final goal.
Steps to replicate it (hint: details matter!):
-
Deploy custom yaml for pgAdmin by putting into 2 docker network of the 2 Nextcloud instances.
ix-dextcloud_defaultandnextcloud-aio -
Get the password of the 2 databases by going into their configuration file
-
Configure pgAdmin to connect to those database containers.
Names/hostnames of the containers are- ix-nextcloud-postgres-1
- nextcloud-aio-database
-
Back up the database of the actual Nextcloud instance to a .sql file
-
Restore the database to AIO by checking Pre-data, Data, Post-data, Clean before messes up and got error 500, so If it’s not checked, that’s ok
Log entries
Nextcloud
Please provide the log entries from your Nextcloud log that are generated during the time of problem (via the Copy raw option from Administration settings->Logging screen or from your nextcloud.log located in your data directory). Feel free to use a pastebin/gist service if necessary.
The logs shows after the fresh install. Haven’t started the restoration of the database yet
Not posting it. Due to tons of sensitive data such as IP and FQDN
Web Browser
If the problem is related to the Web interface, open your browser inspector Console and Network tabs while refreshing (reloading) and reproducing the problem. Provide any relevant output/errors here that appear.
PASTE
Web server / Reverse Proxy
The output of your Apache/nginx/system log in /var/log/____:
PASTE HERE
Configuration
Nextcloud
The output of occ config:list system or similar is best, but, if not possible, the contents of your config.php file from /path/to/nextcloud is fine (make sure to remove any identifiable information!):
PASTE HERE
Apps
The output of occ app:list (if possible).
Tips for increasing the likelihood of a response
- Use the
preformatted textformatting option in the editor for all log entries and configuration output. - If screenshots are useful, feel free to include them.
- If possible, also include key error output in text form so it can be searched for.
- Try to edit log output only minimally (if at all) so that it can be ran through analyzers / formatters by those trying to help you.
Personal notes
Sorry If I have missed out to post something might be important.

