**Running n8n via (Docker, npm, n8n cloud, desktop app):**npm
**Operating system:**Ubuntu 24.04 LTS x64
No vultr firewall
Im aware of βself hosting n8n is considered to be an advanced optionβ but due to legal reasons and running under a GOV cert i cant run my process in a cloud setup.
Im running this,
root@vultr:~# n8n
User settings loaded from: /root/.n8n/config
Initializing n8n process
n8n ready on 0.0.0.0, port 5678
Version: 1.48.1
Editor is now accessible via:
http://localhost:5678/
I installed from npm and did a certbot update for subdomain as well.
In cloudflare i bypassed the subdomain n8n in the setting,
n8n
71.54.213.120
DNS only
Auto
Under the apache sites-enabled folder i have:
/etc/apache2/sites-enabled/000-default.conf (my functioning www wordpress server setting)
/etc/apache2/sites-enabled/n8n.conf:
<VirtualHost *:443>
ProxyPreserveHost On
ProxyRequests Off
ServerAdmin [email protected]
ServerName n8n.donotdox.com
ServerAlias n8n.donotdox.com
ProxyPass / http://0.0.0.0:5678/
ProxyPassReverse / http://0.0.0.0:5678/
</VirtualHost>
Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
Apache/2.4.58 (Ubuntu) Server at n8n.donotdox.com Port **80**
I have tried different settings all day, but what i cant wrap my head around is why the error message over https show port 80?
Another thing that stands out for me is, 0.0.0.0:5678 as service ip for n8n, is that normal or do i need to set up something?
Anyone knows what im missing to get n8n up and running?
I tested @geckse example of the setup file as well but that broke my site
<VirtualHost _default_:443>
SSLEngine on
ProxyPreserveHost On
ProxyRequests Off
ServerName n8n.let-the-work-flow.com
ProxyPass / http://localhost:5678/
ProxyPassReverse / http://localhost:5678/
</VirtualHost>
Jun 29 17:22:53 vultr systemd[1]: Starting apache2.service - The Apache HTTP Server...
ββ Subject: A start job for unit apache2.service has begun execution
ββ Defined-By: systemd
ββ Support: http://www.ubuntu.com/support
ββ
ββ A start job for unit apache2.service has begun execution.
ββ
ββ The job identifier is 195.
Jun 29 17:22:54 vultr systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
ββ Subject: Unit process exited
ββ Defined-By: systemd
ββ Support: http://www.ubuntu.com/support
ββ An ExecStart= process belonging to unit apache2.service has exited.
ββ The process' exit code is 'exited' and its exit status is 1.
Jun 29 17:22:54 vultr systemd[1]: apache2.service: Failed with result 'exit-code'.
ββ Subject: Unit failed
ββ Defined-By: systemd
ββ Support: http://www.ubuntu.com/support
ββ The unit apache2.service has entered the 'failed' state with result 'exit-code'.
Jun 29 17:22:54 vultr systemd[1]: Failed to start apache2.service - The Apache HTTP Server.
ββ Subject: A start job for unit apache2.service has failed
ββ Defined-By: systemd
ββ Support: http://www.ubuntu.com/support
ββ A start job for unit apache2.service has finished with a failure.
ββ The job identifier is 195 and the job result is failed.