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:
(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):
34.0.3snap1
Operating system and version (e.g., Ubuntu 24.04):
Debian GNU/Linux 13 (trixie) 13.5
Web server and version (e.g, Apache 2.4.25):
replace me
Reverse proxy and version _(e.g. nginx 1.27.2)
Apache (dont know the version)
PHP version (e.g, 8.3):
dont know
Is this the first time you’ve seen this error? (Yes / No):
yes
When did this problem seem to first start?
after install
Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
snap on raspberry pi
Are you using CloudfIare, mod_security, or similar? (Yes / No)
tailscale
Summary of the issue you are facing:
local computers get a ‘This site can’t be reached’
internet connected (Phone on cell network with wifi turned off) get an untusted Domain message
Hey @PaulBoudreau, welcome to the Nextcloud community and thanks for supporting Nextcloud snap
Sorry to hear you are having issues with your Nextcloud snap installation. If you’ve come this far, you’re on the right track! There is a good chance someone in the community has had a similar issue and knows how to resolve it.
Below are some links to how-to’s answering frequently asked questions and may help you help yourself;
Please note that the “domain” part of this: boudreaucloud.tail348316.ts.net is actually ts.net - boudreaucloud is a sub-sub domain
Try to add ts.net to your trusted domains list and see if that helps. The trusted domains list needs to be what is presented in the “host” header for the request, so I am not sure IPs will work
Turns out replacing the IP address’ with domain names works for getting to the server over the internet.
Locally accessing the server doesn’t seem to work though. My desktop, which is on the same local area network as the nextcloud server can’t access the server via boudreaucloud.tail348316.ts.net in a browser. It can ping the hostname. The results are still 'This site can’t be reached’ in the chrome browser. if i try to reach it via http://boudreaucloud/ on the local network it works.
@PaulBoudreau try and see what happens if you enter ``nextcloud.local`:
After installation, Nextcloud will start automatically. Assuming you and the device on which it was installed are on the same network, you will reach the Nextcloud installation by visiting <hostname>.local or the IP address of the instance in your browser. If your hostname is localhost or localhost.localdomain, like on an Ubuntu Core device, nextcloud.local will be used instead.
alternatively see:
and check your servers FQDN configuration then try adding nextcloud.local in your config.php:
PS. My cell phone can reach the Nextcloud server via ‘boudreaucloud. tail348316.ts.net’ while it is on the local wifi network with the nextcloud server or when it is off the wifi and using only the cell network.
If you add boudreaucloud.local to your trusted domains, that error will go away, hence why I suggested that as a workaround for you.
the “trusted_domains” array in your config essentially says to nextcloud:
If someone tries to access me using any of these domains in the host header, I can trust them
Since boudreaucloud.local is not in the list, nextcloud does its job, and blocks the access.
You do not need to add your other tailscale device DNS’s in that list, as you will not use those “domains” to access nextcloud.
aha, to figure out what that is due to, you will need to share some logs from your nextcloud instance. Internal server errors are usually logged there. Could you take a look?
i must have typed something wrong in the config.php the first time because i re added boudreaupaul.local and now that is working.
The only issue now is that browsing to ‘boudreaucloud. tail348316. ts. net’ gives a ‘This site cant be reached’
I tested this on my laptop also and it works with all 3 methods.
boudreaucloud
boudreaucloud.local
‘boudreaucloud. tail348316. ts. net’
At this point I’m thinking its a windows setting i probably changed on my desktop. The desktop is never going to be outside the local wifi network and it can access the files via samba anyway. So i’m willing to forget about the Desktop issue.
The only missing test is to try my laptop when its not on the local network. But my phone is working off the local network, so my laptop should also. I will post here or open a new help topic if i have an issue with the laptop
