Pogosta vprašanja o oddaljenem dostopu¶

Q: What is the correct WebDAV URL?: Celoten naslov URL, ki ga uporabite za WebDAV, je: https://my.domain.tld/remote.php/webdav/, obstajajo poročila, da bi za izvirni WebDAV za Windows lahko potrebovali: https://my.domain.tld/remote.php/dav/files/USERNAME, pri čemer je USERNAME uporabniško ime, ki ga želite uporabiti.

Q: Can I access my Nextcloud instance using WebDAV?: Da, popoln pregled najdete v Dokumentaciji Nextcloud WebDAV. Enostavna namestitev za sisteme, podobne Unixu, je lahko videti takole: mount -t davfs https://my.domain.tld/remote.php/webdav/ /mnt/target/path, pri čemer se prepričajte, da je nameščen davfs2 paket. Za Windows dodatno preberite te docs.

Q: Why does my Android smartphone’s browser not open: ``http://nextbox.local``: Danes tehnologija, potrebna za uporabo .local URL-jev, ni podprta v različnih (osnovnih) brskalnikih Android. Mehanizem temelji na mDNS. Ena od možnih rešitev je uporaba aplikacije tretje osebe, kot je BonjourBrowser, ki odkrije vse storitve mDNS v vašem omrežju.

Obstaja več drugih razlogov, zakaj dostop z uporabo http://nextbox.local morda ne bo deloval:

Pri uporabi naprave Fritz!Box, ko je NextBox povezan prek vrat LAN, odjemalec/brskalnik pa je v omrežje povezan prek WiFI (WLAN), naprava Fritz!Box blokira mDNS.

Q: I followed all guides and still cannot acquire the TLS certificate, what can I do?: Razlog, da potrdila TLS ni mogoče pridobiti, je skoraj vedno dejstvo, da vaš NextBox ni dosegljiv iz interneta. Prepričajte se, da ste sledili navodilom v Pregled oddaljenega dostopa. Če ste sledili navodilom po korakih in še vedno ne deluje, zelo verjetno nekaj blokira povezavo, tipični kandidati so funkcije spletnega upravljanja usmerjevalnika, kot npr: MyFritz!, Fritz Web Services ali podobne storitve, ki se izvajajo v usmerjevalniku in tako blokirajo promet na vratih 80 in/ali 443. Izklopite jih in ponovno poskusite pridobiti potrdilo TLS.

Q: Why is my reachability with IPv4 not working?: If you have properly set up port forwarding and IPv4 connections (reachability test) are still not working there are good chances that your Internet-Service-Provider (ISP) does not provide a proper (public) IPv4 address to you. There are several (end-customer) internet technologies, which do not allow incoming traffic for the IPv4, which was assigned to you. An incomplete list is: private IPv4 address, DS-Lite connection or CarrierGrade-NAT (CG-NAT). All these essentially share one IPv4 address across multiple users, thus block (incoming) traffic from the internet to you. Some ISPs allow upgrading to so-called full-stack connections, which should enable full bi-directional traffic for IPv4 and IPv6.

Q: Why do some devices fail to connect for my IPv6 configured NextBox?: Sadly, still not all ISPs and mobile-network providers (smartphones) do have full IPv6 support activated. This means, if your NextBox is configured for IPv6 only access, devices inside these networks will not be able to connect. The backwards-proxy does work as a workaround here, as it provides an IPv4 entrypoint to your NextBox independent of your other remote access configuration.