Yeah I was just so confused when I found out that this isn’t possible. Like, it’s a file hosting and sync-ing application. That’s like absolute basics. It isn’t even “just” an open source project any more, there’s a company behind this product now. I am the last person to be angry about an open source project, run by a volunteer or three, not being feature complete.

For what it’s worth I think it works in the iOS version of the app (possibly always has?). But that’s doesn’t exactly help me either.

The native Android client just can’t do two way sync. Just put a text file or something into any folder (from the web or desktop). Now sync that folder to Android. Now edit it on the web/desktop, and look for the changes on Android (without actively telling it to “sync”). Then change the file on Android, these 2nd changes are never sent back to the server unless you explicitly tell it to “sync” again, manually. That’s what I mean with 2 way sync.

There are quite a few files where you just need that to work to use them properly, like the database of a password manager as a prime example. Mine can talk to Nextcloud natively, so I don’t need the client for that, but I was incredibly close to just switching to syncthing, if I didn’t have active users that use the web office integration of Nextcloud.

Nextcloud can’t do two-way sync on Android. At all. That’s like core functionality for the product IMHO and there’s a feature request open I think. When I found that out, I basically spit out my coffee. It’s fine if you just want to upload photos you take, that kinda works (but my god is it fragile).

Nextcloud is pretty good at quite a few things, including extensibility, but having some omissions in functionality that boggle the mind.

Another name, depending on the exact context, is “hairpin NAT”. Should make googling with the specific router OP has easier.

Yes I know why you have so the interfaces, but as far as I know: Linux simply can’t do what you want. So if you want to access PiAlert from your main PC on .6.X, you need to make that accessible from .6.Y on that VM. If you want to have the management port (UI) only open on the management interface, you would need to remove it’s interface on .6.X.

As I said, as far as I’m aware Linux simply can’t not route packets properly in an environment like that. I won’t respect that the interface packets came in on needs to also be the outgoing interface for the return trip. I also had that problem and eventually j I’ve just given up.

Do I understand this correctly? Your PC is on .6.X, and your connecting to the PiAlert on .1.X, but it also has an interface on .6.X? You just can’t do that with Linux. Weirdly enough I hink Windows handles this correctly and sends the responses back via your router (I think any stateful TCP connection will use the same interface both ways). This doesn’t explain why anything actually freezes though. Did the VM lock up, or is it just ssh that’s dropping?

But as for the solution: if both devices have interfaces on the same network, you should connect to that interface.