Cannot access Nextcloud AIO on iOS device

ℹ️ Support 📦 Appliances (Docker, Snappy, VM, NCP, AIO)
, , , ,
1

Hi everyone,

I’ve just installed NextCloud AIO for the first time, after using for 1 day, I cannot access it on iOS device. I have tested with two linux devices and it’s all good. I am running AIO behind the caddy reverse proxy as I’m hoping to put more services behind it later. The error I am getting on Firefox on iOS is “A server with the specified name could not be found. NSURLErrorDomain”.

I think it stopped working after I tried to install forgejo on the same machine. Forgejo was on port 3000 and I didn’t think that would have an impact but apparently I was wrong hahaha.

Does anyone know what could be the issue and what step I could do to solve it. I’m mainly trying to learn so I can fix it later and would rather not just nuke my server to reinstall it even though it is possible.

The Basics

  • Nextcloud Server version (e.g., 29.x.x):
    • 31.0.6
  • Operating system and version (e.g., Ubuntu 24.04):
    • Ubuntu 25.04
  • Web server and version (e.g, Apache 2.4.25):
    • I don’t know
  • Reverse proxy and version _(e.g. nginx 1.27.2)
    • Caddy
  • PHP version (e.g, 8.3):
    • I don’t know
  • Is this the first time you’ve seen this error? (Yes / No):
    • Yes
  • When did this problem seem to first start?
    • after one day of use, after I strated Forgejo
  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    • AIO
  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    • No

I’m not sure what log would be useful or how to get them :/.

Configuration

Nextcloud

When I try to run sudo -u www-data php occ -h I got a php not found error. My guess is that I should run those in the docker? If someone could point me at how to get there… :frowning:

1 Like
2

It sounds like DNS or reverse proxy routing is failing specifically for iOS. The NSURLErrorDomain typically means your iOS device can’t resolve the domain name. A few things to check:

  1. DNS resolution: Make sure your iOS device can resolve the domain (try opening it in Safari).
  2. Caddy config: Ensure Caddy is routing traffic to the correct container and didn’t change after adding Forgejo.
  3. Firewall/port conflict: Verify Forgejo didn’t interfere with ports or overwrite Caddy rules.

Also, test over cellular and Wi-Fi to rule out local DNS caching issues on iOS.

1 Like
3

See AIO: How to run occ

1 Like
4

Thanks for the answer. Somehow it was bad for a day or two and then the rate of error slowed down and now it is working without problem, including with forgejo… So I have no idea how but it is fixed

Ok never mind: after 3 weeks good it is happening again