Hosting: Resolve known issues when installing in a sub-directory on a shared domain

[lastzero]

Installing PhotoPrism in a subdirectory on a shared domain is possible in principle if you run it behind a reverse proxy, though still experimental and not extensively tested.

History / Background:

• After a few users asked for it, we finally implemented support for installation in a sub-directory while we were working on the front- and back-end routers anyway.
• However, we did not have time to test additional features or include automated tests to guarantee a certain feature set or stability.

Related Documentation and Discussions:

• Getting Started FAQ: Can I install PhotoPrism in a sub-directory on a shared domain?
• PHOTOPRISM_AUTO_IMPORT not working in a sub-directory on a shared domain #2386

Currently known issues that should be addressed over time if possible:

• For our Progressive Web App (PWA) to work as intended, the service worker should be installed in the root directory.
• Due to the way Web browsers function, sharing a domain with other services can affect the performance and security of all the apps installed.
• The length of sharing and other links increases and may not match the documentation.
• There may be problems with WebDAV sharing and automatic indexing/importing.

[lastzero]

Feel free to submit a pull request to document the changes that work for you as this will save us time! 👍

[lastzero]

We would appreciate it very much if someone could test the current preview for compatibility with shared domains.

[NePoCz]

Hi, I just spun-up a fresh docker image of photoprism (wanted to try it out) and already running it in a subdirectory behind NGINX. I have been using it literarly for only a few minutes and no problems so far - do you have anything specific you want me to test? I already switched to the preview image build today. Unfortunatelly I do not plan to use WebDAV or the sharing functionality, but if really needed, I can test that as well.

BTW, the links to Photoprism github user guide in the original post seem to be broken

[lastzero]

Thanks for testing! What original post? Where should we fix it?

[lastzero]

Fixed the links in the issue description 👍

[rthouvenin]

I tried to install Photoprism in a subfolder without seeing that the support was not complete, and can confirm that webDAV does not work. When I tried to connect to example.com/original, my webDAV client reports an error "moved temporarily". When I try to connect to example.com/mysubfolder/originals, I get an error "invalid credentials".

I was evaluating photoprism and in particular what will be the most convenient import method for me, so I will re-install it on a dedicated domain, but feel free to let me know if there is anything you want me to test before I discard this install.

[lastzero]

@rthouvenin Have you properly configured the PHOTOPRISM_SITE_URL to include the /path where you host PhotoPrism?

• https://docs.photoprism.app/getting-started/config-options/

Also note that the path in the URL you use to access WebDAV must be /originals/ (default) or /path/originals/ (in your case), i.e. NOT /original, /path/original or /path/originals:

• https://docs.photoprism.app/user-guide/sync/webdav/

Please note that the slash at the end of the path must not be omitted and that the WebDAV URL in your client apps needs to be updated if the hostname or port of the server changes.

[rthouvenin]

@lastzero Thank you for the hints. I typed the paths in my comment rather than pasted them, which is my the s and the final slash were missing, but I did enter when trying to connect. Sorry for the confusion.

I checked the PHOTOPRISM_SITE_URL env var, it is correctly set (the set-up was automated by Yunohost package).

I tried again just now, both with my password and an app password with "WebDAV" scope, and in both cases I get:

• /originals/ => Moved temporarily error
• /path/originals/ => Connection times out (since I get a different behaviour from what I reported yesterday, maybe I indeed mistyped the path yesterday)

The client I am using is Nemo file explorer. I am able to connect to another WebDAV server (Nextcloud) with that same client.

[rthouvenin]

Actually, now I get the "invalid credentials" error again, even though I am doing exactly what I did a few minutes ago... This happens both with my password and the app password. Could Photoprism fail to accept the webDAV connection while it is re-indexing ?

[rthouvenin]

I've tried installing Photoprism at the root of another domain and I face the same problem with webDAV (sometimes a timeout, sometimes a 401). So my problem does not seem to be linked to being installed in a subpath of a shared domain. I found an alternative to using webDAV that's more convenient for me ( mounted Photoprism folder as an external folder in Nextcloud on same host), so giving up webdav in photoprism. Sorry for reporting in the wrong issue.

For the rest of it, Photoprism works great so far!