How to Install Plane on Your Synology NAS

by

How to Install Plane on Your Synology NAS

Plane is an open-source software development tool to manage issues, sprints, and product roadmaps with peace of mind. It allows users to start with a basic task tracking tool and gradually adopt various project management frameworks like Agile, Waterfall, and many more. My personal experience with Plane: clean, modern UI and solid self-hosted performance felt lighter and more focused than most alternatives Iā€™ve tried. I use Plane to manage personal side projects and small team sprints directly from my Synology NAS, keeping everything private and offline-capable without relying on cloud tools. In this step by step guide I will show you how to install PlaneĀ on yourĀ Synology NAS using Docker & Dockhand.

šŸ’”Note:Ā This guide works perfectly with the latest Plane v1.4.2Ā release.

  • STEP 1

Please Support My work by Making a Donation.

  • STEP 2

InstallĀ Dockhand using my step by step guide. If you already have Dockhand installed on your Synology NAS, skip this STEP. āš ļøAttention: Make sure you have installed the latest Dockhand version.

  • STEP 3

Make sure you have a synology.me Wildcard Certificate. Follow my guide to get a Wildcard Certificate. If you already have a synology.me Wildcard certificate, skip this STEP.

  • STEP 4

Go toĀ Control PanelĀ /Ā Login PortalĀ /Ā AdvancedĀ Tab / clickĀ Reverse Proxy. Follow the instructions in the image below.

Plane Synology NAS Set up 1

  • STEP 5

Now click the ā€œCreateā€ button. Follow the instructions in the image below.

Plane Synology NAS Set up 2

  • STEP 6

After you click the Create button, the window below will open. Follow the instructions in the image below.

On the General area, set the Reverse Proxy Name description: type in Plane. After that, add the following instructions:

Source:
Protocol:Ā HTTPS
Hostname: plane.yourname.synology.me
Port:Ā 443

Check Enable HSTS

Destination:
Protocol:Ā HTTP
Hostname:Ā localhost
Port:Ā 3356

Plane Synology NAS Set up 3

  • STEP 7

On the Reverse Proxy Rules click the Custom HeaderĀ tab. ClickĀ CreateĀ and then, from the drop-down menu, clickĀ WebSocket. After you click on WebSocket, two Header Names and two Values will be automatically added. ClickĀ Save. Follow the instructions in the image below.

Synology Proxy WebSocket

  • STEP 8

Go to Control Panel / Network / Connectivity tab/ Check Enable HTTP/2 then click Apply. Follow the instructions in the image below.

Plane Synology NAS Set up 4

  • STEP 9

Go to Control Panel / Security / Advanced tab/ Check Enable HTTP CompressionĀ then click Apply. Follow the instructions in the image below.

Plane Synology NAS Set up 5

  • STEP 10

Go toĀ File StationĀ and open the docker folder. Inside the docker folder, create one new folder and name itĀ plane. Follow the instructions in the image below.
Note: Be careful to enter only lowercase, not uppercase letters.

Plane Synology NAS Set up 6

  • STEP 11

Now create four new folders inside the plane folder that you created at STEP 10Ā and name them db, rabbitmq, redis, uploads. Follow the instructions in the image below.
Note: Be careful to enter only lowercase, not uppercase letters.

Plane Synology NAS Set up 7 new 2025

  • STEP 12

Open your browser and type in http://synology-ip-address:3866 to connect to your Dockhand container. On the left sidebar, click Stacks then + Create. Follow the instructions in the image below.

Dockhand add stack

  • STEP 13

In the Stack name field, type in plane. āš ļøWarning: Type in the name in lowercase letters. The installation process can take up to a few seconds/minutes. It will depend on your Internet speed connection. Follow the instructions in the image below.

Note: Copy Paste the code below in the Dockhand Compose Stack then click Load.

