404 and 403 using nginx Pagekit php7.2-fpm [on hold]












0















I installed nginx by following setup guide at digitalocean.



https://www.digitalocean.com/community/tutorials/how-to-install-nginx-on-ubuntu-18-04



The guide had me change root from /var/www/html to /var/www/mydomain/html.



Everything worked well from the setup, but I am recieving 403 error trying to get pagekit working.



http://w3.life/pagekit/



The installer went through all the permission changes needed and when the last one was done a 404 error ensued. The guide said:



example.com: Will respond to requests for example.com and www.example.com.
default: Will respond to any requests on port 80 that do not match the other two blocks.



How do I serve default again? I have pagekit in /var/www/mydomain/html, why can't it find it and why the 403? Permissions are 755/644 and owner is www-data:www-data



sudo cat  /etc/group
[sudo] password for david:
root:x:0:
daemon:x:1:
bin:x:2:
sys:x:3:
adm:x:4:syslog
tty:x:5:
disk:x:6:
lp:x:7:
mail:x:8:
news:x:9:
uucp:x:10:
man:x:12:
proxy:x:13:
kmem:x:15:
dialout:x:20:
fax:x:21:
voice:x:22:
cdrom:x:24:
floppy:x:25:
tape:x:26:
sudo:x:27:david
audio:x:29:
dip:x:30:
www-data:x:33:
backup:x:34:
operator:x:37:
list:x:38:
irc:x:39:
src:x:40:
gnats:x:41:
shadow:x:42:
utmp:x:43:
video:x:44:
sasl:x:45:
plugdev:x:46:
staff:x:50:
games:x:60:
users:x:100:
nogroup:x:65534:
systemd-journal:x:101:
systemd-network:x:102:
systemd-resolve:x:103:
input:x:104:
crontab:x:105:
syslog:x:106:
messagebus:x:107:
lxd:x:108:
mlocate:x:109:
uuidd:x:110:
ssh:x:111:
landscape:x:112:
david:x:1000:
mysql:x:113:

drwxr-xr-x 3 root root 4096 Mar 5 10:38 .
drwxr-xr-x 4 root root 4096 Mar 5 10:38 ..
drwxr-xr-x 3 david david 4096 Mar 5 11:25 html

server {
listen 80;
listen [::]:80;
root /var/www/w3.life/html/pagekit;
index index.php index.html index.htm;
server_name w3.life www.w3.life;

client_max_body_size 100M;

location / {
index index.php index.html index.htm;
try_files $uri $uri/ /index.php?$args;
}

location ~ .php$ {
include snippets/fastcgi-php.conf;
fastcgi_pass unix:/var/run/php/php7.2-fpm.sock;
fastcgi_param SCRIPT_FILENAME
$document_root$fastcgi_script_name;
}
}









share|improve this question















put on hold as off-topic by Thomas Ward 5 hours ago


This question appears to be off-topic. The users who voted to close gave this specific reason:


  • "This describes a problem that can't be reproduced, that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – Thomas Ward

If this question can be reworded to fit the rules in the help center, please edit the question.

















  • Let us continue this discussion in chat.

    – George Udosen
    9 hours ago






  • 1





    Can you please share your nginx config?

    – Samuel P.
    9 hours ago











  • added to question

    – ubiquitousDave
    7 hours ago











  • I am going to close this as George who is extremely knowledgeable and helpful, informed me that my configs are all out of whack, Therefore I'm restarting from scratch with the nginx manual and kicking the guides. I'll be back if a simpler config raises issues. Apache was enough and nginx promises to be simpler, once you get the correct understanding.

    – ubiquitousDave
    5 hours ago











  • THe interface will not allow me to post this as an answer.

    – ubiquitousDave
    5 hours ago
















0















I installed nginx by following setup guide at digitalocean.



https://www.digitalocean.com/community/tutorials/how-to-install-nginx-on-ubuntu-18-04



The guide had me change root from /var/www/html to /var/www/mydomain/html.



Everything worked well from the setup, but I am recieving 403 error trying to get pagekit working.



http://w3.life/pagekit/



The installer went through all the permission changes needed and when the last one was done a 404 error ensued. The guide said:



example.com: Will respond to requests for example.com and www.example.com.
default: Will respond to any requests on port 80 that do not match the other two blocks.



How do I serve default again? I have pagekit in /var/www/mydomain/html, why can't it find it and why the 403? Permissions are 755/644 and owner is www-data:www-data



