A question can only have one accepted answer. Are you sure you want to replace the current answer with this one?
You previously marked this answer as accepted. Are you sure you want to unaccept it?
Ghost has NGINX and Node…other generally have one of the three. Plus there is PM2, CertBot, VNC, etc.
Is it simpler to just build it from scratch?
A corollary problem is that the upgrade from 16.04 to 18.04 fails, but search the web or posting here hasn’t produced an answer to the problem.
Thanks,
David
Hey friend,
If you have custom needs, building from scratch is always a good way to go. Just break up the pieces individually and focus on each one by itself until you have it all where you need it.
What happens when you upgrade to Ubuntu 18 from 16? I ask, but I should also say that I never recommend upgrading a full distro release in place. The only time I truly expect that to go off without issue is when the system is in it’s default state, without production services running. Too many things change between full distro versions.
Jarland
This is all about installing WordPress with Easyengine. Everything goes fine while installing easyengine and its stack with ubuntu 16.04. but now getting issue on installation when the datacenter region changes. with new-york datacenter, installation works fine when it changes to india-bangalore region, creates these following errors. ee stack install Adding repository for MySQL, please wait... Adding repository for NGINX, please wait... Adding repository for PHP, please wait... Adding SWAP file, please wait... Oops Something went wrong!! Check logs for reason `tail /var/log/ee/ee.log` & Try Again!!! I checked the ee.log file, there i found nginx and mysql not installed, at the same time i installed everything on new-york region and i checked the ee.log file, everything installed successfully. I don't understand how it would be different like installing with a different region.
Hey, So I am having a lot of problems with nginx lately. As of nginx is not accepting my php file to put it on my sub domain. I have setup php-fpm etc. I need help with it and below is the config. Also the directory where the file is present root /var/www and server_info won't be shown as I don't wanna. I have also did the php-fpm for php7.1 as that was available. You can also see it on https://codepen.io/sharletsings123/pen/ZKdMXV ``` ## # You should look at the following URL's in order to grasp a solid understanding # of Nginx configuration files in order to fully unleash the power of Nginx. # http://wiki.nginx.org/Pitfalls # http://wiki.nginx.org/QuickStart # http://wiki.nginx.org/Configuration # # Generally, you will want to move this file somewhere, and start with a clean # file but keep this around for reference. Or just disable in sites-enabled. # # Please see /usr/share/doc/nginx-doc/examples/ for more detailed examples. ## # Default server configuration # server { listen 80; listen [::]:80; #SSL configuration # # listen 443 ssl default_server; # listen [::]:443 ssl default_server; # # Note: You should disable gzip for SSL traffic. # See: https://bugs.debian.org/773332 # # Read up on ssl_ciphers to ensure a secure configuration. # See: https://bugs.debian.org/765782 # # Self signed certs generated by the ssl-cert package # Don't use them in a production server! # # include snippets/snakeoil.conf; root /var/www/cantShowItsPrivate/html; # Add index.php to the list if you are using PHP index index.php index.html index.htm index.nginx-debian.html; server_name lol.com; location / { # First attempt to serve request as file, then # as directory, then fall back to displaying a 404. try_files $uri $uri/ =404; } # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000 # location ~ \.php$ { include snippets/fastcgi-php.conf # # With php7.1-cgi alone: # fastcgi_pass 127.0.0.1:9000; # # With php7.1-fpm: fastcgi_pass unix:/run/php/php7.1-fpm.sock; } # deny access to .htaccess files, if Apache's document root # concurs with nginx's one # location ~ /\.ht { deny all; } } # Virtual Host configuration for example.com # # You can move that to a different file under sites-available/ and symlink that # to sites-enabled/ to enable it. # #server { #. listen 80; # listen [::]:80; # # server_name example.com; # # root /var/www/example.com; # index index.html; # # location / { # try_files $uri $uri/ =404; # } #} ``` Thanks/ Kind regards, /shar.
In Ghost's preview the `inlinecode` looks fine but when I publish the blog post and load in Safari or Chrome, it shows up as plain text. Here's the post: https://linuxhowto.tech/managing-users-and-groups/ ## Adding new users While you can use `vipw` to edit the user configuration files, it is better to run `useradd`. `vim /etc/default/useradd` The output should look similar to this: ``` GROUP=100 HOME=/home INACTIVE=-1 EXPIRE= SHELL=/bin/bash SKEL=/etc/skel CREATE_MAIL_SPOOL=yes ``` ### Useradd examples * `useradd -c "Comment here" sarah -s /bin/bash` sets a comment (-c) and defines the default shell (-s) * `useradd bob -s /usr/sbin/nologin` sets `nologin` as the users's default shell because many users don't need shell access * `useradd -m -u 1201 -G ops,dev linda` adds user, adds home directory (-m), adds user to groups _ops_ and _dev_ (-G), assigns _UID 1201+ (-u) * `useradd` creates a locked account until you run `passwd user` ### The login configuration file The `/etc/login.defs` file sets the configuration for the for the _Shadow Password Suite._ The following are some of its most significant attributes: > * `MOTD_FILE`: Defines the file that is used as _message of the day_ file. In this file, you can include messages to be displayed after the user has successfully logged into the server. > * `ENV_PATH`: Defines the `$PATH` variable, a list of directories that should be searched for executable files after logging in. > * `PASS_MAX_DAYS`, `PASS_MIN_DAYS`, and `PASS_WARN_AGE`: Define the default password expiration properties when creating new users. > * `UID_MIN`: The first UID to use when creating new users. > * `CREATE_HOME`: Indicates whether or not to create a home directory for new users. > * `USERGROUPS_ENAB`: Set to yes to create a private group for all new users. That means that a new user has a group with the same name as the user as its default group. If set to no, all users are made a member of the group users. [^n] ### System-wide Bash shell startup files * `/etc/profile` runs system-wide environment variables and startup scripts * `/etc/bashrc` contains system-wide aliases and functions [^n] ### Bash shell personal startup files While creating a user, `useradd` copies the `/etc/skel` user environment configuration files to the new user's home directory. The following are the default configuration files: * `~/.bash_profile` contains personal environment variables and startup scripts * `~/.bashrc` contains personal aliases and functions * `~/.bash_logout` contains personal scripts to run on logout[^n] ## Using usermod to modify users These are a couple common use cases for `usermod`: * `usermod -g sales mike` adds _mike_ to sales as _primary_ group * `usermod -aG ops lisa` adds _lisa_ to ops as a *secondary* group ## Managing password properties Here are some example use cases for `passwd` and `chage`: * `chage -E 2018-12-31 bob` sets Bob's account to expire on a specific date * `chage -l linda` lists account aging information * `passwd -n 30 -x 90 lori -w 3` sets _minimum password age_ of 30 days, a _maximum password age_ of 90 days (-w), and starts _warning_ the user 3-days before the password expires (-w) ## Linux group management The `useradd` command creates a default _primary group_ with the same name as the user. When a user creates a file, the group owner will be set to that user's primary group. Users have access to files owned by their secondary groups. Use the `id` command to list a user's group memberships: `id linda` The output should look something like this: `uid=1002(linda) gid=1003(account) groups=1003(account),1001(sales)` A common use case for secondary groups is to share documents between departments with a file server. ## Creating groups To create a new group, you can use the `vigr` command to directly modify the `/etc/group` file or you can run the `groupadd` command. * `groupadd devs` adds a group called _dev_ * `groupadd -g 404 devproject` adds a group called _devproject_ with _Group ID (GUID) 404_ * `grep devproject /etc/group` to confirm that you successfully added a group ### Modifying group membership * `usermod -g 1003 frank` changes frank's **primary** group to account, assigning GUID of 1003 * `usermod -aG dev lori` adds account as a _secondary_ group for lori * `usermod -g sales anouk` changes anouk's _primary_ group to sales --------------------------------------- [^n]: Excerpt from Sander van Vugt's [Red Hat® RHCSA™/RHCE® 7 Cert Guide Premium Edition](http://www.sandervanvugt.com/book-red-hat-rhcsa-rhce-7-cert-guide/) [^n]: Derived from [Linux From Scratch](http://www.linuxfromscratch.org/blfs/view/5.1/postlfs/profile.html) [^n]: Derived from [Linux From Scratch](http://www.linuxfromscratch.org/blfs/view/5.1/postlfs/profile.html)
I run Nginx on my wordpress site, but now all pages and categories, except homepage, suddenly appear "404 not found, Nginx", the permalinks are correct and i don't do anything before such problem occur. How can i troubleshoot and fix this problem? Thank you!