Cannot access via WAN and LAN through a single "account"
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 2.5k
- Forks
- 1k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 13
Description
Steps to reproduce
- Try to access from LAN and WAN from the same server name login without hairpinning/own DNS server.
Expected behaviour
Ideally, it should be possible to configure the iOS app so that LAN IP is used as a preference, and WAN (ddns or static ip) when the server is not reachable via the LAN IP. Configurations are possible with some routers to solve this, but not all, and it would seem to be a better blanket approach to fix it within nextcloud.
Actual behaviour
It is necessary to have two "accounts" set on the iOS app. accounts in "" because it will be the same actual nextcloud login, but with different server details for the access route.
Reasoning or why should it be changed/implemented?
It would prevent having to keep switching accounts when on site/off site
Environment data
**iOS version:15.2
**Nextcloud iOS app version:4.2.2.7
**Server operating system:TrueNAS Core 12.0
Web server: nginx i think?
**Nextcloud version: 23.0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test entry point is named; begin with the iOS app's account and server-connection configuration. Trace how a single account could prefer a LAN address and fall back to WAN, and define verification for access from both networks without switching accounts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, swift
- Domain
- mobile, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100