Skip to content

Spotweb in Docker on Synology NAS

Spotweb Installation

Open up a new tab in your browser and go to the address below, changing the IP address to the one used by your NAS.

http://yournasip:9096/install.php

Please note
1 – As you progress through the next screens you may get a blank screen when submitting a section. If this happens you will need to manually advance to the next settings page by changing the URL in your browser (I have noted the page numbers under each screenshot)

2 – If you receive an error on a page – the selections you made will reset so double check them before resubmitting the page.

Page 1 – Web Settings

You should see the screen below, confirming Spotweb is running.

Page 1

Click on ‘Next’

Page 2 – Database Settings

You will be asked to fill in the database settings. Fill in all sections and remember if you used two different passwords for the Root user and your normal user enter them correctly.

OptionValue
typeMySQL
serverIP address of your NAS
port3306
Root PasswordThe root password you created earlier
MySQL databasespotweb
Database user nameThe username you created earlier
Database user passwordThe user password you created earlier
Page 2

Now click ‘Verify database’ if the settings are correct you will move to the next page.

Page 3 – Usenet server settings

Next you will need to enter the details of your Usenet provider, there are a number of pre-defined options, if yours is not listed choose ‘custom’ (These will be the same connection details as used in NZBGet or SabNZBd)

Click on ‘Verify usenet server’ to check your settings are good.

Page 3

Page 4 – Spotweb type

On the final settings page we are going to set Spotweb up for a Single user you can then fill in all the remaining sections based on your own preferences filling in all sections.

Page 4

When you click ‘Create system’ the database for Spotweb will be created, You will then see the screen below.

Page 99

While it’s tempting to jump in and start using the main interface, don’t yet! Close the tab and move on to Page 3 (almost done)


Pages: 1 2 3 4

Published inDockerSearch / IndexersSynologyUsenet

32 Comments

  1. 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.

  2. 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.

drfrankenstein.co.uk – writing Synology Docker Guides since 2016 – Join My Discord!