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?
What is the best and the safest way to allow other developers to access my droplet?
I have created my droplet using SSH key (public and private) for linux environment. However, the other developers require to access the droplet via FTP (putty with .ppk).
What would be the best solution to grant others to access my droplet?
FTP is inherently insecure, so I would recommend setting up SFTP instead. It doesn’t require that you setup another piece of software and allows you to connect to SFTP using SSH.
The developers can use public/private key pairing as long as you set it up for them. They’d provide you with the public key, which would be placed in the users authorized_keys file.
My droplet is running Ubuntu 14.04.4 LTS. I tried running the following command: ``` sudo apt-get update ``` but got errors like: ``` Temporary failure resolving 'mirrors.digitalocean.com' ``` Pinging 8.8.8.8 works. Pinging google.com results in: ``` ping: unknown host google.com ``` I found other people with a similar problem, but none of the solutions in the other threads worked, such as forcing IPv4 by uncommenting ```precedence ::ffff:0:0/96 100``` in /etc/gai.conf. Disabling IPv6 with /etc/sysctl.conf did not fix the DNS problems either. Is there something else that could be wrong? I tried the above commands with and without ufw enabled.
On my droplet I have installed and configured a django website successfully. My client asked me to re-do the project (it was a very old project). So I created another django website on this droplet for testing purposes (for my client to see the new version of the old site before deleting the old one and the new one going live) and added a new domain entry (i.e. stage.example.com) pointing to this droplet. I edited gunicorn.service file and added this section: [Service] User=myuser Group=www-data WorkingDirectory=/home/myuser/project2 ExecStart=/home/myuser/.virtualenvs/project2env/bin/gunicorn --workers 3 --bind unix:/home/myuser/project2/project2.sock project2.wsgi:application **Question 1: Is this allowed? To add two [Service] sections in gunicorn.service file?** Anyway, I tried to reload gunicorn and got this error message: ``` Failed to restart gunicorn.service: Unit gunicorn.service is not loaded properly: Invalid argument. See system logs and 'systemctl status gunicorn.service' for details. ``` I opened /var/log/syslog and I noticed this: ``` Jun 9 08:57:59 project1-fra1 systemd[1]: Reloading. Jun 9 08:58:00 project1-fra1 systemd[1]: gunicorn.service: Service has more than one ExecStart= setting, which is only allowed for Type=oneshot services. Refusing. Jun 9 08:58:00 project1-fra1 systemd[1]: apt-daily.timer: Adding 11h 23.852822s random time. Jun 9 08:58:00 project1-fra1 systemd[1]: snapd.refresh.timer: Adding 4h 8min 5.201022s random time. Jun 9 08:58:00 project1-fra1 systemd[1]: Started ACPI event daemon. Jun 9 09:00:22 project1-fra1 systemd[1]: Stopping A high performance web server and a reverse proxy server... Jun 9 09:00:22 project1-fra1 systemd[1]: Stopped A high performance web server and a reverse proxy server. Jun 9 09:00:22 project1-fra1 systemd[1]: Starting A high performance web server and a reverse proxy server... Jun 9 09:00:22 project1-fra1 systemd[1]: nginx.service: Failed to read PID from file /run/nginx.pid: Invalid argument Jun 9 09:00:22 project1-fra1 systemd[1]: Started A high performance web server and a reverse proxy server. ``` I removed the second section from gunicorn.service file and tried to reload the gunicorn service, but although the site is working as normal, I still receive the same "Invalid Argument" error message. **Question 2: What did I do wrong? Is this fixable? How?**
Hey All, I changed to DO but since our domain already has a DNS server I don't think I need to use DO's DNS. However locally it doesn't work, and I would ask you expert whats going wrong. Seems : juridischforum.be works, but www.juridischforum.be is giving ERR_NAME_NOT_RESOLVED ``` [root@juridischforum ~]# dig juridischforum.be NS ; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.30.rc1.el6_6.3 <<>> juridischforum.be NS ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38003 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;juridischforum.be. IN NS ;; ANSWER SECTION: juridischforum.be. 5819 IN NS ns1.dot-01.nl. juridischforum.be. 5819 IN NS ns2.dot-01.nl. ;; Query time: 6 msec ;; SERVER: 8.8.4.4#53(8.8.4.4) ;; WHEN: Sat Jun 20 20:05:59 2015 ;; MSG SIZE rcvd: 80 [root@juridischforum ~]# dig juridischforum.be A ; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.30.rc1.el6_6.3 <<>> juridischforum.be A ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 46941 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;juridischforum.be. IN A ;; ANSWER SECTION: juridischforum.be. 3654 IN A 128.199.41.151 ;; Query time: 5 msec ;; SERVER: 8.8.4.4#53(8.8.4.4) ;; WHEN: Sat Jun 20 20:06:08 2015 ;; MSG SIZE rcvd: 51 [root@juridischforum ~]# dig www.juridischforum.be A ; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.30.rc1.el6_6.3 <<>> www.juridischforum.be A ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16230 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.juridischforum.be. IN A ;; ANSWER SECTION: www.juridischforum.be. 10229 IN A 128.199.41.151 ;; Query time: 6 msec ;; SERVER: 8.8.4.4#53(8.8.4.4) ;; WHEN: Sat Jun 20 20:06:14 2015 ;; MSG SIZE rcvd: 55 ``` What I setup is : ``` ftp A 178.18.91.128 juridischforum.be. A 128.199.41.151 localhost A 127.0.0.1 mail A 178.18.91.128 pop A 178.18.91.128 smtp A 178.18.91.128 www A 128.199.41.151 juridischforum.be. NS ns1.dot-01.nl. juridischforum.be. NS ns2.dot-01.nl. juridischforum.be. MX 10 mail juridischforum.be. TXT "v=spf1 a mx ip4:178.18.91.128 ~all" ``` I only changed www (A) & juridischforum.be. (A). Any tips ?
I getting problem with Ubuntu repository on Ubuntu 16.04 and 18.04 droplets created in London. For droplets created in Frankfurt everything works out of box. Does anyone experiencing this too? ``` # apt-get update Ign:4 http://security.debian.org bionic/updates InRelease Ign:1 http://lon1.mirrors.digitalocean.com/debian bionic InRelease Err:6 http://security.debian.org bionic/updates Release 404 Not Found [IP: 151.101.60.204 80] Ign:2 http://lon1.mirrors.digitalocean.com/debian bionic-updates InRelease Ign:3 http://lon1.mirrors.digitalocean.com/debian bionic-backports InRelease Err:5 http://lon1.mirrors.digitalocean.com/debian bionic Release 404 Not Found [IP: 5.101.111.50 80] Err:7 http://lon1.mirrors.digitalocean.com/debian bionic-updates Release 404 Not Found [IP: 5.101.111.50 80] Err:8 http://lon1.mirrors.digitalocean.com/debian bionic-backports Release 404 Not Found [IP: 5.101.111.50 80] Hit:9 https://repos.sonar.digitalocean.com/apt main InRelease Reading package lists... Done E: The repository 'http://security.debian.org bionic/updates Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'http://mirrors.digitalocean.com/debian bionic Release' no longer has a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'http://mirrors.digitalocean.com/debian bionic-updates Release' no longer has a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. E: The repository 'http://mirrors.digitalocean.com/debian bionic-backports Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. ```