No access to my nextcloudpi trough my fritzbox

,

Hallo, I don’t know if I be at the right spot with my question, I setup a new raspberry pi5 with nextcloudpi, I connected it over a LAN cable to my Fritz Box but it is impossible to reach it over my Webbrowser, all Computers are connected to the same FRITZ!Box, I also can open it and the IP address of the Nextcloud Pi shows up fine, I hooked up a screen to the pi to see the boot sequence, it looks ok for me, be au at the end it tells me to access it over my Webbrowser on https://nextcloudpi.local but it doesn’t respond, I tried Safari, Firefox, chromium and torbrowser.
My goal is to use it as a sync point for my Vollaphone and on a second drive for the pictures of the iPhone of my wife, but that later. I have no idea where to start with the trouble shooting.

No response or no expected response?
Try

https://<ip-number>

instead.
So we have to check your server is working as expected or you networksettings need some setup.

You can maybe figure out the IP address in the device list of Fritz!OS. It lists all devices with the local IP addresses which you can try to reach via HTTP by trial and error. The less devices you have in your network, the easier. Not an elegant approach but sometimes it helped me, too. :smile:

Well, if @MP28 was able to setup a Nextcloud on a Raspberry pi5 he was most likely using ssh to do so. So he shall know the IP-Adress of his Raspberry pi5. If not he can use

ifconfig

as root or sudo.
That will show IPv4- and IPv6-Adress of his pi5. There is no need to search in the FritzBox.

Hallo, thanks for so many answers, the IP adress is marked as fix in the Fritz box it is 192.168.178.57, I tried to ping it from my Linux mint pc and it responded with ping 192.168.178.57 56(84) bytes of data
192.168.178.43 icmp_seq=1 destination host unreachable , this continues 142 times.

No response at all, not with the ip address as well.

Not pingable - not reachable, of course the server is not responding.

Check your networkconiguration,
Simpelst thing, the machine you ping from is in “guest-net”,
check

hostname -I

General proposal, use dhcp, you can configure the address-pool and even advice to fix addresses.

But does your Pi5 know and get this IP 192.168.178.57. Check your Pi5’s network-Config. Check whether the Pi5 has a configured DCHP-Client or is usuing a fixed IP-Adress, which is not 192.168.178.57

What’s that?(192.168.178.43)
Please cite your commands from prompt (input) - (output) prompt as in (exp.):

georg@HEKA:~$ hostname -I

172.24.246.3

georg@HEKA:~$ ping 192.168.2.49

PING 192.168.2.49 (192.168.2.49) 56(84) bytes of data.
64 bytes from 192.168.2.49: icmp_seq=1 ttl=63 time=3.32 ms
64 bytes from 192.168.2.49: icmp_seq=2 ttl=63 time=3.27 ms
64 bytes from 192.168.2.49: icmp_seq=3 ttl=63 time=3.46 ms
64 bytes from 192.168.2.49: icmp_seq=4 ttl=63 time=3.32 ms
64 bytes from 192.168.2.49: icmp_seq=5 ttl=63 time=3.31 ms
64 bytes from 192.168.2.49: icmp_seq=6 ttl=63 time=3.45 ms
64 bytes from 192.168.2.49: icmp_seq=7 ttl=63 time=3.31 ms
64 bytes from 192.168.2.49: icmp_seq=8 ttl=63 time=5.68 ms
64 bytes from 192.168.2.49: icmp_seq=9 ttl=63 time=4.75 ms
64 bytes from 192.168.2.49: icmp_seq=10 ttl=63 time=4.90 ms
64 bytes from 192.168.2.49: icmp_seq=11 ttl=63 time=3.33 ms
64 bytes from 192.168.2.49: icmp_seq=12 ttl=63 time=4.10 ms
^C
— 192.168.2.49 ping statistics —
12 packets transmitted, 12 received, 0% packet loss, time 11019ms
rtt min/avg/max/mdev = 3.267/3.849/5.681/0.785 ms
georg@HEKA:~$

This prompt lines I can Input them from my Linux pc or I need to input them on the Raspberry pi?

As far as I understand your situation you gave some spare information you are sitting in front of screen at your pi with a login prompt you can not login, or on your linux-pc watching the network page of your router (fritz box). From your linux pc you tried to access your pi device pinging it or your ncp-server on your pi via web browsing, both without success.

This spare information leads to my pure guess work, the easiest way explaining this situation is;
Your linux pc is a laptop connected to your fritz box wireless via guest-net, your pi5 is connected via ethernet cable to your fritz box, therefore not reachable. Nice guess - but no evidence.

Of course from your linux pc.
The first example prompt could give answer to the snippet you gave

another ip address we have to sort in.
The second is self declaring.