services:
  redis:
    image: redis:8
    container_name: Plane-REDIS
    security_opt:
      - no-new-privileges:true
    read_only: false
    user: 0:0
    healthcheck:
      test: ["CMD-SHELL", "redis-cli ping || exit 1"]
    volumes:
      - /volume1/docker/plane/redis:/data:rw
    environment:
      TZ: Europe/Bucharest
    restart: on-failure:5

  db:
    image: postgres:18
    command: postgres -c 'max_connections=1000'
    container_name: Plane-DB
    hostname: plane-db
    security_opt:
      - no-new-privileges:true
    healthcheck:
      test: ["CMD", "pg_isready", "-q", "-d", "plane", "-U", "planeuser"]
      timeout: 45s
      interval: 10s
      retries: 10
    volumes:
      - /volume1/docker/plane/db:/var/lib/postgresql:rw
    environment:
      POSTGRES_DB: plane
      POSTGRES_USER: planeuser
      POSTGRES_PASSWORD: planepass
    restart: on-failure:5
  
  plane-mq:
    image: rabbitmq:4.3.6-management-alpine
    container_name: Plane-RABBITMQ
    volumes:
      - /volume1/docker/plane/rabbitmq:/var/lib/rabbitmq:rw
    environment:
      RABBITMQ_HOST: plane-mq
      RABBITMQ_PORT: 5672
      RABBITMQ_DEFAULT_USER: plane
      RABBITMQ_DEFAULT_PASS: plane
      RABBITMQ_DEFAULT_VHOST: plane
      RABBITMQ_VHOST: plane
      AMQP_URL: amqp://plane:plane@plane-mq:5672/plane
    restart: on-failure:5

  minio:
    image: chainguard/minio
    command: server /export --console-address ":9090"
    container_name: Plane-MINIO
    hostname: plane-minio
    security_opt:
      - no-new-privileges:true
    user: 0:0
    healthcheck:
      test: ["CMD", "mc", "ready", "local"]
      interval: 5s
      timeout: 5s
      retries: 5
    volumes:
      - /volume1/docker/plane/uploads:/export:rw
    environment:
      MINIO_ROOT_USER: marius
      MINIO_ROOT_PASSWORD: mariushosting
    restart: on-failure:5

  back:
    image: artifacts.plane.so/makeplane/plane-backend:stable
    command: ./bin/docker-entrypoint-api.sh
    container_name: Plane-BACK
    hostname: api
    security_opt:
      - no-new-privileges:true
    user: 0:0
    healthcheck:
      test: wget --no-verbose --tries=1 --spider http://api:8000
    env_file:
      - .env
    depends_on:
      redis:
        condition: service_healthy
      db:
        condition: service_healthy
    restart: on-failure:5

  worker:
    image: artifacts.plane.so/makeplane/plane-backend:stable
    command: ./bin/docker-entrypoint-worker.sh
    container_name: Plane-WORKER
    hostname: worker
    security_opt:
      - no-new-privileges:true
    user: 0:0
    env_file:
      - .env
    depends_on:
      redis:
        condition: service_healthy
      db:
        condition: service_healthy
      back:
        condition: service_started
      plane-mq:
        condition: service_started
    restart: on-failure:5
        
  beat:
    image: artifacts.plane.so/makeplane/plane-backend:stable
    command: ./bin/docker-entrypoint-beat.sh
    container_name: Plane-BEAT
    hostname: beat-worker
    security_opt:
      - no-new-privileges:true
    user: 0:0
    env_file:
      - .env
    depends_on:
      redis:
        condition: service_healthy
      db:
        condition: service_healthy
      back:
        condition: service_started
      plane-mq:
        condition: service_started
    restart: on-failure:5

  migrator:
    image: artifacts.plane.so/makeplane/plane-backend:stable
    container_name: Plane-MIGRATOR-EXITED
    restart: no
    env_file:
      - .env
    command: ./bin/docker-entrypoint-migrator.sh
    depends_on:
      db:
       condition: service_healthy
      redis:
       condition: service_healthy
      plane-mq:
       condition: service_started

  front:
    image: artifacts.plane.so/makeplane/plane-frontend:stable
    container_name: Plane-FRONT
    hostname: web
    security_opt:
      - no-new-privileges:true
    user: 0:0
    healthcheck:
      test: ["CMD-SHELL", "nc -z 127.0.0.1 3000 || exit 1"]
      interval: 10s
      timeout: 5s
      retries: 3
      start_period: 90s
    env_file:
      - .env
    depends_on:      
      back:
        condition: service_started
      worker:
        condition: service_started
    restart: on-failure:5

  space:
    image: artifacts.plane.so/makeplane/plane-space:stable
    container_name: Plane-SPACE
    hostname: plane-space
    security_opt:
      - no-new-privileges:true
    user: 0:0
    env_file:
      - .env
    depends_on:      
      back:
        condition: service_started
      worker:
        condition: service_started
      front:
        condition: service_started
    restart: on-failure:5

  admin:
    image: artifacts.plane.so/makeplane/plane-admin:stable
    container_name: Plane-ADMIN
    depends_on:
      - back
      - front
    restart: on-failure:5
      
  live:
    image: artifacts.plane.so/makeplane/plane-live:stable
    container_name: Plane-LIVE
    env_file:
      - .env
    depends_on:
      - back
      - front
    restart: on-failure:5

  proxy:
    image: artifacts.plane.so/makeplane/plane-proxy:v0.27.1
    container_name: Plane-PROXY
    hostname: planeproxy
    security_opt:
      - no-new-privileges:true
    ports:
      - 3356:80
    env_file:
      - .env
    environment:
      FILE_SIZE_LIMIT: 
      BUCKET_NAME: uploads
    depends_on:      
      back:
        condition: service_started
      front:
        condition: service_started
      space:
        condition: service_started
    restart: on-failure:5

