Downloading certificate - invalid tar?

[nephilim]

Hi,

I am running an AC86 as main router of an AiMesh setup. The fw is 384.18 on all devices. I activated http and https access and downloaded the router's certificate from System -> Service. The file is called cert.tar but trying to expand it fails:

$ tar xvf cert.tar
x cert.crt: Truncated tar archive

Is that the expected behavior?

Thanks
Torsten

 

[RMerlin]

Works for me.

merlin@ubuntu-dev:/media/sf_Share$ tar -xvf cert_key.tar 
cert.pem
key.pem
merlin@ubuntu-dev:/media/sf_Share$

 

[nephilim]

Hmm, now I'm puzzled. This is where I download the certificate. The file I am getting is called cert.tar. Yours is called cert_key.tar.

 

[nephilim]

OK, it's getting weird. I noticed that uidivstats page was blank and that the logfiles had not been updated for almost a day. I rebooted and now the tar can be successfully extracted (just a cert.crt file but intact).

 

[debt]

Works for me.

merlin@ubuntu-dev:/media/sf_Share$ tar -xvf cert_key.tar
cert.pem
key.pem
merlin@ubuntu-dev:/media/sf_Share$

I am having the same issue. File will not extract. I am not over-the-top technical so just downloaded and double clicked to extract. Just gave me the .tar file again; not .cert. Rebooted my router twice and still would not extract the file. I will wait a day to see if something changes. I am following the steps with the Asus support page using the first option. I really do not want to do the second one as it seems much more complicated. Any new suggestions since this post? Thanks. PS I love the firmware.

 

[tomr]

Hi,

I am running an AC86 as main router of an AiMesh setup. The fw is 384.18 on all devices. I activated http and https access and downloaded the router's certificate from System -> Service. The file is called cert.tar but trying to expand it fails:

$ tar xvf cert.tar
x cert.crt: Truncated tar archive

Is that the expected behavior?

Thanks
Torsten

Not sure what you mean by fails, but in my case cert.tar is an empty archive. I expected it to contain a certificate. I think that's a bug. I'm using the asus DDNS service and I uploaded a custom certificate. I'm not sure, but that might be what is causing the issue. When I try to connect to the router's web interface using https and port 8443, I see that it's using the DDNS certificate that I uploaded.