Server installation via Portainer

Hello All,

I'm looking forward to switching to Joplin.

I have a self-hosted Ubuntu server running docker with Portainer. I have installed and successfully configured a few apps so far but am not an IT professional. I'm having trouble getting my joplin server installed. After starting a stack, I usually click on the "Published Ports" link to first check out the app locally via HTTP before I set it up in my NGINX reverse proxy. When I click the link, I get a webpage with "Invalid origin: hp://192.168.1.XX:22300". I've already spent some time looking at similar solutions, but they all seem to involve the reverse proxy which is not yet necessary.

Please help! Thanks.

Note I used "hs" and "hp" instead of the usual due to site rules.

My docker compose yaml is:

version: '3'
services:
    db:
        container_name: joplin-db
        restart: unless-stopped
        image: postgres:13.1
        ports:
            - "5432:5432"
        volumes:
            - /data/joplin-data:/var/lib/postgresql/data
        environment:
            - POSTGRES_PASSWORD=joplin
            - POSTGRES_USER=joplin
            - POSTGRES_DB=joplin
    app:
        container_name: joplin-server
        environment:
            - APP_BASE_URL=hs://www.example.com
            - APP_PORT=22300
            - POSTGRES_PASSWORD=joplin
            - POSTGRES_DATABASE=joplin
            - POSTGRES_USER=joplin 
            - POSTGRES_PORT=5432 
            - POSTGRES_HOST=db
            - DB_CLIENT=pg
        restart: unless-stopped
        image: etechonomy/joplin-server:latest
        ports:
            - "22300:22300"
        depends_on:
            - db

If you'd like to test it locally first, you have to set APP_BASE_URL to the local IP, in your case http://192.168.1.XX:22300.

That worked! Thank you.

I just realized that every time I update the compose file, it removed the new container from my NGINX network too.

1 Like