Unable to host application builder

Please fill in the questionnaire below.

Technical Help Questionnaire

Have you read and followed the instructions at: *READ ME FIRST* Technical Help FAQs - #2 by nigel ?

Answer: I have

Self-Hosted Installation and Setup Questions

Delete this section if you are using Baserow.io.

How have you self-hosted Baserow.

I’m hosting it via portainer on a Synology NAS. While using internal port forwarding system.

What are the specs of the service or server you are using to host Baserow.

32GB RAM

Which version of Baserow are you using.

1.28.0

How have you configured your self-hosted installation?

  baserow:
    image: baserow/baserow
    container_name: baserow
    volumes:
      - /volume1/docker/baserow/main:/baserow/data
    restart: always
    networks:
      - stack
    ports:
      - 8082:80
      - 8143:443
    environment:
      - BASEROW_PUBLIC_URL=https://baserow.domain.eu
      - DATABASE_URL=postgresql://baserow:baserow@baserow-db:5432/baserow  # Update port
      - REDIS_URL=redis://redis:6379
      - BASEROW_CADDY_ADDRESS=https://oksjonid.domain.eu
    depends_on:
      - database
      - redis

DNS is already configured to use host oksjonid.domain.eu to a value baserow.domain.eu

Port 8082 is forwarded to baserow.domain.eu which works great. Even the api and webhooks do. It’s just the application publishing that’s a pain right now.

Tried BASEROW_CADDY_ADDRESS=:443 as well but no luck.

Describe the problem

Unable to use Application Builder on additional domain. An easy fix would be to just use it on sublink instead as such: baserow.domain.eu/oksjonid, but that’s not the case right now.

Currently when selecting domain as oksjonid.domain.eu and host automatically uses baserow.domain.eu it publishes successfully, but says unable to connect.

Hey @ihoststuff,

When you say application publishing what do you actually mean? Is it using applications with custom domains or are they just generally failing?

Attached a screenshot

Hi @ihoststuff, can you share the exact error that you’re getting when visiting the URL of the application? I’m not sure how your Baserow instance is configured on your Synology NAS, but more information is required to figure out what’s going wrong.

It just wont connect. Also tried with BASEROW_BUILDER_DOMAINS and a CNAME in domain DNS settings to forward oksjon.domain.eu to baserow.domain.eu. No clue on how to fix that.

I’m using the default reverse proxy on my synology. Websockets are also turned on.

I suspect that if you’re using the default reverse proxy of your Snology Nas, that you would need to add an extra hostname to it. Currently, it only listens on baserow.domain.eu, but it should also listen on oksjon.domain.eu.

I don’t know how to change to, would have to ask this in the forum of Synology.

Note that this is based on the limited information that I have. I don’t know how your DNS is configured, and I don’t know how your Synology is configured. It’s advising in the dark here.

Honestly that worked. I’m quite amazed as it just seemed too easy to work that way. For reference everything is same as the screenshot I attached, just the domain name has changed to oksjon.domain.eu

As the destination port is same as original hosted application i expected to have just another baserow access point, but it does work correctly with the published application. Not sure how it’s possible, but very thankful either way.

Thank you Bram!

Glad to hear that it worked for you @ihoststuff!