sudo cat  /etc/group
[sudo] password for david:
root:x:0:
daemon:x:1:
bin:x:2:
sys:x:3:
adm:x:4:syslog
tty:x:5:
disk:x:6:
lp:x:7:
mail:x:8:
news:x:9:
uucp:x:10:
man:x:12:
proxy:x:13:
kmem:x:15:
dialout:x:20:
fax:x:21:
voice:x:22:
cdrom:x:24:
floppy:x:25:
tape:x:26:
sudo:x:27:david
audio:x:29:
dip:x:30:
www-data:x:33:
backup:x:34:
operator:x:37:
list:x:38:
irc:x:39:
src:x:40:
gnats:x:41:
shadow:x:42:
utmp:x:43:
video:x:44:
sasl:x:45:
plugdev:x:46:
staff:x:50:
games:x:60:
users:x:100:
nogroup:x:65534:
systemd-journal:x:101:
systemd-network:x:102:
systemd-resolve:x:103:
input:x:104:
crontab:x:105:
syslog:x:106:
messagebus:x:107:
lxd:x:108:
mlocate:x:109:
uuidd:x:110:
ssh:x:111:
landscape:x:112:
david:x:1000:
mysql:x:113:

drwxr-xr-x 3 root root 4096 Mar 5 10:38 .
drwxr-xr-x 4 root root 4096 Mar 5 10:38 ..
drwxr-xr-x 3 david david 4096 Mar 5 11:25 html

server {
listen 80;
listen [::]:80;
root /var/www/w3.life/html/pagekit;
index index.php index.html index.htm;
server_name w3.life www.w3.life;

client_max_body_size 100M;

location / {
index index.php index.html index.htm;
try_files $uri $uri/ /index.php?$args;
}

location ~ .php$ {
include snippets/fastcgi-php.conf;
fastcgi_pass unix:/var/run/php/php7.2-fpm.sock;
fastcgi_param SCRIPT_FILENAME
$document_root$fastcgi_script_name;
}
}









share|improve this question















put on hold as off-topic by Thomas Ward 5 hours ago


This question appears to be off-topic. The users who voted to close gave this specific reason:


  • "This describes a problem that can't be reproduced, that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – Thomas Ward

If this question can be reworded to fit the rules in the help center, please edit the question.

















  • Let us continue this discussion in chat.

    – George Udosen
    9 hours ago






  • 1





    Can you please share your nginx config?

    – Samuel P.
    9 hours ago











  • added to question

    – ubiquitousDave
    7 hours ago











  • I am going to close this as George who is extremely knowledgeable and helpful, informed me that my configs are all out of whack, Therefore I'm restarting from scratch with the nginx manual and kicking the guides. I'll be back if a simpler config raises issues. Apache was enough and nginx promises to be simpler, once you get the correct understanding.

    – ubiquitousDave
    5 hours ago











  • THe interface will not allow me to post this as an answer.

    – ubiquitousDave
    5 hours ago














0












0








0


0






I installed nginx by following setup guide at digitalocean.



https://www.digitalocean.com/community/tutorials/how-to-install-nginx-on-ubuntu-18-04



The guide had me change root from /var/www/html to /var/www/mydomain/html.



Everything worked well from the setup, but I am recieving 403 error trying to get pagekit working.



http://w3.life/pagekit/



The installer went through all the permission changes needed and when the last one was done a 404 error ensued. The guide said:



example.com: Will respond to requests for example.com and www.example.com.
default: Will respond to any requests on port 80 that do not match the other two blocks.



How do I serve default again? I have pagekit in /var/www/mydomain/html, why can't it find it and why the 403? Permissions are 755/644 and owner is www-data:www-data



sudo cat  /etc/group
[sudo] password for david:
root:x:0:
daemon:x:1:
bin:x:2:
sys:x:3:
adm:x:4:syslog
tty:x:5:
disk:x:6:
lp:x:7:
mail:x:8:
news:x:9:
uucp:x:10:
man:x:12:
proxy:x:13:
kmem:x:15:
dialout:x:20:
fax:x:21:
voice:x:22:
cdrom:x:24:
floppy:x:25:
tape:x:26:
sudo:x:27:david
audio:x:29:
dip:x:30:
www-data:x:33:
backup:x:34:
operator:x:37:
list:x:38:
irc:x:39:
src:x:40:
gnats:x:41:
shadow:x:42:
utmp:x:43:
video:x:44:
sasl:x:45:
plugdev:x:46:
staff:x:50:
games:x:60:
users:x:100:
nogroup:x:65534:
systemd-journal:x:101:
systemd-network:x:102:
systemd-resolve:x:103:
input:x:104:
crontab:x:105:
syslog:x:106:
messagebus:x:107:
lxd:x:108:
mlocate:x:109:
uuidd:x:110:
ssh:x:111:
landscape:x:112:
david:x:1000:
mysql:x:113:

