How To Install Full GNOME desktop in Ubuntu 16.04 (DigitalOcean)

November 14, 2018 1.2k

Applications DigitalOcean

By:

ChristineB

Please Help me to install Full Gnome Desktop in My server with commands.

Log In to Comment

Be the first one to answer this question.

Related

question

Is DO a good hosting solution for a CRM like SugarCRM

We are looking for a reliable Linux solution for a couple business apps, SugarCRM, and Jira Core. We would also likely have a couple modestly trafficked web sites. Could we do this all cost-effectively on Digital Ocean?
question

URL masking or Hiding domain name

Hi Guys, I created a website previously and all my clients know my domain name, but recently we partnered up with a company and they created a website for us and some other thing that we needed, they said we can go ahead and musk their URL to our domain but this is where I'm having problem. my domain is (mycompanyname.com) partners created website url is (mycompanyname.partnername.com) so what I want is if I can mask the entire website with (mycompanyname.com), instead of the (mycompanyname.partnername.com). I have managed to redirect it when someone enters mycompanyname.com it gets directed to (mycompanyname.partnername.com), but on the address bar the (mycompanyname.partnername.com) stays on there I want that to be masked with my (mycompanyname.com). Can someone help me please.
question

Permission denied (publickey) for root login

It was working before but now somehow its not working. ssh root@111.11.11.111 gives below error message Permission denied (publickey). While for other user its working ( i.e ssh myUser@111.11.11.111 ) I had tried many tutorials on digital oceans and from stackoverflow, but none working and I can't login with root. Anybody has resolution? Thanks.
question

Best way to configure Nginx SSL + force HTTP to redirect to HTTPS + force www to non-www on Serverpilot free plan (by using Nginx configuration file only)

I have set up a Wordpress website running on my Serverpilot/Digital Ocean droplet. I have succesfully managed to: * Manually Install a PositiveSSL certificate (from Namecheap) * Change the APPNAME.conf file to force HTTP to redirect to HTTPS and to force www to non-www So everything works fine but I'm not sure if I have configured the Serverpilot Nginx configuration file correctly. My questions are: **What I did:** I have implemented the 301 redirects rules in Serverpilots Nginx configuration file (APPNAME.conf) so the redirects are handled in the most efficient way possible by the server.** **My question:** is this indeed the best/fastest way? **What I did:** The config files should be protected from serverpilot updates, so when serverpilot updates it's system, no files get overwritten, no errors will take place. I followed this [Serverpilot Article](https://serverpilot.io/community/articles/customize-nginx-settings.html) **My question:** Is my configuration protected from being overwritten by serverpilot? **What I did:** Reduce the amount of redirects. All requests (http//example.com, http://www.example.com, https://www.example.com) should be redirected to https://example.com in max. one redirect step. I have tested my website in [HTTP Status Code Checker](https://httpstatus.io/). All redirects are done in max. one step. **My question:** When I test for instance Google.nl in this tool I see that the redirect from http://google.nl to https://www.google.nl is performed in two steps. Why is that? Should I also perform a redirect from http://www.example.com to https://example.com in two 301 redirects? # My Serverpilot Nginx configuration ### Step 1: Installing SSL certificat I have installed the PositiveSSL certificate on the server following step 1 - 4 of this tutorial: https://www.blogmehow.com/how-to-manually-install-ssl-on-serverpilot-free-plan-1331/ ### Step 2: Create 3 serverblocks in the APPNAME.custom.conf file I have renamed the APPNAME.conf file to APPNAME.custom.conf file in this /etc/nginx-sp/vhosts.d opened it and changed it so it has three serverblocks. One to redirect http to https, one to redirect the https www-name to no-www, and one to actually handle the requests.: ``` server { listen 80; listen [::]:80; server_name example.com www.example.com; return 301 https://example.com$request_uri; } server { listen 443 ssl; listen [::]:443 ssl; server_name www.example.com; ssl on; ssl_certificate /root/certs/APPNAME/APPNAME_nl.chained.crt; ssl_certificate_key /root/certs/APPNAME/ssl.key; ssl_session_timeout 1d; ssl_session_cache shared:SSL:20m; ssl_session_tickets off; ssl_protocols TLSv1 TLSv1.1 TLSv1.2; ssl_prefer_server_ciphers on; ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!3DES:!MD5:!PSK'; ssl_stapling on; ssl_stapling_verify on; ssl_trusted_certificate /root/certs/APPNAME/APPNAME_nl.chained.crt; root /srv/users/serverpilot/apps/APPNAME/public; access_log /srv/users/serverpilot/log/APPNAME/APPNAME_nginx.access.log main; error_log /srv/users/serverpilot/log/APPNAME/APPNAME_nginx.error.log; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-SSL on; proxy_set_header X-Forwarded-Proto $scheme; include /etc/nginx-sp/vhosts.d/APPNAMEd/*.nonssl_conf; include /etc/nginx-sp/vhosts.d/APPNAME.d/*.conf; return 301 https://example.com$request_uri; } server { listen 443 ssl; listen [::]:443 ssl; server_name example.com; ssl on; ssl_certificate /root/certs/APPNAME/APPNAME_nl.chained.crt; ssl_certificate_key /root/certs/APPNAME/ssl.key; ssl_session_timeout 1d; ssl_session_cache shared:SSL:20m; ssl_session_tickets off; ssl_protocols TLSv1 TLSv1.1 TLSv1.2; ssl_prefer_server_ciphers on; ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!3DES:!MD5:!PSK'; ssl_stapling on; ssl_stapling_verify on; ssl_trusted_certificate /root/certs/APPNAME/APPNAME_nl.chained.crt; root /srv/users/serverpilot/apps/APPNAME/public; access_log /srv/users/serverpilot/log/APPNAME/APPNAME_nginx.access.log main; error_log /srv/users/serverpilot/log/APPNAME/APPNAME_nginx.error.log; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-SSL on; proxy_set_header X-Forwarded-Proto $scheme; include /etc/nginx-sp/vhosts.d/APPNAME.d/*.nonssl_conf; include /etc/nginx-sp/vhosts.d/APPNAME.d/*.conf; } ``` I hope someone can take the time to have a look at my configuration and let me know how I can optimize my setup even more taking into account my goals. Kind regards, Jan ** According to what I have found in [This article]( http://serverfault.com/a/258424/377649), this is the most efficient and fastest way to do a 301 redirect: The best way to accomplish this is using three server blocks: one to redirect http to https, one to redirect the https www-name to no-www, and one to actually handle requests. The reason for using extra server blocks instead of ifs is that server selection is performed using a hash table, and is very fast. Using a server-level if means the if is run for every request, which is wasteful. Also, capturing the requested uri in the rewrite is wasteful, as nginx already has this information in the $uri and $request_uri variables (without and with query string, respectively).