NEMS Linux Community Forum

Hi everybody, In NConf i can see eight OS descriptions already created each with a gif image and a .gd2 file associated. By example the FreeBSD OS has got base/freebsd40.gif as icon and base/freebsd.gd2 as statusmap image. Question: Can i add new images to use when I create new OS descriptions? (i c...

Hi guys, ive done what you say, Nagios Core has reverted to normal, but then...
Any ideas?

Thank you.

Just to add a bit of clarity:

What i mean is: If i do a newer install burning a new image on SD and then use kuesco (without capitals) as username, the script runs fine.

Sorry if i generated some confussion.

Hi, this could not be a bug but an improvement. I was noticed that in NEMS 1.2.3 i was able to create a username with the first letter in capital (Kuesco). I backed up config and created a new SD with NEMS 1.3 just to do a fresh install and test after the SSL and Migrator bugs was resolved. This tim...

Hi, i think you´re right because chrome complaints about a non valid SSL response, and not about the validation of the cert. I´ve tried from a brand new installed windows with edge and IE and the result is the same.

Regards.

Hii, same trouble here. Running 1.3 trying to restore from 1.2.3.

Same exact error so this could not be an isolated case.

Regards.

Robbie, this is the output of my nems-info sslcert command (after run the quickfix script): kuesco@NEMS:~ $ nems-info sslcert Certificate:    Data:        Version: 1 (0x0)        Serial Number: 1 (0x1)    Signature Algorithm: sha256WithRSAEncryption        Issuer: C = CA, ST = Ontario, L = Toronto, ...

Hi Robbie, i have run the command, used generic settings when asked on the NEMS quickfix part and the script autogenerated a new cert (Ontario, Canada), but i still get the same SSL error. Only thing to note during the nems-update partt was one repository marked as unavailable (the last one). As far...