drwxr-xr-x 3 root root 4096 Mar 5 10:38 .
drwxr-xr-x 4 root root 4096 Mar 5 10:38 ..
drwxr-xr-x 3 david david 4096 Mar 5 11:25 html

server {
listen 80;
listen [::]:80;
root /var/www/w3.life/html/pagekit;
index index.php index.html index.htm;
server_name w3.life www.w3.life;

client_max_body_size 100M;

location / {
index index.php index.html index.htm;
try_files $uri $uri/ /index.php?$args;
}

location ~ .php$ {
include snippets/fastcgi-php.conf;
fastcgi_pass unix:/var/run/php/php7.2-fpm.sock;
fastcgi_param SCRIPT_FILENAME
$document_root$fastcgi_script_name;
}
}









share|improve this question
















I installed nginx by following setup guide at digitalocean.



https://www.digitalocean.com/community/tutorials/how-to-install-nginx-on-ubuntu-18-04



The guide had me change root from /var/www/html to /var/www/mydomain/html.



Everything worked well from the setup, but I am recieving 403 error trying to get pagekit working.



http://w3.life/pagekit/



The installer went through all the permission changes needed and when the last one was done a 404 error ensued. The guide said:



example.com: Will respond to requests for example.com and www.example.com.
default: Will respond to any requests on port 80 that do not match the other two blocks.



How do I serve default again? I have pagekit in /var/www/mydomain/html, why can't it find it and why the 403? Permissions are 755/644 and owner is www-data:www-data



sudo cat  /etc/group
[sudo] password for david:
root:x:0:
daemon:x:1:
bin:x:2:
sys:x:3:
adm:x:4:syslog
tty:x:5:
disk:x:6:
lp:x:7:
mail:x:8:
news:x:9:
uucp:x:10:
man:x:12:
proxy:x:13:
kmem:x:15:
dialout:x:20:
fax:x:21:
voice:x:22:
cdrom:x:24:
floppy:x:25:
tape:x:26:
sudo:x:27:david
audio:x:29:
dip:x:30:
www-data:x:33:
backup:x:34:
operator:x:37:
list:x:38:
irc:x:39:
src:x:40:
gnats:x:41:
shadow:x:42:
utmp:x:43:
video:x:44:
sasl:x:45:
plugdev:x:46:
staff:x:50:
games:x:60:
users:x:100:
nogroup:x:65534:
systemd-journal:x:101:
systemd-network:x:102:
systemd-resolve:x:103:
input:x:104:
crontab:x:105:
syslog:x:106:
messagebus:x:107:
lxd:x:108:
mlocate:x:109:
uuidd:x:110:
ssh:x:111:
landscape:x:112:
david:x:1000:
mysql:x:113:

drwxr-xr-x 3 root root 4096 Mar 5 10:38 .
drwxr-xr-x 4 root root 4096 Mar 5 10:38 ..
drwxr-xr-x 3 david david 4096 Mar 5 11:25 html

server {
listen 80;
listen [::]:80;
root /var/www/w3.life/html/pagekit;
index index.php index.html index.htm;
server_name w3.life www.w3.life;

client_max_body_size 100M;

location / {
index index.php index.html index.htm;
try_files $uri $uri/ /index.php?$args;
}

location ~ .php$ {
include snippets/fastcgi-php.conf;
fastcgi_pass unix:/var/run/php/php7.2-fpm.sock;
fastcgi_param SCRIPT_FILENAME
$document_root$fastcgi_script_name;
}
}






server permissions nginx






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 7 hours ago







ubiquitousDave

















asked 9 hours ago









ubiquitousDaveubiquitousDave

212




212




put on hold as off-topic by Thomas Ward 5 hours ago


This question appears to be off-topic. The users who voted to close gave this specific reason:


  • "This describes a problem that can't be reproduced, that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – Thomas Ward

If this question can be reworded to fit the rules in the help center, please edit the question.







put on hold as off-topic by Thomas Ward 5 hours ago


This question appears to be off-topic. The users who voted to close gave this specific reason:


  • "This describes a problem that can't be reproduced, that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – Thomas Ward

