New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Config: Support non-root site URL for shared domains #425
Comments
That's not supported at the moment. Since https certs and sub domains are free nowadays, why use a path? It's also more complicated in terms of security and browser storage as AFAIK you share one local storage per (sub) domain. That can have all sorts of side effects. |
I understand this argument for classic hosting... but depending on the infrastructure unfortunately sometimes this is just not possible. In my case I'm using DynDNS where multiple subdomains are not supported and I'm reverse proxying multiple services on a single dyndns domain ( It would be awesome if either the existing setting Just my two cents. |
Dyndns wildcard domains are possible, for example with a free DigitalOcean account. Also supported by let's encrypt. |
Thank you for the quick response. Well, I'm not saying that it is impossible to solve my specific problems and I really appreciate your work. But I just would like to express, that there are definitely use cases where it would be at least more convinient to have an option for subdirectory configuration and I would surely like to vote up this issue. Photoprism is a pretty big project, otherwise I would have tried to create a pull request on my own :-) |
It's a ton of work, changing the domain / cert config is definitely easier meanwhile. Also more secure. |
Thank all contributors to this project. I have ton of website are hosted in home LAN. Such as Gogs, Vaultwarden, OMV, Portainer and so on. It seems that subpath/subdirectory may cure my pain. Luckily other projects support this, except docker registry. I understand that supporting subpath/subdirectory means changing whole architecture of the front-end. But I also hope it will come true. |
Maybe using <base href="/subdir/"> |
No, it's not that simple. |
Should would with our latest Development Preview when you configure a non-root site URL in |
@lastzero Awesome news... thank you. |
@lastzero still all I get is the PhotoPrism logo only, no login or any functional UI on the webpage. Here's the relevant part from my docker-compose: services:
photoprism:
# Use photoprism/photoprism:preview instead for testing preview builds:
image: photoprism/photoprism:preview
PHOTOPRISM_SITE_URL: "https://myserverdomain.de/photoprism/" And the settings of my nginx reverse proxy:
has the feature been disabled or is there anything I'm missing to enable this? |
@Schroedingers-Cat Think it's caused by this rewrite rule:
|
Tested this feature in the development preview. Copied link: https://.../photoprism/s/wecj8ms5k0/test Would this be caused by the internal photoprism link redirects? Doesn't appear to be caused by SWAG's config. |
For Apache 2.4 reverse proxy with non-root site url, I was successful with this config. docker-compose.yml
/etc/apache2/sites-enabled/reverse-proxy-for-photoprism.conf
|
using /prism/api/v1/ws/ solved my issue
|
may I ask how your config looks like now? |
This works for me on Nginx docker-compose.yml nginx
|
Doesnt work. Any way to check on this ? Havent been successful so far on this. |
Please don't use GitHub Issues for discussions and support questions. Thank you! ❤️ |
Hi,
I am running Photoprism behind Traefik directly on subdomain.domain.com. Everything is working fine. But when I try to run it at some non-root path, let's say /photoprism, it only shows only the big photoprism logo instead of the login form.
I tried to use the StripPrefix Middleware of Traefik which removes the /photoprism part of the URL. Still not working.
Has anyone suggestions to get this working at some non-root URL Path?
Thanks in advance
The text was updated successfully, but these errors were encountered: