I’ve done the same.
Try listen port 8080, as anything < port 1024 needs to run as root. Then in
your url, enter hedge.local:8080. Shove hedge.local into your /etc/hosts file
and point to the proper IP. But you need to enter the port number in that url
to fetch it on the LAN.
> On Jul 23,
> On Jul 15, 2017, at 6:24 AM, nanaya wrote:
>
>> If I deliberately start up using root, why would I need a directive that
>> indicates that? This directive seems like a reminder after the fact.
>>
>
> root is usually needed to bind port 80 and 443 so usually people want to
> start it using
> On Jul 15, 2017, at 5:04 AM, nanaya wrote:
>
>
> It works if you start it from user with root privilege. Otherwise you
> can't switch user and thus the directive is ignored.
If I deliberately start up using root, why would I need a directive that
indicates that? This directive seems like a
The latter. It makes little sense. If it’s ignored then there’s no sense in
having it.
Much like how the current `nginx -t` report makes little sense as well:
nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok
nginx: [emerg] open() "/var/run/nginx.pid" failed (13: Per
OK, good to know. Thank you. This does suggest that security isn’t really
respected in this case.
Cheers
> On Jul 14, 2017, at 11:04 AM, Alberto Castillo wrote:
>
> I've just set up mine on a FreeBSD box and using sudo solves the
> problem, same issue with .pid.
_
Rich in T
Hi there.
> On Jul 14, 2017, at 9:29 AM, Francis Daly wrote:
>
> In unix land, usually, if a process starts running as root, then it is
> able to "switch" to run as another user. If a process starts running as
> non-root, it is not able to switch to run as another user.
>
> And (usually) only r
> On Jul 13, 2017, at 9:31 PM, li...@lazygranch.com wrote:
>
> However the nginx process is owned by www:
> 823 www 1 200 28552K 7060K kqread 0:01 0.00% nginx
Sure the process is owned, and is called upon by nginx as the www user. The
`nginx -t` report is being called by ri
Hi there. Thanks for the reply.
Persistent permissions issues are on other boxes, on OSX as well. But I had
some Passenger issues so I’ve moved into another issue.
But sudo nginx -t gets rid of the error on nginx.pid
That whole user/group issue on the user directive in nginx.conf is confusing
Hi folks. Trying to get this FreeBSD nginx installation set up.
FreeBSD 11.1-RC1
nginx version: nginx/1.12.0
3 vhosts on this box. nginx.conf tests show the following:
[Wed Jul 12 06:08:41 rich@neb /var/log/nginx] nginx -t
nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax
Just wondering where the best location is for www on FreeBSD.
The default nginx.conf reports /usr/local/www/nginx
But then it reports this:
[Wed Jul 12 05:10:09 rich@neb /usr/local/www/nginx] ll
dr-xr-xr-x 2 root wheel5 Jul 7 10:23 .
drwxr-xr-x 3 root wheel4 Jul 7 10:23 ..
-rw-r--r
nginx.conf sets the user and admin, but that coughs up an error when trying to
run as root. This is why it’s so confusing.
> On Jul 10, 2017, at 9:27 PM, li...@lazygranch.com wrote:
>
> I don't have server access at the moment, but I think nginx under FreeBSD
> runs under user www.
__
Hi there.
Looking to get port 80 serving. Changed to root, but the error keeps the user
from running:
nginx: [warn] the "user" directive makes sense only if the master process runs
with super-user privileges, ignored in /usr/local/etc/nginx/nginx.conf:2
nginx: the configuration file /usr/loca
Never mind. Solved.
> On Sep 28, 2016, at 6:12 PM, Viaduct Lists
> wrote:
>
> Hi folks. A localhost passenger domain (hq.local) isn’t showing up on my
> local Safari. It’s pointed properly in the hosts file and Firefox takes
> about 10 seconds to show it, but Safari
Hi folks. A localhost passenger domain (hq.local) isn’t showing up on my local
Safari. It’s pointed properly in the hosts file and Firefox takes about 10
seconds to show it, but Safari just waits for it. Curl also takes about 10
seconds to show the page, but it does show up using:
curl —basi
> On Oct 30, 2015, at 7:02 PM, Francis Daly wrote:
>
> You must nominate a user and group to run nginx as.
>
> If you don't explicitly name a group, you implicitly name the group with
> the same name as the user.
>
> So: name a group that exists. Possibly the same one that your working apache
Hi Robert.
rich is my normal admin user on my workstation. I tried it knowing that the
files in my /Library/WebServer/Documents/ are owned by rich. Some groups are
wheel and admin.
This is OSX (OpenBSD). That getgrnam("rich”) reply was from testing the
nginx.conf file.
I’ve not gone do
403 error. Not sure who to run
nginx as.
Cheers
> On Oct 30, 2015, at 5:20 PM, Viaduct Lists
> wrote:
>
> Hi folks.
>
> I’m getting 403’s on all my locahost domains. All are entered into
> /etc/hosts as 127.0.0.1, and were working when using Apache.
>
> Nothing
Hi folks.
I’m getting 403’s on all my locahost domains. All are entered into /etc/hosts
as 127.0.0.1, and were working when using Apache.
Nothing is showing up in the access or error log. Some domains are owned by
rich/wheel and some by rich/admin. I’m using passenger with these, and I can
18 matches
Mail list logo