Note: Before you paste the code above in the Stack editor area below, change the value for TZ.Ā (Select your current Time Zone from this list.)
Note: Before you paste the code above in the Stack editor area below, change the value for MINIO_ROOT_USER and type in your username. marius is an example for a username.
Note: Before you paste the code above in the Stack editor area below, change the value for MINIO_ROOT_PASSWORD and type in your password. mariushosting is an example for a password.

Plane Synology NAS Set up 9 new 2030

Click the Load button. Download the .env file by clicking the blue link below and then upload it from your computer. Follow the instructions in the image below. šŸ”’Note: Support my work to unlock the password. You can use this password to download any file on mariushosting forever!

šŸ‘‰šŸ»Download .env file

Note: On the Environment variables change the value for WEB_URL. Type in your own synology.me DDNS that you have previously created at STEP 6 with https at the beginning.
Note: On the Environment variables change the value for CORS_ALLOWED_ORIGINS. Type in your own synology.me DDNS that you have previously created at STEP 6 with https at the beginning.
Note: On the Environment variables change the value for SECRET_KEY.Ā (Generate your own 32 length SECRET_KEY.)
Note: On the Environment variables change the value for LIVE_SERVER_SECRET_KEY.Ā (Generate your own 32 length LIVE_SERVER_SECRET_KEY.)
Note: On the Environment variables change the value for AWS_ACCESS_KEY_ID and type in your own MINIO_ROOT_USER that you have previously added in the stack editor.
Note: On the Environment variables change the value for AWS_SECRET_ACCESS_KEY and type in your own MINIO_ROOT_PASSWORD that you have previously added in the stack editor.
āš ļøWarning: Do not change any of the other values. All the values should be inside ” “.

Click Create & Start. Follow the instructions in the image below.

Plane Synology NAS Set up 10 new 2030

  • STEP 14

If everything goes right, you will see the following message at the bottom right of your screen: ā€œCreated stack “plane”ā€œ.

Dockhand add stack successfully

  • STEP 15

In the left sidebar, click Containers.āš ļøWarning: Wait approximately 5-10 minutes (refresh this Dockhand/Containers page from time to time) until your Plane-MIGRATOR-EXITEDĀ container is marked as exited. This is a normal behavior. Go straight to STEP 16.

Plane Synology NAS Set up 11 new 2030

  • STEP 16