If this question can be reworded to fit the rules in the help center, please edit the question.













  • Let us continue this discussion in chat.

    – George Udosen
    9 hours ago






  • 1





    Can you please share your nginx config?

    – Samuel P.
    9 hours ago











  • added to question

    – ubiquitousDave
    7 hours ago











  • I am going to close this as George who is extremely knowledgeable and helpful, informed me that my configs are all out of whack, Therefore I'm restarting from scratch with the nginx manual and kicking the guides. I'll be back if a simpler config raises issues. Apache was enough and nginx promises to be simpler, once you get the correct understanding.

    – ubiquitousDave
    5 hours ago











  • THe interface will not allow me to post this as an answer.

    – ubiquitousDave
    5 hours ago



















  • Let us continue this discussion in chat.

    – George Udosen
    9 hours ago






  • 1





    Can you please share your nginx config?

    – Samuel P.
    9 hours ago











  • added to question

    – ubiquitousDave
    7 hours ago











  • I am going to close this as George who is extremely knowledgeable and helpful, informed me that my configs are all out of whack, Therefore I'm restarting from scratch with the nginx manual and kicking the guides. I'll be back if a simpler config raises issues. Apache was enough and nginx promises to be simpler, once you get the correct understanding.

    – ubiquitousDave
    5 hours ago











  • THe interface will not allow me to post this as an answer.

    – ubiquitousDave
    5 hours ago

















Let us continue this discussion in chat.

– George Udosen
9 hours ago





Let us continue this discussion in chat.

– George Udosen
9 hours ago




1




1





Can you please share your nginx config?

– Samuel P.
9 hours ago





Can you please share your nginx config?

– Samuel P.
9 hours ago













added to question

– ubiquitousDave
7 hours ago





added to question

– ubiquitousDave
7 hours ago













I am going to close this as George who is extremely knowledgeable and helpful, informed me that my configs are all out of whack, Therefore I'm restarting from scratch with the nginx manual and kicking the guides. I'll be back if a simpler config raises issues. Apache was enough and nginx promises to be simpler, once you get the correct understanding.

– ubiquitousDave
5 hours ago





I am going to close this as George who is extremely knowledgeable and helpful, informed me that my configs are all out of whack, Therefore I'm restarting from scratch with the nginx manual and kicking the guides. I'll be back if a simpler config raises issues. Apache was enough and nginx promises to be simpler, once you get the correct understanding.

– ubiquitousDave
5 hours ago













THe interface will not allow me to post this as an answer.

– ubiquitousDave
5 hours ago





THe interface will not allow me to post this as an answer.

– ubiquitousDave
5 hours ago










1 Answer
1






active

oldest

votes


















1














I am going to close this as George who is extremely knowledgeable and helpful, informed me that my configs are all out of whack, Therefore I'm restarting from scratch with the nginx manual and kicking the guides. I'll be back if a simpler config raises issues. Apache was enough and nginx promises to be simpler, once you get the correct understanding.






share|improve this answer






























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    I am going to close this as George who is extremely knowledgeable and helpful, informed me that my configs are all out of whack, Therefore I'm restarting from scratch with the nginx manual and kicking the guides. I'll be back if a simpler config raises issues. Apache was enough and nginx promises to be simpler, once you get the correct understanding.






    share|improve this answer




























      1














      I am going to close this as George who is extremely knowledgeable and helpful, informed me that my configs are all out of whack, Therefore I'm restarting from scratch with the nginx manual and kicking the guides. I'll be back if a simpler config raises issues. Apache was enough and nginx promises to be simpler, once you get the correct understanding.






      share|improve this answer


























        1












        1








        1







        I am going to close this as George who is extremely knowledgeable and helpful, informed me that my configs are all out of whack, Therefore I'm restarting from scratch with the nginx manual and kicking the guides. I'll be back if a simpler config raises issues. Apache was enough and nginx promises to be simpler, once you get the correct understanding.






        share|improve this answer













        I am going to close this as George who is extremely knowledgeable and helpful, informed me that my configs are all out of whack, Therefore I'm restarting from scratch with the nginx manual and kicking the guides. I'll be back if a simpler config raises issues. Apache was enough and nginx promises to be simpler, once you get the correct understanding.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 5 hours ago









        ubiquitousDaveubiquitousDave

        212




        212















            Popular posts from this blog

            GameSpot

            日野市

            Tu-95轟炸機