Closed jbtruffault closed 5 years ago
Dont remove ownphotos-proxy. It routes between the frontend and backend.
I don't know if this can be the pb, I do thee routing with my own nginx instance, just rewrote the ownphoto proxy conf:
server{
listen 443 ssl;
server_name my_url;
index index.html index.php;
proxy_connect_timeout 600;
proxy_send_timeout 600;
proxy_read_timeout 600;
send_timeout 600;
client_max_body_size 1024m;
location / {
proxy_pass http://ownphotos_frontend:3000;
include /etc/nginx/proxy_params;
}
location /api {
proxy_pass http://ownphotos_backend/api;
include /etc/nginx/proxy_params;
}
location /media {
proxy_pass http://ownphotos_backend/media;
include /etc/nginx/proxy_params;
}
ssl_certificate /etc/letsencrypt/live/my_url/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/my_url/privkey.pem; # managed by Certbot
}
The issues came from a wrong way to restart my docker-compose: I should delete all my volumes as I changed the docker-compose.yml file after build it a first time
The magic command was:
docker-compose down --volumes --remove-orphans; docker-compose up -d
Thanks for updating the fix
Hi everyone !
I'm facing the following error just after ownphotos installation through the following docker-compose:
I have my own nginx reverse-proxy, that is the reason why I removed the ownphotos-proxy.
Just after a login try, I get this error screen:
Does anyone would have an idea of what is going on ?
Thanks !