I am a total beginner to self-hosted world (docker ect…).
Possibly, this is just a quick fix, what is the domain used in n8n when setting up Baserow (both applications are self-hosted)? Currently, I’m just using: https://mysubdomain.mydomain.com and not getting any connection to my Baserow.
I’m using nginx proxy manager and have followed this post to get it set up, and I thought working:
Am I missing something obvious, I have looked at both the n8n and Baserow communities and tried some pretty targeted google searches with no luck.
I don’t run this setup anymore. If I recall correctly, just use the command to list docker containers. Use the docker container name and just made sure they were on the same docker network.
@joffcom as the original posted, said connection not working
I am using http://localhost:9080 as the baserow URL in n8n. and that’s the URL I use to login to my local baserow and using the only credentials that I have
default URL was https://api.baserow.io
what is the equivalent URL for API for self hosted?
In short, i get an ERROR cannot connect to API Server upon signup.
It seems to me that it has problem or conflict Websocket implement. Thus, may need to manually adjust. Unfortunately, I do not know how. yet i am completely new to Linux world. So I am looking forward for guidance.
Please kindly assist.
Below is my configuration, follow your instruction to rheaver.
For this configuration:
1 - If i change destination to baserow (my docker name), i cannot see the baserow signup page with error Bad Gateway (my baserow docker network is different from NPM (Nginx Proxy Manager) docker network.
2 - If i change destination to http://baserow:80, I get Internal ERROR
In your case localhost is local to the machine you are running on, as baserow won’t be running on what n8n will resolve as localhost it will always fail.
Assuming a default network configuration you could try connecting to 172.17.0.1 and see if that works if not you may need to configure BASEROW_EXTRA_ALLOWED_HOSTS
@ratanainfo I wouldn’t worry too much about the documented nginx settings as nginx proxy manager takes care of all of that.
For websockets you just need to enable the toggle under the details tab and you should be good to go for that.
I would remove the web frontend port from the compose file as it doesn’t look like you will need that and also remove the amount of workers and run minimal then see if that gets things working.
I will grab a screenshot of the settings I use in Portainer for Baserow later today