No, I'd just remove all of that completely. This is my production
nginx.conf file. Also note the last 2 lines...
user www-data;
worker_processes auto;
pid /run/nginx.pid;
events {
worker_connections 768;
# multi_accept on;
}
http {
##
# Basic Settings
##
sendfile on;
tcp_nopush
removed, tried, restarted everything but errors still remains.
Modified it as you had suggested but the latest error:
nginx: [emerg] unknown directive "web2py" in /etc/nginx/nginx.conf:87
On Tue, Jul 16, 2019 at 4:28 PM Jim Steil wrote:
> I would remove that and retry it.
>
> On Tue, Jul 16,
I would remove that and retry it.
On Tue, Jul 16, 2019 at 8:16 AM Maurice Waka wrote:
> Nope. Web2py example
>
> On Tue, 16 Jul 2019, 14:38 Jim Steil wrote:
>
>> Did you take that server directive out of the nginx.conf file?
>>
>> Jim
>>
>>
>> On Tue, Jul 16, 2019, 3:01 AM Maurice Waka wrote:
Nope. Web2py example
On Tue, 16 Jul 2019, 14:38 Jim Steil wrote:
> Did you take that server directive out of the nginx.conf file?
>
> Jim
>
>
> On Tue, Jul 16, 2019, 3:01 AM Maurice Waka wrote:
>
>> Used the link as you directed
>>
>> posted this:
>> # file /etc/nginx/sites-available/web2py
>>
Did you take that server directive out of the nginx.conf file?
Jim
On Tue, Jul 16, 2019, 3:01 AM Maurice Waka wrote:
> Used the link as you directed
>
> posted this:
> # file /etc/nginx/sites-available/web2py
> server {
> listen 80;
> server_name 165.22.57.107;
>
Used the link as you directed
posted this:
# file /etc/nginx/sites-available/web2py
server {
listen 80;
server_name 165.22.57.107;
#to enable correct use of response.static_version
#location ~* /(\w+)/static(?:/_[\d]+.[\d]+.[\d]+)?/(.*)$ {
#
I don't think server can be a root element in this file. Do you have it
under another element? I'd try it like this:
web2py {
server {
listen 443;
server_name server_domain_or_IP;
root html;
index index.html index.htm;
ssl on;
7 matches
Mail list logo
