Issue: unable to access Nextcloud unless using the machine where Nextcloudpi is installed.
What would need configuring to fix this?
Summary:
Nextcloudpi in Docker installed on Raspberry Pi.
Able to access Nextcloud (https: //< RPi_IP >) and see NCP Activation page (https: //< RPi_IP> / activate /) only when browsing on the RPi.
When using other machines on the same LAN as RPi results in 403 error when trying to access Nextcloud (https: //< RPi_IP >).
Able to SSH into the RPi using other machines on the same LAN as the RPi.
Only need Nextcloud accessible on LAN.
Original post:
Hi all,
I’m a beginner Linux user.
Issue: 403 forbidden when trying to activate/access https://< RPi_IP > after installation. Unable to access wizard on https://< RPi_IP >:4443/
Nextcloudpi installed on RPi3B+.
Trying to access Nextcloud from laptop.
Using Raspbian Buster Lite.
SSH into RPi from laptop.
Installed Docker and ran: docker run -d -p 4443:4443 -p 443:443 -p 80:80 -v ncdata:/data --name nextcloudpi ownyourbits/nextcloudpi $DOMAIN
Waited for ‘Init done’.
But 403 on https://< RPi_IP >
On a fresh image I have tried installing NCP using cURL method and on another fresh SD used the NextCloudPi system image: https:// ownyourbits. com/downloads/NextCloudPi_RPi_03-28-20/
But both methods still cannot access Nextcloud from https://<RPi_IP> on laptop as it results in 403 forbidden error. Unable to access wizard https://< RPi_IP >:4443/
Would prefer getting NCP working on Docker. How would I diagnose this issue? (beginner-friendly advice please).
Maybe you can provide a screenshot, and info on browser used.
You have to add an exception to by-pass the warning when wisiting a site with a selfsigned certificate for the first time. Et Least until you get a valid Letsencrypt certificate…
Check docs for steps
In Warning screen. Click advanced and add exception to proceed.
In short: unable to access Nextcloud unless using the machine where Nextcloudpi is installed.
Decided to do a completely fresh install.
This time using Raspbian Buster with desktop instead of Raspbian Buster Lite.
Went through the process of installing Nextcloudpi in Docker (using laptop to SSH into RPi).
On the laptop was still getting 403 error on the NCP page (https://< RPi_IP >).
But using the browser on the RPi (where NCP is installed), I was able to gain access to the NCP Activation page (https://< RPi_IP> / activate /).
So I’m unable to access Nextcloud unless I’m using the machine where Nextcloudpi is installed.
The laptop and RPi are connected on the same LAN.
Is there something that needs configuring?
Summary:
Nextcloudpi in Docker installed on Raspberry Pi.
Able to access Nextcloud (https://< RPi_IP >) and see NCP Activation page (https://< RPi_IP> / activate /) only when browsing on the RPi.
When using other machines on the same LAN as RPi results in 403 error when trying to access Nextcloud (https://< RPi_IP >).
Able to SSH into the RPi using other machines on the same LAN as the RPi.
Only need Nextcloud accessible on LAN.
NextCloudPi version v1.24.0
NextCloudPi image NextCloudPi_docker_04-06-20
distribution Debian GNU/Linux 10 \n \l
automount no
USB devices none
datadir /data/nextcloud/data
data in SD yes
data filesystem ext2/ext3
data disk usage 4.7G/15G
rootfs usage 4.7G/15G
swapfile /var/swap
dbdir /data/database
Nextcloud check ok
Nextcloud version 18.0.3.0
HTTPD service up
PHP service up
MariaDB service up
Redis service up
Postfix service up
internet check ok
port check 80 closed
port check 443 open
IP ***REMOVED SENSITIVE VALUE***
gateway ***REMOVED SENSITIVE VALUE***
interface eth0
certificates ***REMOVED SENSITIVE VALUE***
NAT loopback no
uptime 17:11
<RequireAny>
Require host localhost
Require local
Require ip 192.168
Require ip 172
Require ip 10
Require ip fe80::/10
Require ip fd00::/8
</RequireAny>
Could this be a requirement to activate then access NCP locally through the browser? (Didn’t see any documentation mention requirements).
Anyone able to verify if using an address outside the above private addresses causes issues?