Iām trying to create a stand alone NextCloudPi for travel. My goal is to be able to run the Pi off a USB power pack and have the Pi host a WiFi AP so family can connect to the AP, open the NextCloud app and share pictures without the complications and security concerns of joining the Pi to a local WiFi network. This also allows us to share media without any requirement for internet access at all (else I would cloud host it).
Iāve been successful with the following:
NextCloudPi installed/configured connected into home network via eth0
Pi hosting secured WiFi AP
iOS NextCloud app connecting to server at IP on home network
iOS device successfully connects to Pi WiFi AP and receives IP via DHCP
However, once connected to the wifi AP the iOS NextCloud app gives a āBad Connectionā error when directed to connect to the serverās IP address in the wifi network.
Iāve tried to find some documentation/tutorials on this kind of setup but my Google-fu has failed me thus far.
Thatās a very unusual thing to try to do. I think youāre likely to run into weird problems like that which may or may not be resolvable. The iOS app isnāt going to be happy about having no internet on the ad hoc connection.
Thanks for the input and point outs. The home network connection was simply to make it easy for updating packages. Once I stepped away to travel it would be entirely self-contained. Iām not super concerned about https connections and refreshing certs as my āaccess controlā is not sharing the WPA2 key for the wifi with anyone but trusted agents.
KarlF12, youāre right that iOS sometimes squawked about not being connected to the internet.
wwe summed it up well as a ālocal network to go.ā
Iāll do some checking, but could it be as simple as the iOS client refusing http or unsigned https connections?