Jump to content

aian

Validating
  • Posts

    2
  • Joined

  • Last visited

  1. Hi all, I am trying to add SSH Keys to an HC1. The commands I am using are: sudo mkdir ~/.ssh sudo chmod 700 ~/.ssh sudo nano ~/.ssh/authorized_keys Then I select all the PUBLIC key from PuTTy Gen and copy/paste it on the file above, close and save the file. sudo chmod 600 ~/.ssh/authorized_keys sudo chown -R $(whoami):$(whoami) ~/.ssh/ sudo reboot I then try to SSH with PuTTy and SSH keys. Immediately I get an error saying "Server refused our key" and then it asks me for my normal password as a user. Any idea what I am doing wrong?
  2. Hi all, I have a Rpi 3B+ where I am running Pihole with Unbound. As a secondary DNS, I am planning to use an Odroid HC1 which will also be running other stuff. Today I installed Armbian_20.05.7_Odroidxu4_buster_current_5.4.50_minimal.img and started the installation of Pihole, which went through just fine. Then I attempted to install Unbound, but got an error message. The command I run was: sudo apt install unbound -y And this is what was returned: Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libevent-2.1-6 libpython3.7 libunbound8 unbound-anchor Suggested packages: apparmor The following NEW packages will be installed: libevent-2.1-6 libpython3.7 libunbound8 unbound unbound-anchor 0 upgraded, 5 newly installed, 0 to remove and 0 not upgraded. Need to get 2,682 kB of archives. After this operation, 7,786 kB of additional disk space will be used. Get:1 http://security.debian.org buster/updates/main armhf libunbound8 armhf 1.9.0-2+deb10u2 [411 kB] Get:2 http://deb.debian.org/debian buster/main armhf libevent-2.1-6 armhf 2.1.8-stable-4 [159 kB] Get:3 http://deb.debian.org/debian buster/main armhf libpython3.7 armhf 3.7.3-2+deb10u1 [1,282 kB] Get:4 http://security.debian.org buster/updates/main armhf unbound-anchor armhf 1.9.0-2+deb10u2 [145 kB] Get:5 http://security.debian.org buster/updates/main armhf unbound armhf 1.9.0-2+deb10u2 [686 kB] Fetched 2,682 kB in 1s (4,479 kB/s) Selecting previously unselected package libevent-2.1-6:armhf. (Reading database ... 27770 files and directories currently installed.) Preparing to unpack .../libevent-2.1-6_2.1.8-stable-4_armhf.deb ... Unpacking libevent-2.1-6:armhf (2.1.8-stable-4) ... Selecting previously unselected package libpython3.7:armhf. Preparing to unpack .../libpython3.7_3.7.3-2+deb10u1_armhf.deb ... Unpacking libpython3.7:armhf (3.7.3-2+deb10u1) ... Selecting previously unselected package libunbound8:armhf. Preparing to unpack .../libunbound8_1.9.0-2+deb10u2_armhf.deb ... Unpacking libunbound8:armhf (1.9.0-2+deb10u2) ... Selecting previously unselected package unbound-anchor. Preparing to unpack .../unbound-anchor_1.9.0-2+deb10u2_armhf.deb ... Unpacking unbound-anchor (1.9.0-2+deb10u2) ... Selecting previously unselected package unbound. Preparing to unpack .../unbound_1.9.0-2+deb10u2_armhf.deb ... Unpacking unbound (1.9.0-2+deb10u2) ... Setting up libpython3.7:armhf (3.7.3-2+deb10u1) ... Setting up libevent-2.1-6:armhf (2.1.8-stable-4) ... Setting up libunbound8:armhf (1.9.0-2+deb10u2) ... Setting up unbound-anchor (1.9.0-2+deb10u2) ... Setting up unbound (1.9.0-2+deb10u2) ... Created symlink /etc/systemd/system/multi-user.target.wants/unbound.service → /lib/systemd/system/unbound.service. Created symlink /etc/systemd/system/unbound.service.wants/unbound-resolvconf.service → /lib/systemd/system/unbound-resolvconf.service. Job for unbound.service failed because the control process exited with error code. See "systemctl status unbound.service" and "journalctl -xe" for details. Job for unbound.service failed because the control process exited with error code. See "systemctl status unbound.service" and "journalctl -xe" for details. invoke-rc.d: initscript unbound, action "start" failed. ● unbound.service - Unbound DNS server Loaded: loaded (/lib/systemd/system/unbound.service; enabled; vendor preset: enabled) Active: activating (auto-restart) (Result: exit-code) since Sat 2020-07-18 17:29:48 BST; 24ms ago Docs: man:unbound(8) Process: 2692 ExecStartPre=/usr/lib/unbound/package-helper chroot_setup (code=exited, status=0/SUCCESS) Process: 2697 ExecStartPre=/usr/lib/unbound/package-helper root_trust_anchor_update (code=exited, status=0/SUCCESS) Process: 2701 ExecStart=/usr/sbin/unbound -d $DAEMON_OPTS (code=exited, status=1/FAILURE) Main PID: 2701 (code=exited, status=1/FAILURE) Processing triggers for systemd (241-7~deb10u4) ... Processing triggers for libc-bin (2.28-10) ... 4th line from the bottom, the error (code=exited, status=1/FAILURE) appeared. Any idea what I did wrong and how to solve this? Thanks in advance.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines