I installed n8n on my NAS with TrueNas Core OS and it works.
My problem: I can’t access OAuth2 which is mandatory for some Google services because I still have the localhost link.
I have an SSL domain name that points to the page of my internet box or to n8n using the dedicated port.
The console specific to the n8n plugin on my NAS is, it seems to me, in SSH, but they offer other services to activate (see photo1)
I did all the configuration steps: Node, npm, n8n, pm2, etc. and set up environment variables with “vi”, because “export” doesn’t work.
I couldn’t do the Nginx and SSL steps because with or without sudo it doesn’t work.
I have a post-installation note (photo2).
It says the config file is somewhere, but I never managed to find it.
Instead of running ‘pm2 restart ecosystem.config.js’ I ran ‘pm2_n8n restart ecosystem.config.js’ as written on the post install note.
And my domain name finally appears in the OAuth2 link.
I have reported this link in the URL field of the Google OAuth2 client ID and correctly entered the client id and the client secret on n8n, and yet, I read in the window that opens that the site is inaccessible .
N8n is accessible from “www.mydomain.fr:5678”; without the port, it redirects to the page of my box.
My subdomain being “www”, maybe “n8n” for example would be more suitable.
I tried adding “:5678” after all the “fr”, it didn’t work.
I tried to add the environment variable “N8N_PORT:5678”, without success either.
I just configured the DNS zone of “n8n.mydomain.fr” to direct it to the desired IP and port. I’m waiting for the 24 hour delay hoping that’s the problem.