Looks like you are working with Windows. Honestly do not think any developer at n8n is working with it at n8n. So is sadly quite possible that something is not working perfectly there right now.
Thanks a lot. That is a very important datapoint. Think nobody is using CentOS either but would not have expected that issues arise there. We will have a look.
fyi just to be sure that nothing major is currently wrong did I check out n8n (master branch) totally new inside of my Ubuntu-Dev-Image. Did then run the 3 commands you mentioned above and everything worked perfectly. So at least nothing major obvious wrong, which really would have been embarrassing.
It could be something specific to Cent, could you try disabling selinux and seeing if that works? If that allows it to start it a policy will need to be created.