Skip to content

Spotweb in Docker on Synology NAS

New guide Published03/02/2022
Updated with DSM7.1 steps and screenshots20/06/2022
Added new port settings and Docker Bridge Network23/07/2022

What is Spotweb?

To quote the GitHub page.

“Spotweb is a decentralized Usenet community based on the Spotnet protocol.”

It is essentially a self-hosted Usenet indexer that integrates with your favourite media managers such as Radarr, and I am going to walk you through setting this up in Docker on your Synology NAS

Lets Begin

The guide has 4 pages and will take around 30 minutes to complete, it is important you follow all the steps in order so take your time.

  • Page 1 – Download and Setup of the Docker Containers
  • Page 2 – Installation of Spotweb
  • Page 3 – Final Docker Changes
  • Page 4 – FAQ

Before we start with the main guide head over and follow the steps in the Docker Bridge Network guide.

Downloading the Spotweb and MariaDB images

Open up Docker within DSM and navigate to the ‘Registry’ tab, then search for ‘Spotweb’.

In the list of available containers download the one made by jgeusebroek as shown below.

Registry Image Selection

When the dialogue pops up asking you to choose a version, make sure you choose ‘latest’ from the list.

While the Spotweb image is downloading do another search for MariaDB as this is the database will we be using.

Again download the official version as shown below using the ‘Latest’ tag when asked.

Setting up the MariaDB Container

In Docker click on the ‘Image’ tab, in the list of your containers select the ‘MariaDB’ image and click on ‘Launch’

The first screen will ask how you want to set up the Docker network, we will be using the default bridge network.

General Settings

Next you will be greeted with the General Settings screen, this is where you can start specifying some of your preferences.

You can change the name of the container to anything you like, and you will want to enable Auto Restart as this will ensure the database starts automatically if you reboot your NAS.

Next up we are going to click on the ‘Advanced Settings’ button, this will take you to a new window with a number of tabs which we are going to work through.


Next we are going to specify some variables that will tell MariaDB what to use for our credentials so Spotweb can access it.

Click the Add button, and fill in the following details as per the table/screenshot. Make note of these you will need them later!

MYSQL_ROOT_PASSWORDYou need to create a strong root user password
MYSQL_USERenter a unique username
MYSQL_PASSWORDenter a unique password

You do not need to set up anything on these tabs.

Press ‘Save’ to go back to the initial setup screen, then press ‘Next’

Port Settings

You will see that the Local Port has Auto in it by default, change this to 3306 then click Next.

Volume Settings

We will now be specifying the directories where the database will be stored along with its config files.

Click on ‘Add Folder’ then select the ‘docker’ folder and create a new sub-folder called ‘mariadb’ click on this folder and click ‘Select’

Now in the Mount Path box enter ‘/var/lib/mysql’


You have now completed the setup of the database. Click on Next to move back to the final summary screen, this is a good time to double-check everything is correct.

Finally, click on Done and the container should start to boot.

Setting up the Spotweb Container

We are now doing the initial setup and will be coming back to complete it later.

Head back into the Image tab and this time Launch the Spotweb image

You will be greeted with the Network screen, we will be using the ‘synobridge’ network we created earlier select it from the list and click Next.

General Settings

Next you can rename the container and enable auto-restart to make sure Spotweb starts up with your NAS, then click Next.

Port Settings

Spotweb wants to use port 80, we need to move it to an alternative port as this is reserved by DSM. Let’s use 9096.

Click Next, you do not need to enter any information on the ‘Volume Settings’ page, click next again and then Click Done on the Summary to start the container.

We will come back to add some additional settings a little later in the guide. You can now move on to Page 2.

Pages: 1 2 3 4

