1. I generated my ssh key on my local machine.

2. I then used the following command to copy my public key onto my server: ssh-copy-id username@remote_host. That went smoothly.

3. I have confirmed that my local machine's ~/.ssh/id_rsa.pub has been copied onto my server at my_user's_home_directory/.ssh/authorized_keys. There are no other files in there.

4. I've also copied that same public key into Gitlab.

5. When I try to git clone a repo onto the server, I'm told:

[email protected]: Permission denied (publickey,keyboard-interactive).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

6. I can ssh easily enough into my server. But since my server doesn't hold my private key, it sort of makes sense to me that I wouldn't be able to ssh git clone. What's the normal procedure here? I can do a regular https download, is that the standard route?

• Nextcloud is currently being served at my-domain.dev/nextcloud.
• I'd like to have it be served at cloud.my-domain.dev.
• I've already set up an A record for cloud.my-domain.dev to point to my servers' IP address.
• Sitting alongside my /var/www/nextcloud, I've also got a /var/www/my-domain.dev, my main site which I've set up to use HTTPS using Let's-Encrypt.
• I'm using Server version: Apache/2.4.41 (Ubuntu).

Now I need to set up the vhosts to play together. I'm assuming I'll have to convert the nextcloud.conf to sit within a virtual host, maybe under a different port? How do I proceed?

nextcloud.conf as recommended by nextcloud.

Alias /nextcloud "/var/www/nextcloud/"

<Directory /var/www/nextcloud/>
  Require all granted
  AllowOverride All
  Options FollowSymLinks MultiViews

  <IfModule mod_dav.c>
    Dav off
  </IfModule>    

  SetEnv HOME /var/www/nextcloud
  SetEnv HTTP_HOME /var/www/nextcloud

</Directory>

my-domain.dev.conf

<VirtualHost *:80>
    ServerAdmin webmaster@localhost
    ServerName my-domain.dev
    ServerAlias www.my-domain.dev
    DocumentRoot /var/www/my-domain.dev
    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined
</VirtualHost>

WHAT WORKED FOR ME:

Andrew Schulman's answer almost worked for me, I just had to make a few small changes:

• Remove "Require all granted".
• Move "AllowOverride All" and "Options FollowSymLinks MultiViews" into a directory tag.

Could someone explain why these steps were necessary?

Thanks Andrew!

nextcloud.conf:
  1 <VirtualHost *:80>
  2         ServerAdmin [email protected]
  3         ServerName cloud.b-t.dev
  4         DocumentRoot /var/www/nextcloud
  5
  6         #ErrorLog ${APACHE_LOG_DIR}/error.log
  7         #CustomLog ${APACHE_LOG_DIR}/access.log combined
  8
  9         <Directory "/var/www/nextcloud">
 10                 AllowOverride All
 11                 Options FollowSymLinks MultiViews
 12         </Directory>
 13
 14         #Satisfy Any
 15
 16         <IfModule mod_dav.c>
 17                 Dav off
 18         </IfModule>
 19
 20         SetEnv HOME /var/www/nextcloud
 21         SetEnv HTTP_HOME /var/www/nextcloud
 22 </VirtualHost>

I've tried this with both apache and nginx servers (separately, not at the same time). Both default servers have served content properly to the IP address but not to the domain name "b-t.dev". This applies both for the default "nginx/apache server is up and running" status page as well as for the PicoCMS installation I'm trying to debug here.

I've used other browsers and other devices so it's not a client caching issue.

This is my first time setting up these servers, so I'm probably missing something obvious.

Here are some status outputs:

pico.conf

/etc/nginx/sites-available/pico.conf (symlinked to sites-enabled/ of course):

server {
        listen 80;
        server_name 195.201.89.229 b-t.dev;
        root /var/www/html/pico;
        index index.php index.html index.htm;

        location / {
                try_files $uri $uri/ /index.php;
        }

        access_log /var/log/nginx/pico.access.log;
        error_log /var/log/nginx/pico.error.log;

        location ~ \.php$ {
                fastcgi_split_path_info ^(.+\.php)(/.+)$;
                fastcgi_pass unix:/var/run/php/php7.4-fpm.sock;
                fastcgi_index index.php;
                include fastcgi_params;
                fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
                fastcgi_buffer_size 16k;
                fastcgi_buffers 4 16k;
        }

}

Hetzner DNS administration

Hetzner has confirmed that my client is contacting the server, as this issue indicated might be a problem.

# ping b-t.dev
PING b-t.dev (195.201.89.229) 56(84) bytes of data.
64 bytes from static.229.89.201.195.clients.your-server.de (195.201.89.229): icmp_seq=1 ttl=58 time=0.503 ms

Firewall status: $ sudo ufw status Status: active

To                         Action      From
--                         ------      ----
OpenSSH                    ALLOW       Anywhere
mosh                       ALLOW       Anywhere
22/tcp                     ALLOW       Anywhere
80/tcp                     ALLOW       Anywhere
443/tcp                    ALLOW       Anywhere
Apache                     ALLOW       Anywhere
Nginx HTTP                 ALLOW       Anywhere
OpenSSH (v6)               ALLOW       Anywhere (v6)
mosh (v6)                  ALLOW       Anywhere (v6)
22/tcp (v6)                ALLOW       Anywhere (v6)
80/tcp (v6)                ALLOW       Anywhere (v6)
443/tcp (v6)               ALLOW       Anywhere (v6)
Apache (v6)                ALLOW       Anywhere (v6)
Nginx HTTP (v6)            ALLOW       Anywhere (v6)

systemctl status

$systemctl status nginx
● nginx.service - A high performance web server and a reverse proxy server
     Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2020-12-03 22:16:00 CST; 17h ago
       Docs: man:nginx(8)
    Process: 5060 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=0/SUCCESS)
    Process: 5069 ExecStart=/usr/sbin/nginx -g daemon on; master_process on; (code=exited, status=0/SUCCESS)
   Main PID: 5074 (nginx)
      Tasks: 2 (limit: 2286)
     Memory: 3.0M
     CGroup: /system.slice/nginx.service
             ├─5074 nginx: master process /usr/sbin/nginx -g daemon on; master_process on;
             └─5075 nginx: worker process

It seems like I could simply set up a redirect from the IP address to the domain name, but seems like a band-aid solution, no?

I've setup a clean new VPS running Ubuntu 20.04 LTS with Hetzner and would like to access it via ssh.

Here is what I've tried to do:

1. I have added my public ssh key (passphrase-less) in Hetzner's online GUI. That looked something like this:

ssh-rsa blahblahblah= [email protected]

2. But when I attempt to ssh-copy-id this key to the server, I run into issues. Since I haven't logged into the server to create users, I don't know what to put for the user in this command:

ssh-copy-id -i .ssh/id_rsa_pub [user]@serveraddress

I've tried adding the key to root user like so:

ssh-copy-id -i .ssh/id_rsa_pub [user]@serveraddress

But then I'm prompted for a password I don't know.

This leads me to the following questions I've had a hard time finding answers to:

1. How can I use ssh-copy-id to copy my public key to the server if I haven't setup a user yet?

2. What is the default root password on the server? How Would I find this out? I've tried ubuntu, root, the basics.

3. What does adding a public key via GUI on the server host's website normally do with regards to server users? Does it add the key to the known_hosts file?

4. What is the technical significance of the final comment line in my public ssh key, currently [email protected]?