Hi,

I experienced the very same issue on my iPad today.

I'm running Piwigo on a local server (let's say, it has the hostname SRV) as a docker container. As I have no other services sitting on the default port 80, I configured Piwigo to port 80. Like you, I do not use SSL.

So, I usually can access it typing

http://srv

in the browser.

The Piwigo app on my iPad will not connect with the above setting. Coincidentally, I've found out that

http://srv:80 works instead.

HTH,
Daniel

Last edited by dma (2020-05-17 21:57:36)

> I think by default Apache is using port 80.

This is true for sure, but the iOS Piwigo app seems to ignore this. Therefore the setting must be done explicitely as part of the URL.

> Do you use piwigo for your primary photo management on your NAS?

Yes, after years of messing around and copying my photo lib back and forth across all the devices existing in my household, I started investigating whether there is something which would suit my needs better (searching for tags, providing a central database to all my family members regardless of the device they use, quick delivery of the photos etc.).

For some reason, it was not easy for me to "find" Piwigo... I never heard of it before I started my investigation.

> I had previously used Nextcloud photos but it seemed slow and I thought Piwigo would be a better solution.

Yes, I'm using NC in my network, too. This is mainly to manage all my paper work (which is actually no paper in 99% of time) and all my ebook library. I really love it (especially the full text search abilities based on Elastic Search). But, when it  comes to manage your photos, you can simply forget it. It is ways to slow and lacking of meta data search...

Daniel

Same story. I recently installed Piwigo and had a hard time getting into my library from my iOS device. The fact that you need to enter the port number should be documented more clearly or corrected. When entering a web location and entering http or https should default to port 80 or 443 respectively.
I am very happy with the performance of Piwigo so far.

HMunky, did you make sure that the piwigo iOS app is allowed to access local network? It is somewhere in general settings. For some reason, iOS apps are blocked by default.

Wow, how did you manage to run iPhone app on Windows?
For iPad, I suggest to remove the app and install it again. It should work - very strange it doesn't...

Hi All,

The iOS app is identical to the iPadOS one as far as connections are concerned.

By default, when the user does not type "http://" or 'https://", the app tries "https" on port 443. If it fails, it suggests to use an unsecured connection and tries "http" on port 80 if the user requests it. What I understand from this thread is that it should re-ask the user's agreement (unless there is a regression).

To answer questions you may have:
- It is necessary to type the port number only if it is different than the default ports 80 for http and 443 for https.
- When the SSL certificate is not secure, the app asks if it should accept it (e.g. self-signed certificates). It saves it for future connections after approval.
- The app manages simple HTTP basic access authentication.

Hope this helps,
Eddy