Valid response back, no image on server

[scorobogaci]

Server response is ok
{"status":"OK","type":"png","hash":"1ucq23hnr5.png","url":"http:\/\/192.168.99.100\/1ucq23hnr5.png","domain":"http:\/\/192.168.99.100"}

But image is not present in upload folder

[scorobogaci]

Accesing after the url : http://192.168.99.100/1ucq23hnr5.png
redirects to the default upload page

[geek-at]

looks like you have permission problems. check if the upload folders are created

[scorobogaci]

@chrisiaut , upload folder is created inside container
/usr/share/nginx/html/upload exists

[geek-at]

yeah but inside the upload folder is the 1ucq23hnr5.png folder created?

[scorobogaci]

@chrisiaut nope, 1ucq23hnr5.png folder isn't created
also, sometimes image after upload appears for preview, sometimes not . but when clicking on the image, it redirects to default page

[geek-at]

must be a permission problem then

[scorobogaci]

logs from error.log on the container

2017/08/14 15:54:21 [error] 229#229: *59 FastCGI sent in stderr: "PHP message: P
HP Notice: Undefined index: HTTPS in /usr/share/nginx/html/index.php on line 17
" while reading response header from upstream, client: , server: _,
request: "POST / HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168
.99.100", referrer: "http://192.168.99.100/"
2017/08/14 15:55:12 [error] 231#231: *63 FastCGI sent in stderr: "PHP message: P
HP Notice: Undefined index: HTTPS in /usr/share/nginx/html/index.php on line 17
" while reading response header from upstream, client: , server: _,
request: "POST /17aa3ngtwl.jpg HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000",
host: "192.168.99.100", referrer: "http://192.168.99.100/17aa3ngtwl.jpg"

[geek-at]

that's just notices, nothing unusual. No seriously check the permissions of the upload folder

[scorobogaci]

[scorobogaci]

at permissions level seems to be ok

[geek-at]

try the command

sudo su -c "touch /usr/share/nginx/html/upload/check" nginx

and see if it gets created or if it says permission denied

[scorobogaci]

I know it;s kind of strange, but after restarting pc , everything worked
I've metioned that i have an app on :9000 port , and somehow SGI remember the request from that app, which is using this service, and even that after I'm making request from the app page, it still apend on the log file the old request from :9000

[scorobogaci]

sudo su -c "touch /usr/share/nginx/html/upload/check" nginx
sudo is not available in container :(

[scorobogaci]

@chrisiaut thank you for your help :)
Can you also add cors requests to the app, things like :
header('Access-Control-Allow-Origin: *'); header('Access-Control-Allow-Methods: GET, POST, PUT, DELETE'); header('Access-Control-Allow-Headers: Authorization');

I don't know it this is a good practice , but maybe you have another idea or good practice to deal with it