Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setting base url doesn't solve running in subdirectory (e.g. behing Nginx) #212

Closed
SmallhillCZ opened this issue Jan 15, 2020 · 2 comments
Closed

Comments

@SmallhillCZ
Copy link

Describe the bug
The Base URL setting described in https://docs.n8n.io/#/configuration does not support running the app in subdirectory behind reverse proxy. Static Vue files are not loaded as <base> href tag is not set.

To Reproduce
Steps to reproduce the behavior:

  1. Run n8n with base url set to https://example.com/n8n
docker run -it --rm   --name n8n   -p 80:5678 -e "VUE_APP_URL_BASE_API=http://example.com/n8n" n8nio/n8n
  1. Open http://example.com/n8n in browser
  2. You see blank page

Expected behavior
n8n loads okay.

Environment (please complete the following information):
Using Docker
n8n 0.46.0

@janober
Copy link
Member

janober commented Jan 17, 2020

Yes, VUE_APP_URL_BASE_API is not meant for that. It simply tells the frontend how it can reach the backend.

I never tried to run it in a subfolder but can imagine that it will cause some issues. Here and maybe also in other parts of the application. The currently recommended way is to run n8n under its own domain/subdomain. Have no idea how much work it would be to run in a subfolder. It is honestly also right now not a priority at as I do not have many resources available, there are so many other things to do and running it on a subdomain is a viable alternative. Very sorry.

@janober
Copy link
Member

janober commented Jan 17, 2020

Addition: I would also not call it a bug right now. Would say it is more of a "feature-request" which you can post here:
https://community.n8n.io/
If a lot of people are interested in it the priority on it will obviously change.

So close this issue for now.

@janober janober closed this as completed Jan 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants