Hi and thanx for ur reply.
The solution is "sudo setenforce Permissive "
thanx and regards
On Tuesday, March 21, 2017 at 2:21:29 PM UTC+1, Jan Miszura wrote:
>
> I was having the same issue and it was solved with "sudo chmod 777
> /socket". It's not necessary manually create uwsgi.sock.
>
> Goo
I was having the same issue and it was solved with "sudo chmod 777
/socket". It's not necessary manually create uwsgi.sock.
Good luck!
Jan
On Tue, Mar 21, 2017 at 9:16 AM, valerio orfano
wrote:
> BTW i ve created the uwsgi.sock manually gave permission 777 and changes
> the owner from root to n
BTW i ve created the uwsgi.sock manually gave permission 777 and changes
the owner from root to nginx:nginx
On Tuesday, March 21, 2017 at 1:10:22 PM UTC+1, valerio orfano wrote:
>
> Hi folks i have django 1.9 application integrated to nginx via uwsgi
> application on Centos7.
> It was working f
Hi folks i have django 1.9 application integrated to nginx via uwsgi
application on Centos7.
It was working fine, but then i had to reboot my machine. Now i am having
the follwoing issue: unix:/socket/uwsgi.sock failed (13: Permission
denied) while connecting to upstream, client: 10.184.160.9,
4 matches
Mail list logo