Tranks for the Feedback, I be trying to access the Raspberry pi over my browser, the Linux pc I be using, is my full-size working machine, no laptop, I be running Linux mint on it and it ist connected by LAN, no wifi in use. I will trie as soon as I can and post the results.

Ok, than we have to know all of you (your setup) :wink:
How did you flash your ncp-image?
I recommend nothing other than rpi-imager no presets set.

PING 192.168.178.57 (192.168.178.57) 56(84) bytes of data.
64 bytes from 192.168.178.57: icmp_seq=1 ttl=64 time=1.36 ms
64 bytes from 192.168.178.57: icmp_seq=2 ttl=64 time=1.29 ms
64 bytes from 192.168.178.57: icmp_seq=3 ttl=64 time=1.34 ms
64 bytes from 192.168.178.57: icmp_seq=4 ttl=64 time=0.211 ms
64 bytes from 192.168.178.57: icmp_seq=5 ttl=64 time=0.209 ms
64 bytes from 192.168.178.57: icmp_seq=6 ttl=64 time=0.193 ms
64 bytes from 192.168.178.57: icmp_seq=7 ttl=64 time=0.192 ms
64 bytes from 192.168.178.57: icmp_seq=8 ttl=64 time=0.198 ms
64 bytes from 192.168.178.57: icmp_seq=9 ttl=64 time=0.200 ms
The lines continue still further.

The prompt i used was ping 192.168.178.57 -l 3
If i be interpreting the answers back from it, the nextcloudpi is responding?
I asked for 3 packages.

I used Raspberry pi imager v. 1.8.5 to create the bootable SD card.
I hooked it up to my screen to see if it was booting. If there is any need i can try to get a pic of the screen and show it to you.

I am sorry and apologize if it looks unhandy but i am not a programmer and with networking i have very little experience.

Thanks a lot

There is no need to apologize, I am “only” a user too, we meet here trying to solve problems.

So your rpi5 is up and running and is reachable on the network. Your nextcloud server should be pingable too.

georg@HEKA:~$ ping nextcloudpi
PING nextcloudpi (192.168.2.32) 56(84) bytes of data.
64 bytes from nextcloudpi.fritz.box (192.168.2.32): icmp_seq=1 ttl=63 time=2.91 ms
64 bytes from nextcloudpi.fritz.box (192.168.2.32): icmp_seq=2 ttl=63 time=2.82 ms
64 bytes from nextcloudpi.fritz.box (192.168.2.32): icmp_seq=3 ttl=63 time=2.52 ms
64 bytes from nextcloudpi.fritz.box (192.168.2.32): icmp_seq=4 ttl=63 time=2.77 ms
64 bytes from nextcloudpi.fritz.box (192.168.2.32): icmp_seq=5 ttl=63 time=2.79 ms
64 bytes from nextcloudpi.fritz.box (192.168.2.32): icmp_seq=6 ttl=63 time=2.75 ms
^C
--- nextcloudpi ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5008ms
rtt min/avg/max/mdev = 2.522/2.759/2.912/0.118 ms
georg@HEKA:~$

Now you should be able to get the activation page in your webbrowser, js enabled no blocker.

who cares? It does not matter at all what Linux-Distro you use beside the Raspberry pi. What you have to do was using a Terminal WIndow or any other command line prompt and the usual and hopefully well known command line commands to check and configure the network of your Raspberry pi. That could be done on the Pi itself by using a keyboard and a Monitor connected to the Pi, or (if networks is running and ssh-access is possible) remote by using another device. No matter it is Linux mint, Fedora or even WIndows.

I wonder how MP28 should access his device, he flashed it with the latest nextcloudpi image and struggles to get the activation page and start setting up access. May you tell me, what credentials should do the trick?

How about editing configs on Pi, using a keyboard and a Monitor?

If i do not have remote Access to any of my Linux devices i do use keyboard and a Monitor and configure Network and OpenSSH-Server.

Edit: and on a SD-Card, like used in Pi’s even no keyboard and a Monitor is needed. Just remove the SD-Card, put it in a Card reader on any other device and edit it from there. Then put SD-Card back into Pi and boot it again. All files needs to be edited must be on the SD-Card.

Thank you for this profound explanation, would you please be so kind and offer me advice which file should be changed in which manner so the nextcloudpi server will be able to function as expected?

How should I name specific files if @MP28 returns insufficient or contradictory error messages?

  1. Error was:
  1. then this Message somewhat later

So now ping works.

But he never told us result of using https://192.168.178.57/ instead of https://nextcloudpi.local

With no propper description of the error(s), no concrete help is possible. And don’t say @MP28 was not asked to do so. He was asked to do so before by @iva.horn and i usualy don’t ask twice just because @MP28 ignoring offers to help.