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):
31.0.9.1
- Operating system and version (e.g., Ubuntu 24.04):
Alpine Linux v3.22.1
- Web server and version (e.g, Apache 2.4.25):
nginx/1.28.0 (fpm-fcgi)
- Reverse proxy and version _(e.g. nginx 1.27.2)
traefik 2.9.6
- PHP version (e.g, 8.3):
8.4.11
- Is this the first time you’ve seen this error? (Yes / No):
Yes
- When did this problem seem to first start?
just noticed
- Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
container
- Are you using CloudfIare, mod_security, or similar? (Yes / No)
No
Summary of the issue you are facing:
Inspecting Contacts and found that the only user’s Federated Cloud ID was incorrect. Researched and found good advice about setting it, but it wasn’t changing anything.
Created new user to test with, the advice had resolved the issue at some point and the new user has the correct ID.
Original user has the original private IP as the domain.
Steps to replicate it (hint: details matter!):
-
Create Nextcloud installation, logging in behind via private IP
-
Setup reverse proxy and expose to internet, configure reverse proxy settings appropriately
-
new users get new domain, but original user still has provisioning IP as federated cloud id in contacts
Log entries
n/a
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.
N/A
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.
N/A
Web server / Reverse Proxy
The output of your Apache/nginx/system log in /var/log/____:
N/A
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!):
N/A
Apps
Enabled:
- activity: 4.0.0
- app_api: 5.0.2
- bookmarks: 15.2.0
- bruteforcesettings: 4.0.0
- calendar: 5.5.3
- carnet: 0.25.6
- circles: 31.0.0
- cloud_federation_api: 1.14.0
- comments: 1.21.0
- contacts: 7.3.1
- contactsinteraction: 1.12.0
- dashboard: 7.11.0
- dav: 1.33.0
- drawio: 3.1.0
- event_update_notification: 2.6.1
- federatedfilesharing: 1.21.0
- federation: 1.21.0
- files: 2.3.1
- files_downloadlimit: 4.0.0
- files_pdfviewer: 4.0.0
- files_reminders: 1.4.0
- files_sharing: 1.23.1
- files_trashbin: 1.21.0
- files_versions: 1.24.0
- firstrunwizard: 4.0.0
- integration_giphy: 2.1.0
- logreader: 4.0.0
- lookup_server_connector: 1.19.0
- mail: 5.4.0
- nextcloud_announcements: 3.0.0
- notes: 4.12.3
- notifications: 4.0.0
- oauth2: 1.19.1
- password_policy: 3.0.0
- passwords: 2025.9.20
- photos: 4.0.0
- previewgenerator: 5.10.0
- privacy: 3.0.0
- profile: 1.0.0
- provisioning_api: 1.21.0
- recognize: 9.0.7
- recommendations: 4.0.0
- related_resources: 2.0.0
- richdocuments: 8.7.4
- serverinfo: 3.0.0
- settings: 1.14.0
- sharebymail: 1.21.0
- spreed: 21.1.4
- support: 3.0.0
- survey_client: 3.0.0
- systemtags: 1.21.1
- tasks: 0.16.1
- text: 5.0.0
- theming: 2.6.1
- twofactor_backupcodes: 1.20.0
- updatenotification: 1.21.0
- user_status: 1.11.0
- viewer: 4.0.0
- weather_status: 1.11.0
- webhook_listeners: 1.2.0
- workflowengine: 2.13.0
Disabled:
- admin_audit: 1.21.0
- appointments: 2.4.6 (installed 2.4.6)
- encryption: 2.19.0
- files_external: 1.23.0
- inventory: 0.1.3 (installed 0.1.3)
- money: 0.30.0 (installed 0.30.0)
- suspicious_login: 9.0.1
- twofactor_nextcloud_notification: 5.0.0
- twofactor_totp: 13.0.0-dev.0
- user_ldap: 1.22.0
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.