This image failed to load как исправить

Hi,

Setup

I tried to setup Ownphotos with docker-compose on my Ubuntu 18.04 VPS with a mounted 2TB disk.

Problem

The setup seems to work, i can also scan my nextcloud account, and the recognition, people, etc seems to work. Except that i can’t view any images.

Fix

So how can i fix this, is my configuration incorrectly or is there something else?

docker-compose.yml

`version: ‘2’

services:

proxy:
image: guysoft/ownphotos-proxy
tty: true
container_name: ownphotos-proxy
restart: always
links:
– “backend:backend”
– “frontend:frontend”
ports:
– “3000:80”

ownphotos-db:
image: postgres
container_name: ownphotos-db
restart: always
environment:
# This db password is internal, you can change it if you want, but also change it in ownphotos-backend container
– POSTGRES_PASSWORD=–secret–
– POSTGRES_DB=ownphotos
volumes:
– ownphotos-data:/var/lib/postgresql/data

frontend:
container_name: ownphotos-frontend
image: guysoft/ownphotos-frontend:dev
tty: true
environment:
# This is the path to the backend host public facing. if your website is ownphotos.org then this should be “ownphotos.org”.
# Default here is assuming you are running on localhost on port 3000 as given in ownphotos-proxy service
#- BACKEND_HOST=localhost:3000
– BACKEND_HOST=–secret–
links:
– “backend:backend”

backend:
image: hooram/ownphotos:dev
# For development uncomment this and comment the image name above
#build: .
container_name: ownphotos-backend
volumes:
# Your photos go here
– /mnt/bigstorage/ownphotos/data:/data
– media:/code/media
environment:
– SECRET_KEY=–secret–
# This is backend host from within the service, you dont need to change this
– BACKEND_HOST=backend
– ADMIN_EMAIL=–secret–
– ADMIN_USERNAME=admin
# Change your admin password!
– ADMIN_PASSWORD=–secret–
– DEBUG=false
– DB_BACKEND=postgresql
– DB_NAME=ownphotos
– DB_USER=postgres
# This db password is internal, you can change it if you want, but also change it in ownphotos-db container
– DB_PASS=–secret–
– DB_HOST=ownphotos-db
– DB_PORT=5432
– REDIS_HOST=ownphotos-redis
– REDIS_PORT=6379
– MAPBOX_API_KEY=–secret–
links:
– “ownphotos-db:ownphotos-db”
– “ownphotos-redis:ownphotos-redis”

ownphotos-redis:
image: redis
container_name: ownphotos-redis

adminer:
image: adminer
restart: always
ports:
– 8080:8080
container_name: ownphotos-adminer
links:
– “ownphotos-db:db”

volumes:
ownphotos-data:
media:
`

NGINX conf file

`server {
# the port your site will be served on
# the domain name it will serve for
server_name –secret–; # substitute by your FQDN and machine’s IP address
charset utf-8;

#Max upload size
client_max_body_size 75M;   # adjust to taste

# Django media
location /media  {
    internal;
    alias /code/media;      # your Django project's media files
}


# Finally, send all non-media requests to the Django server.
location / {

add_header 'Access-Control-Allow-Origin' 'https://--secret--';
add_header 'Access-Control-Allow_Credentials' 'true';
add_header 'Access-Control-Allow-Headers' 'Authorization,Accept,Origin,DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Content-Range,Range';
add_header 'Access-Control-Allow-Methods' 'GET,POST,OPTIONS,PUT,DELETE,PATCH';

    proxy_pass http://localhost:3000;
    proxy_set_header Host $host;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}

listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/--secret--/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/--secret--/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

}
server {
if ($host = –secret–) {
return 301 https://$host$request_uri;
} # managed by Certbot

listen      80;
server_name --secret--;
return 404; # managed by Certbot

}`

Hello,

When an image fails to load there are a lot of things it could be, and we will need some more information to know the cause for sure.

I have a few follow up questions to try and narrow this down, but Is the image visible to other internal service desk users? And are there any errors in the logging when the front end error occurs?

One thing I was able to locate that seems like very similar behavior can be seen in the following post where the user discovered it was caused by an add-on that needed an update, check this out to see if the behavior lines up with what you are seeing:

• https://community.atlassian.com/t5/Jira-questions/Can-t-view-attachments-in-Customer-Portal/qaq-p/753605

Regards,
Earl

I have an issue with firefox, it doesn’t load an image.All the other,Chrome, Opera and IE can load this but firefox fails, it does not display any picture and if i go check with firebug it displays the following error on the image link: “Failed to load the given URL”. I did clear my cache, also, if i open the image link in another tab it works.

THe code:

<ul class="nav navbar-nav navbar-right">
<li>
   <a style='padding:4px' href="<?php echo $login_url?>">
      <img src="<?php echo base_url(); ?>img/facebook_log22.png" class='facebookLogin' />
   </a>  
</li>
</ul>

Also in style:

.facebookLogin
{
height:40px;
} 

I’m using codeigniter(if u wonder about base_url() function) and bootstrap(but i don’t think that matters so much.

Edit: I also see that it adds another class to the code…
Also,the error: