Nextcloud Trusted domain error. tried to access using as host

ℹ️ Support
1

I am receiving "nextcloud Trusted domain error. “external_ip” tried to access using as host.

I have hundreds of iOS devices out in the field that will be accessing the server for Contacts and each one will produce this error. It is not feasible to whitelist every external ip addy from mobile devices. I’m looking for advice on how to proceed.

Thanks

2

The trusted domain is simply the hostname in the URL you’ll be using to access your instance. You’ll likely only have one (maybe two, if you include localhost).

Please check the Admin Manual for details: https://docs.nextcloud.com

https://docs.nextcloud.com/server/latest/admin_manual/installation/installation_wizard.html#trusted-domains

3

Thanks. I do have my trusted domains already established.

Maybe I’m not asking the right question. Ex: I push out a contact list to iOS devices through an MDM, but if any iOS device connects to another router, the routers ip addy is seen as trying to access the server and a log is written. I can probably limit the number of logs by setting hours on the server.

4

That is a strange behavior, because routers are ususally not listed as communication source, except they are doing a kind of natting or are working as a proxy. You need to provide more detailed information about your network to be able to understand what is going on in detail.

5

I’m still not following what you’re saying. Can you post the actual log entry you’re concerned about?

6

My log has quite a few errors such as: Trusted domain error. “185.242.226.109” tried to access using “68...**” as host.

I am new to Nextcloud and erroneously assumed this was one of my phones trying to log into the carddav server. I now believe these are just people/bots trying to access the server and are being blocked. I hope they are being blocked.

I only have two trusted domains and I can log in from either just fine.

7

Sounds like you’ve changed your loglevel from the default of 2 to 1 which means you’ll get a lot more noise in your logs like that: Logging — Nextcloud latest Administration Manual latest documentation

Every bot/etc connection attempt isn’t normally logged in the main log.

It’s also possible to adjust your web server configuration (note: this isn’t a Nextcloud matter but just a general virtual host configuration matter with web servers) to have a default handler for connections that lack the correct hostname in the Host: header. This prevents those connections from even getting as far as Nextcloud.