Error loading settings file: .node-red/settings.js after server restart

Hi all
Recently started working with Node-Red for a project I've got; and so far I like it a lot.
I am going to connect it to Ubidots, to use their functionality as they seem to have what I need.
Anyway; I am getting this error everytime I restart the server (ubuntu 18.04) or have kept the server turned off (in cloud) when not developing on it.

I have forced HTTPS, installed a cert (in nodecerts subfolder), and made the setup with user authentication.

The error log I get:
Error loading settings file: /home/noby/.node-red/settings.js
{ Error: ENOENT: no such file or directory, open 'nodecerts/node-key.pem'
at Object.openSync (fs.js:443:3)
at Object.readFileSync (fs.js:343:35)
at Object. (/home/noby/.node-red/settings.js:151:14)
at Module._compile (internal/modules/cjs/loader.js:776:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)
at Module.require (internal/modules/cjs/loader.js:690:17)
at require (internal/modules/cjs/helpers.js:25:18)
errno: -2,
syscall: 'open',
code: 'ENOENT',
path: 'nodecerts/node-key.pem' }

I am solving the issue simply by opening settings.js, delete one letter of the nodecerts/node-key.pem path and typing it in again; and finish with esc+wq!.
Restart the server and its running like nothing ever happened.
Anyway it is pretty anoying that I have to do this everytime the server restarts.
Does anyone know of a better solution to the issue?

Best Regards

So that file doesn't exist, as the error says. I suspect that it isn't in the relative path that you think it is.

Try using an absolute path.

Thanks - The thing is that the path/file does exist.
After using absolute path in the settings.js file I no longer experience this error.
Issue solved - thank you TotallyInformation.