How to forward requests to remote server
So I am very much a newb when it comes to docker and containers. I've successfully set up an n8n service on the same server as dokploy. I'm now trying to figure out how to replicate that n8n service on a remote server. Here are the details:
DNS config:
I have a wildcard A record forwarding all subdomains to the dokploy IP address. There is not Proxy enabled, it's DNS Only.
Environment Variables:
I've set N8N_HOST to the appropriate subdomains (task.mydomain.com - local, and test.mydomain.com - remote). The n8n instance running on the same server as dokploy is functioning on that subdomain as expected. The test.mydomain.com which should be running on the remote server is showing a 404 page not found error.
I thought that maybe there was a port conflict, so on the n8n service running on the remote server, I changed the N8N_PORT to a different port (6789 instead of 4578)
Domain Settings:
Service Name: test.mydomain.com
Path: /
Container Port: 6789 (same as N8N_PORT in environment variables.
HTTPS: disabled, but when enabled with Let's Encrypt, I still get the same 404 error, just on the https protocol
Logs:
Editor is now accessible via:
http://test.mydomain.com:6789
When I compare the logs with the working local version of N8N I don't see any differences, other than the port and subdomain.
There's got to be some simple setting that I'm missing. Can anyone help me out?
DNS config:
I have a wildcard A record forwarding all subdomains to the dokploy IP address. There is not Proxy enabled, it's DNS Only.
Environment Variables:
I've set N8N_HOST to the appropriate subdomains (task.mydomain.com - local, and test.mydomain.com - remote). The n8n instance running on the same server as dokploy is functioning on that subdomain as expected. The test.mydomain.com which should be running on the remote server is showing a 404 page not found error.
I thought that maybe there was a port conflict, so on the n8n service running on the remote server, I changed the N8N_PORT to a different port (6789 instead of 4578)
Domain Settings:
Service Name: test.mydomain.com
Path: /
Container Port: 6789 (same as N8N_PORT in environment variables.
HTTPS: disabled, but when enabled with Let's Encrypt, I still get the same 404 error, just on the https protocol
Logs:
Editor is now accessible via:
http://test.mydomain.com:6789
When I compare the logs with the working local version of N8N I don't see any differences, other than the port and subdomain.
There's got to be some simple setting that I'm missing. Can anyone help me out?