šŸŸ¢Please Support My work by Making a Donation. Almost 99,9% of the people that install something using my guidesĀ forget to support my work, or justĀ ignoreĀ STEP 1. Iā€™ve been very honest about this aspect of my work since the beginning: I donā€™t run any ADS, I donā€™t require subscriptions, paid or otherwise, I donā€™t collect IPs, emails, and I donā€™t have any referral links from Amazon or other merchants. I also donā€™t have any POP-UPs or COOKIES. I have repeatedly been told over the years how much I have contributed to the community. Itā€™s something I love doing and have been honest about my passion since the beginning. But I also Need The Community to Support me Back to be able to continue doing this work.

  • STEP 17

Now open your browser and type in your HTTPS/SSL certificate like this https://plane.yourname.synology.me/god-mode/ – In my case it’s https://plane.mariushosting.synology.me/god-mode/ If everything goes right, you will see the Plane Admin page. Type in your own info, uncheck the usage collect events telemetry then click Continue. Follow the instructions in the image below. āš ļøNote: Don’t forget to add /god-mode/ at the end of your synology.me DDNS.

Plane Synology NAS Set up 12 new 2030

  • STEP 18

In this section you can set up your SMTP email and other details. To activate the SMTP details, follow the instructions on how to set up email notifications on Plane. On the left sidebar, click Email. At the top right of the page, activate/switch the email option to on. Type in your own SMTP details, then click Save changes. āš ļøWarning: Make sure you switch on the email setting or you will get a blank page in this area.

Plane Synology NAS Set up 13 new 2030

  • STEP 19

Now open your browser and type in your HTTPS/SSL certificate like this https://plane.yourname.synology.meĀ – In my case it’s https://plane.mariushosting.synology.me Type in your Email address that you have previously added at STEP 17. Click Continue. Follow the instructions in the image below.

Plane Synology NAS Set up 14 new 2030

  • STEP 20

Type in your own Password, then click Continue. Follow the instructions in the image below.

Plane Synology NAS Set up 15 new 2030

  • STEP 21

Upload your own profile icon. Type in your own Name, then click Continue. Follow the instructions in the image below.

Plane Synology NAS Set up 16 new 2030

  • STEP 22

Type in your Workspace name and the Company size, then click Create Workspace. Follow the instructions in the image below.

Plane Synology NAS Set up 17 new 2030

  • STEP 23

Close the pop-up window. Click “No thanks, I will explore it myself”. Follow the instructions in the image below.

Plane Synology NAS Set up 18 new 2030

  • STEP 24

Your Plane dashboard at a glance! At the top right of the page, click the profile icon then Preferences. In this area, you can change the theme from light to dark. Follow the instructions in the image below.

Plane Synology NAS Set up 19 new 2030

  • STEP 25

Your Plane dashboard at a glance!

Plane Synology NAS Set up 20 new 2030

Enjoy Plane!

šŸ†˜TROUBLESHOOTING

If you encounter issues by using this container, make sure to check out the Common Docker issuesĀ article.

Note: Can I run Docker on my Synology NAS?Ā See the supported models.
Note: How to Back Up Docker Containers on your Synology NAS.
Note: Find outĀ how to update the Plane container with the latest image.
Note: How to Free Disk Space on Your NAS if You Run Docker.
Note: How to Schedule Start & Stop For Docker Containers.
Note: How to Activate Email Notifications.
Note: How to Add Access Control Profile on Your NAS.
Note: How to Change Docker Containers Restart Policy.
Note: How to Use Docker Containers With VPN.
Note: Convert Docker Run Into Docker Compose.
Note: How to Clean Docker.
Note: How to Clean Docker Automatically.
Note: Best Practices When Using Docker and DDNS.
Note: Some Docker Containers Need WebSocket.
Note: Find out the Best NAS Models For Docker.
Note: Activate Gmail SMTP For Docker Containers.

This post was updated on Monday / October 12th, 2026 at 1:27 PM

No sponsors, no corporations, no ads, no subscriptions, no membership tiers, no referral links, no pop-ups, no cookies, no tracking code. Just pure guides for the community from Marius.