远程访问常见问题¶

Q: What is the correct WebDAV URL?: 用于WebDAV的完整URL是。https://my.domain.tld/remote.php/webdav/，有报告说，对于本地Windows WebDAV，你可能需要。https://my.domain.tld/remote.php/dav/files/USERNAME，*USERNAME*是你想使用的用户名。

Q: Can I access my Nextcloud instance using WebDAV?: 是的，请参见`Nextcloud WebDAV 文档`_以获得完整的概述。类似unix的系统的简单挂载可能看起来像这样。``mount -t davfs https://my.domain.tld/remote.php/webdav/ /mnt/target/path``同时确保``davfs2``包已安装。对于Windows，请另外阅读这些 docs。

Q: Why does my Android smartphone's browser not open: ``http://nextbox.local``: 截至目前，使用``.local``URLs所需的技术不被各种（库存）Android浏览器支持。该机制是基于``mDNS``。一个可能的解决方法是使用第三方应用程序，如BonjourBrowser来发现你网络中的所有mDNS服务。

使用``http://nextbox.local``的访问可能不工作的原因还有几个，进一步的已知情况是。

Q: I followed all guides and still cannot acquire the TLS certificate, what can I do?: 无法获得TLS证书的原因几乎都是你的NextBox无法从互联网上到达。请确保你已经按照:doc:.../remote/walkthrough`的要求做了。如果你按照说明一步步操作，但仍然无法工作，很可能是有什么东西阻挡了连接，典型的候选人是路由器的网络管理功能，如。``MyFritz!`, ``Fritz Web Services``或类似服务，它们正在你的路由器上运行，从而阻止了80或443端口的流量。关掉它们并重新尝试获取你的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.