-
-
Notifications
You must be signed in to change notification settings - Fork 295
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot access on-device with localhost or 127.0.0.1 #1812
Comments
This also happens on a clean install of Raspberry Pi OS with the latest version of NextcloudPi installed through the curl install script. NextcloudPi diagnostics
Nextcloud configuration
HTTPd logs
Database logs
Nextcloud logs
|
This doesn't seem to be an actual issue. What does seem to be the case, is that Tailscale now requires you use a different command to serve (and funnel) a site with a self-signed HTTPS certificate: Serving the site with the normal command Once you serve the site, you can then generate a proper HTTPS certificate. It appears that, without this certificate, only connections to port 443 will work over Tailscale. Other ports, such as 4443, will complain that they're using a self-signed certificate. But they were before the serving as well, so I'm not sure what's going on here. Additionally, even after generating the certificate, you still cannot serve the site using the normal command. |
When SSHing into my Pi 4 running NextcloudPi (a clean install with the latest version of NextcloudPi, latest version of Nextcloud, and all packages being up-to-date), I cannot access Nextcloud over https://localhost or https://127.0.0.1. Only https://0.0.0.0. I have tested this with curl, which comes back with no output for the first two.
This is an issue because I would like to use Tailscale Funnel to be able to access my Nextcloud instance from outside my network, and this tool doesn't support https://0.0.0.0. When using https://localhost as the site to make accessible, visiting it in a browser shows nothing.
System information
NextcloudPi diagnostics
Nextcloud configuration
HTTPd logs
Database logs
Nextcloud logs
The text was updated successfully, but these errors were encountered: