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.12
- Operating system and version (e.g., Ubuntu 24.04):
Ubuntu 24
- Web server and version (e.g, Apache 2.4.25):
Apache 2
- Reverse proxy and version _(e.g. nginx 1.27.2)
No
- PHP version (e.g, 8.3):
8.3
- Is this the first time you’ve seen this error? (Yes / No)
- Yes
- When did this problem seem to first start?
During live deployment
- Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
VM
- Are you using CloudfIare, mod_security, or similar? (Yes / No)
No
Summary of the issue you are facing:
Full text search working nicely in a sandpit with a disposable Nextcloud and ElasticSearch 8 server. Built real ElasticSearch 8 server and deployed full text search on a dedicated test Nextcloud and also worked fine.
Started deployment of full text search on my live Nextcloud and after debugging typos the occ:fulltextsearch:test kept failing. Error in the nextcloud log:
[fulltextsearch_elasticsearch] Warning: 400 Bad Request: {“error”:{“root_cause”:[{“type”:“media_type_header_exception”,“reason”:“Invalid media-type value on headers [Content-Type, Accept]”}],“type”:“media_type_header_exception”,“reason”:“Invalid media-type value on headers [Content-Type, Accept]”,“caused_by”:{“type”:“status_exception”,“reason”:“Accept version must be either version 8 or 7, but found 9. Accept=application/vnd.elasticsearch+json; compatible-with=9”}},“status”:400}
Fulltext search had updated in the app store from 31.0.0 to 31.0.1 an hour before I did the live deployment. Test and Live share the same Elasticsearch so that’s common to both.
According to the doco on https://github.com/nextcloud/fulltextsearch_elasticsearch “As of version 26.0.0 this app is only compatible with Elasticsearch 8“
I presume this is an oops and not a design decision. Mandating a reinstall of ElasticSearch is not something I would expect as an undocumented feature of a point release.
At the very least this should be a config option if it’s not possible to look up the version of the elastic search server.
Downgrading the app to 31.0.0 (not Nextcloud!) gets me out of this hole for now, but of course has implications for future Nextcloud patches. And I was starting to consider NC32 over the Christmas break too…
Steps to replicate it (hint: details matter!):
-
Install fulltextsearch_elastic 30.0.1 search from app store
-
Configure against ElasticSearch 8.19.8 that’s only week old
-
occ fulltextsearch:test will fail
-
Manually downgrade fulltextsearch_elasticsearch to 30.0.0 to match test system
-
occ fulltextsearch:test now works
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.
[fulltextsearch_elasticsearch] Warning: 400 Bad Request: {“error”:{“root_cause”:[{“type”:“media_type_header_exception”,“reason”:“Invalid media-type value on headers [Content-Type, Accept]”}],“type”:“media_type_header_exception”,“reason”:“Invalid media-type value on headers [Content-Type, Accept]”,“caused_by”:{“type”:“status_exception”,“reason”:“Accept version must be either version 8 or 7, but found 9. Accept=application/vnd.elasticsearch+json; compatible-with=9”}},“status”:400}
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.
NA
Web server / Reverse Proxy
The output of your Apache/nginx/system log in /var/log/____:
NA
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!):
NA
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.
