Connection error

[toonnoot]

attached the log

qb-100000021600-0000Q00000:~# ls -las /etc/openvpn/
1 drwxr-xr-x 3 root root 1024 Dec 4 2017 .
2 drwxr-xr-x 31 root root 2048 Oct 3 23:24 ..
1 drwxr-xr-x 2 root root 1024 Dec 4 2017 certs
0 lrwxrwxrwx 1 root root 33 Dec 4 2017 vpn.conf -> /mnt/persist/etc/openvpn/vpn.conf
0 lrwxrwxrwx 1 root root 42 Dec 4 2017 vpn_port.conf -> /mnt/data/system/etc/openvpn/vpn_port.conf
qb-100000021600-0000Q00000:~# ls -las /etc/openvpn/certs/
1 drwxr-xr-x 2 root root 1024 Dec 4 2017 .
1 drwxr-xr-x 3 root root 1024 Dec 4 2017 ..
0 lrwxrwxrwx 1 root root 19 Dec 4 2017 device.crt -> /mnt/mfr/device.crt
0 lrwxrwxrwx 1 root root 19 Dec 4 2017 device.key -> /mnt/mfr/device.key
0 lrwxrwxrwx 1 root root 51 Dec 4 2017 server-ca-bundle.crt -> /mnt/persist/etc/openvpn/certs/server-ca-bundle.crt
0 lrwxrwxrwx 1 root root 41 Dec 4 2017 ta-ene.key -> /mnt/persist/etc/openvpn/certs/ta-ene.key
0 lrwxrwxrwx 1 root root 37 Dec 4 2017 ta.key -> /mnt/persist/etc/openvpn/certs/ta.key

[TheHogNL]

Please also do: ls -las /mnt/mfr/

[toonnoot]

/root$ ls -las /mnt/mfr/
16 drwxr-xr-x 2 root root 16384 Jan 1 1970 .
1 drwxr-xr-x 8 root root 1024 Dec 4 2017 ..
2 -rwxr-xr-x 1 root root 27 Jan 1 2000 hostname
2 -rwxr-xr-x 1 root root 136 Jan 1 2000 mfr.scr
2 -rwxr-xr-x 1 root root 64 Jan 1 2000 mfr.txt

[TheHogNL]

No device.crt and key indeed

For the update using my server I noticed that I had some bad files stored (file corruption). Fixing it right now

[toonnoot]

No device.crt and key indeed

For the update using my server I noticed that I had some bad files stored (file corruption). Fixing it right now

super weird though.. how can the keys have magically disappeared?
it's also a toon2 so no way that anyone could have done a recovery right?

let me know when your server is updated, i'll try to update through there.
thanks again for your help hog!

[TheHogNL]

The /mnt/mfr is a read only file system (normally) and will be kept after recovery.
So no way to recover the keys I am afraid.
But after the update the toon is ok to use. Only no updates later.

Server is ready.

[toonnoot]

The /mnt/mfr is a read only file system (normally) and will be kept after recovery.
So no way to recover the keys I am afraid.
But after the update the toon is ok to use. Only no updates later.

Server is ready.

I meant the ToonRecovery app.

Could it be something went wrong from Eneco’s side when they tried to update the vpn keys of this toon?
It does seem to be a prerelease batch considering the qb1xxx numbering and the different recovery menu, so maybe the things eneco did to fix it messed this toon up?

[toonnoot]

still getting an error when updating:
Skip starting VPN
Forcing source: http://qutility.nl/feeds
You are currently running version 4.9.124 on a nxt with flavour ene

Available versions: 1.9.10 2.1.0 2.2.24 2.3.17 2.3.29 2.3.36 2.4.7 2.4.12 2.5.11 2.5.14 2.5.18 2.6.24 2.6.33 2.8.16 2.8.21 2.8.27 2.9.15 2.9.26 2.10.15 3.0.29 3.0.32 3.1.22 3.2.14 3.2.18 3.2.21 3.3.8 3.4.2 3.4.4 3.5.4 3.6.3 3.7.8 3.7.9 4.3.20 4.4.21 4.7.23 4.8.25 4.9.23 4.9.124 4.10.6 4.10.9 4.11.6 4.12.0 4.13.6 4.13.7 4.15.2 4.15.6 4.16.8 4.17.11 4.18.8 4.19.10 4.20.7 4.22.7 5.0.4 5.0.5 5.0.6 5.2.11 5.5.7 5.9.6 5.13.9 5.13.12 5.15.6 5.18.8 5.22.14 5.25.8 5.28.6 5.28.9 5.30.4 5.33.9 5.39.7 5.41.1 5.43.2 5.46.4 5.49.4 5.49.7 5.49.16 5.49.19

Which version do you want to upgrade to?
5.49.19
Alright, I will try to upgrade to 5.49.19
Upgrade script downloaded. We need to download the upgrade files first. No upgrade is done yet. Do you want me to download the files (yes) or quit (anything else)?
yes
Starting the upgrade prepare option which downloads all necessary files. No upgrade is done yet.
Waiting to finish. Sometimes this takes a minute or two ..
Prepare failed. Please check the logs at /mnt/data/update/upgrade-nxt.sh.log
Quitting the upgrade. It was a nice try tho...
killall: openvpn: no process killed

[TheHogNL]

can you send the log again?

[TheHogNL]

The /mnt/mfr is a read only file system (normally) and will be kept after recovery.
So no way to recover the keys I am afraid.
But after the update the toon is ok to use. Only no updates later.

Server is ready.

I meant the ToonRecovery app.

Could it be something went wrong from Eneco’s side when they tried to update the vpn keys of this toon?
It does seem to be a prerelease batch considering the qb1xxx numbering and the different recovery menu, so maybe the things eneco did to fix it messed this toon up?

Toonrecovery works only voor toon1.

I believe the prelease batch doesn't contain vpn keys. Only for the old systems maybe but they are not there now anymore.

[toonnoot]

see attached for log

[toonnoot]

btw when I incrementally update in smaller steps it does work up to a certain point.
Currently at 4.22.7->5.5.7

[TheHogNL]

I notice some more file corruption.. need to check them all now

[TheHogNL]

Can you try again?

[toonnoot]

seems to be working now!
thanks hog

it seems like it may also have fixed the vpn issue?
the toon says connected to Service Center, however the update script fails to connect again (-o option)