Published inDockerSearch / IndexersSynologyUsenet


  1. Jeroen Jeroen

    Hi Dr Frankenstein, question: the network for mariadb is also the new created synology bridge? The picture says yes, but the text says default bridge

    • Jeroen Jeroen

      Hmm. Know for sure that the passowrd is coorect. Still get error acces diened.
      For root@172.x.x..x

      • Dr_Frankenstein Dr_Frankenstein

        Are you entering the username you created for the database or root?

      • Dr_Frankenstein Dr_Frankenstein

        Sorry ignore that last comment, try having the password with no special characters. I will update the guide to suggest avoiding @£# etc.

    • Dr_Frankenstein Dr_Frankenstein

      Oh missed that screenshot put it on the Synobridge will fix this evening

  2. xIExodusIx xIExodusIx

    Sorry I forgot to tell you that we had a power failure in our district yesterday night for about 2 hours. and after that this problem come up.

    • Dr_Frankenstein Dr_Frankenstein

      Hey, Did you have Spotweb running successfully before the power outage?

      • xiExodusIx xiExodusIx

        Yes it runs successfully, but now it won’t run because of mariadb did not work anymore. I have stopped both containers now. Waiting for a solution or help.

        • Dr_Frankenstein Dr_Frankenstein

          When I get home tonight I can help you get it up and running, are you able to join Discord so we can walk through? Helps me keep the solution for any else who has the issue. I think we can downgrade the database again. To a different release as you error log suggests it is unable to perform an upgrade.

          • xIExodusIx xIExodusIx

            Yes I am, I have Discord installed. The question is, when will you be at home? I am from Germany 🙂

          • Dr_Frankenstein Dr_Frankenstein

            Back about 5:30pm UK time.

  3. xIExodusIx xIExodusIx

    Hi Dr_Frankenstein,
    I have the same problem llike Chalky, mariadb ist starting and stopping the hole time. I have already checked the mount point, and it is set correctly by “File/Folder: /docker/mariadb”, “Mount-Point: /var/lib/mysql”.
    The aria_log file in the mariadb follder includes a lot of entrys (notes and errors):

    2022-05-27 20:29:23+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.8.3+maria~jammy started.
    2022-05-27 20:29:24+00:00 [Note] [Entrypoint]: Switching to dedicated user ‘mysql’
    2022-05-27 20:29:24+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.8.3+maria~jammy started.
    2022-05-27 20:29:24+00:00 [Note] [Entrypoint]: MariaDB upgrade (mariadb-upgrade) required, but skipped due to $MARIADB_AUTO_UPGRADE setting
    2022-05-27 20:29:24 0 [Note] mariadbd (server 10.8.3-MariaDB-1:10.8.3+maria~jammy) starting as process 1 …
    2022-05-27 20:29:24 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
    2022-05-27 20:29:24 0 [Note] InnoDB: Number of transaction pools: 1
    2022-05-27 20:29:24 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
    2022-05-27 20:29:24 0 [Warning] mariadbd: io_uring_queue_init() failed with ENOSYS: check seccomp filters, and the kernel version (newer than 5.1 required)
    2022-05-27 20:29:24 0 [Warning] InnoDB: liburing disabled: falling back to innodb_use_native_aio=OFF
    2022-05-27 20:29:24 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
    2022-05-27 20:29:24 0 [Note] InnoDB: Completed initialization of buffer pool
    2022-05-27 20:29:24 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.7.3.
    2022-05-27 20:29:24 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
    2022-05-27 20:29:24 0 [Note] InnoDB: Starting shutdown…
    2022-05-27 20:29:24 0 [ERROR] Plugin ‘InnoDB’ init function returned error.
    2022-05-27 20:29:24 0 [ERROR] Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.
    2022-05-27 20:29:24 0 [Note] Plugin ‘FEEDBACK’ is disabled.
    2022-05-27 20:29:24 0 [ERROR] Unknown/unsupported storage engine: InnoDB

    I run Docker on a Synology NAS DS918+ with DSM 7.1-42661 Update 1.

    I dont know how to sole this problem, could you please help?

    Thank you

    • I had the same issue, I’m not sure what ended up causing it, but I just deleted the DB since I had nothing other than spotweb in it at that time. Hoping it doesn’t come up again, but I might just change the MariaDB version to fixed instead of latest to prevent any updates from occurring

      • Dr_Frankenstein Dr_Frankenstein

        I will come back in a bit, I will check what I set on my personal setup.

    • Dr_Frankenstein Dr_Frankenstein

      Hey xIExodusIx, sorry for the late reply I am catching up on some missed comments. Have you fixed this yet? If not reach out on Discord or via the Contact Me page under the logo for the site.

      • xIExodusIx xIExodusIx

        Hi Dr_Frankenstein, no i havn’t fixed it until now. I’m thinking about to delete the “mysql” Folder, but not did it until now. Sorry for my late response, I have not been at homme for about 2 Weeks and could not read your reply.

        • Dr_Frankenstein Dr_Frankenstein

          Are you able to reach out on Discord so we can setup a thread to talk through.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed. – writing Synology Docker Guides since 2016 – Join My Discord!