Not sure if it is just the filepath. I am running an Asus RT-AX88U on Firmware Version: 3.0.0.4.386_49674 and get similar error when running the scp command manually from another machine. When trying to use scp from while ssh’d to the router the command is not found. My suspicion Asus original firmware does not include scp command.
P.S: I couldn’t get the add-on running after cloning your git to the add-on folder. From Supervisor log: 22-08-25 20:45:13 WARNING (SyncWorker_3) [supervisor.store.data] No repository information exists at /data/addons/git/home-assistant-ssl-from-asus-router
Not sure if this is your repo or I cloned it wrong…
I have one suggestion, if I may: some people, like me, might want to keep their original Asus firmware for one reason or another. From what I understand, you get the certificates via SCP, which is not present in the asus fw. There seem to be ways to install scp by adding a usb storage device and a package manager on it, but this seems a bit of an overkill.
Hi,
I need som help. I get this error and I’m stuck.
I only have a file called authorized_keys in my /root/.ssh directory.
s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] 00-banner.sh: executing…
Add-on: Refresh SSL Cert From Stock Asus DDNS Router
An Add-on that help refresh the SSL certificate under the /SSL folder from Stock Asus Router DDNS
Add-on version: 0.1.0
You are running the latest version of this add-on.
System: Home Assistant OS 9.3 (amd64 / qemux86-64)
Home Assistant Core: 2022.11.2
Home Assistant Supervisor: 2022.10.2
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
I thought I worked it out but get the following error when I start the add-on. Any suggestions?
[s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] 00-banner.sh: executing…
Add-on: Refresh SSL Cert From Stock Asus DDNS Router
An Add-on that help refresh the SSL certificate under the /SSL folder from Stock Asus Router DDNS
Add-on version: 0.1.0
You are running the latest version of this add-on.
System: Home Assistant OS 9.4 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2023.1.7
Home Assistant Supervisor: 2023.01.1
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
Excellent add-on If I could get it to work on my HA… I have Stock Asus and installed the SSH-fork of this addon. Here are my log, says nothing to me… any hints welcome
[s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] 00-banner.sh: executing…
Add-on: Refresh SSL Cert From Stock Asus DDNS Router
An Add-on that help refresh the SSL certificate under the /SSL folder from Stock Asus Router DDNS
Add-on version: 0.1.0
You are running the latest version of this add-on.
System: Home Assistant OS 9.5 (amd64 / generic-x86-64)
Home Assistant Core: 2023.1.7
Home Assistant Supervisor: 2023.01.1
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
My log is about the same, except for the line after the “Not known Host, adding…”:
Not known Host, adding...
[192.168.50.1]:5555 ssh-rsa
I don’t see my hostname at all in the log, are you trying to connect to the router through WAN or LAN? And if WAN, do you have WAN SSH enabled? What port are you using and are you sure your ISP doesn’t block it?
I have it configured the following way, with an access from LAN:
In my router settings I changed the default 22 port to 5555, as Asus recommends that for the security reasons.
Also, what’s in the SSL folder? I have my files there, but if you’re rookie like me, make sure you disabled the “enforce basepath” option in the File Editor configuration and are not trying to find the files in /config/SSL
It seems like the problem is the router’s private key not being in the right format.
Have you successfully SSH’d into your router with that key from another computer?
Try creating a new private key.
I used to run home Assistant on my ASUSTOR NAS, but since it uses quite a lot of power (50W with spinning disks isn’t abnormal), I’ve now set it up on a mini PC which uses only 5W. Downside is I now have to set up the certs myself and it’s driving me nuts… I keep getting a connection refused error:
-Create a SSH key using Putty (default settings)
-Pasted the public key in the authorized keys section of the router
-Saved the private.ppk file on the HA machine under config/rsa/private.ppk
put the following configuration in:
routerUser: username
routerIp: 192.168.0.2
routerSshPort: 22517
rsaPrivateKeyPath: rsa/private
keyFilePathOnRouter: /tmp/etc/key.pem
certFilePathOnRouter: /tmp/etc/cert.pem
(paths adopted as suggested above)
and I keep getting the “write (192.168.0.2): Connection refused” error. it’s driving me nuts
Tried using putty to log in with the keys and same IP and port and all is well…
Add-on version: 0.1.0
You are running the latest version of this add-on.
System: Home Assistant OS 10.3 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2023.7.3
Home Assistant Supervisor: 2023.07.1
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
What type of key files are you using? I previously had used this version with a PuttyGen generated key file, that gave me the same error as you have. Then I tried the fork mentioned above, which failed in a different way. Then I created a new keyfile using SSH-keygen and tried that with the fork, and now all is well!
Uhm, sorry to tell you, but I’m afraid that you’ll then first have to read up on creating the private and public keys for your router. It’s what this addon uses to log into your router instead of a username/password. So you first have to create the keys, enter the key in the authorized_key field of the router to tell the router what credentials you’ll be using to log in and that it can trust those. Then you have to put the keys on your HA install and tell it to use those keys to log in to the router. That’s the whole thing behind the addon…
