• Posts

  • Joined

  • Last visited

Everything posted by vurt

  1. Sorry I'm not familiar with "drop the key", do you mean delete "migrations_lock_lock_key_unique" from the database?
  2. No worries, I appreciate you for providing the docker already, I'm sure this is some code change with Ghost, it seems to have gotten a significant update to v4. @cheesemarathon is there a way to roll back to a previous version?
  3. @cheesemarathon I just updated the Ghost docker and it won't start, getting a "wrong name for index" error. I'm pasting this from the log: [2021-03-19 16:08:49] [36mINFO[39m Ghost is running in production... [2021-03-19 16:08:49] [36mINFO[39m Your site is now available on https://my.domain/ghost/ [2021-03-19 16:08:49] [36mINFO[39m Ctrl+C to shut down [2021-03-19 16:08:49] [36mINFO[39m Ghost server started in 0.981s [2021-03-19 16:08:49] [31mERROR[39m alter table `migrations_lock` add primary key `migrations_lock_pkey`(`lock_key`) - ER_WRONG_NAME_FOR_INDEX: Incorrect index name 'migrations_lock_lock_key_unique' [31m [31malter table `migrations_lock` add primary key `migrations_lock_pkey`(`lock_key`) - ER_WRONG_NAME_FOR_INDEX: Incorrect index name 'migrations_lock_lock_key_unique'[39m [1m[37mError ID:[39m[22m [90m6447c370-88cd-11eb-955f-6b297b56d303[39m [1m[37mError Code: [39m[22m [90mER_WRONG_NAME_FOR_INDEX[39m [90m----------------------------------------[39m [90mInternalServerError: alter table `migrations_lock` add primary key `migrations_lock_pkey`(`lock_key`) - ER_WRONG_NAME_FOR_INDEX: Incorrect index name 'migrations_lock_lock_key_unique' at new GhostError (/var/lib/ghost/versions/4.1.0/node_modules/@tryghost/errors/lib/errors.js:10:26) at DatabaseStateManager.getState (/var/lib/ghost/versions/4.1.0/core/server/data/db/state-manager.js:63:32) at processTicksAndRejections (internal/process/task_queues.js:97:5) Error: ER_WRONG_NAME_FOR_INDEX: Incorrect index name 'migrations_lock_lock_key_unique' at Query.Sequence._packetToError (/var/lib/ghost/versions/4.1.0/node_modules/mysql/lib/protocol/sequences/Sequence.js:47:14) at Query.ErrorPacket (/var/lib/ghost/versions/4.1.0/node_modules/mysql/lib/protocol/sequences/Query.js:79:18) at Protocol._parsePacket (/var/lib/ghost/versions/4.1.0/node_modules/mysql/lib/protocol/Protocol.js:291:23) at Parser._parsePacket (/var/lib/ghost/versions/4.1.0/node_modules/mysql/lib/protocol/Parser.js:433:10) at Parser.write (/var/lib/ghost/versions/4.1.0/node_modules/mysql/lib/protocol/Parser.js:43:10) at Protocol.write (/var/lib/ghost/versions/4.1.0/node_modules/mysql/lib/protocol/Protocol.js:38:16) at Socket.<anonymous> (/var/lib/ghost/versions/4.1.0/node_modules/mysql/lib/Connection.js:88:28) at Socket.<anonymous> (/var/lib/ghost/versions/4.1.0/node_modules/mysql/lib/Connection.js:526:10) at Socket.emit (events.js:314:20) at addChunk (_stream_readable.js:297:12) at readableAddChunk (_stream_readable.js:272:9) at Socket.Readable.push (_stream_readable.js:213:10) at TCP.onStreamRead (internal/stream_base_commons.js:188:23) -------------------- at Protocol._enqueue (/var/lib/ghost/versions/4.1.0/node_modules/mysql/lib/protocol/Protocol.js:144:48) at Connection.query (/var/lib/ghost/versions/4.1.0/node_modules/mysql/lib/Connection.js:198:25) at /var/lib/ghost/versions/4.1.0/node_modules/knex/lib/dialects/mysql/index.js:134:18 at new Promise (<anonymous>) at Client_MySQL._query (/var/lib/ghost/versions/4.1.0/node_modules/knex/lib/dialects/mysql/index.js:128:12) at Client_MySQL.query (/var/lib/ghost/versions/4.1.0/node_modules/knex/lib/client.js:168:17) at Runner.query (/var/lib/ghost/versions/4.1.0/node_modules/knex/lib/runner.js:151:36) at Runner.queryArray (/var/lib/ghost/versions/4.1.0/node_modules/knex/lib/runner.js:243:19) at /var/lib/ghost/versions/4.1.0/node_modules/knex/lib/runner.js:38:25 at /var/lib/ghost/versions/4.1.0/node_modules/knex/lib/runner.js:277:24 at processTicksAndRejections (internal/process/task_queues.js:97:5) at async DatabaseStateManager.getState (/var/lib/ghost/versions/4.1.0/core/server/data/db/state-manager.js:39:13) at async DatabaseStateManager.makeReady (/var/lib/ghost/versions/4.1.0/core/server/data/db/state-manager.js:72:25) at async initDatabase (/var/lib/ghost/versions/4.1.0/core/boot.js:49:5) at async bootGhost (/var/lib/ghost/versions/4.1.0/core/boot.js:277:9)[39m [39m [2021-03-19 16:08:49] [35mWARN[39m Ghost is shutting down [2021-03-19 16:08:49] [35mWARN[39m Ghost has shut down [2021-03-19 16:08:49] [35mWARN[39m Your site is now offline [2021-03-19 16:08:49] [35mWARN[39m Ghost was running for a few seconds
  4. Ah interesting, that makes sense but the error it gave doesn't seem related to the cause. This will be the first time I haven't done anything wrong—I always default to user (me) error 😅 Thank you and sorry for the extremely late response! The forum doesn't email notifications and I don't come here much.
  5. I managed to get the Ghost docker running with MariaDB. After an initial hiccup with logging into Ghost admin (a Firefox restart fixed it), everything seems fine from and But if I tried to access it internally at my.ip/blog or my.ip/blog/ghost, I get this Firefox error: Error code: SSL_ERROR_RX_RECORD_TOO_LONG Safari says it can't establish a secure connection to my IP. Has anyone encountered this? I'm guessing it's related to Nginx but my other dockers are accessible.
  6. Thanks for the tip! I'm equally surprised the feature is disabled by default.
  7. That fixed it!! Thank you. I still don't understand why it worked previously though. By "custom docker bridge", do you mean the custom network? I just looked this up: After running the command $ docker network create my-net Do I then use the unRAID GUI to edit all my dockers' config to point Network Type to "my–net" instead of "bridge"? Would that be it or are there other stuff I need to do? My Emby is currently set to "Host", will that stay that way?
  8. Do you mean the /calibre? I renamed it because I want to access it via instead of This hadn't been a problem previously. I literally have not touched anything besides updating calibre-web and switched letsencrypt to swag.
  9. I've only installed dockers from the unRAID gui. Is there a way to get this information for you? Should I check the logs? I'm probably using this command wrongly ... root@Tower:~# docker run calibre-web Unable to find image 'calibre-web:latest' locally docker: Error response from daemon: pull access denied for calibre-web, repository does not exist or may require 'docker login': denied: requested access to the resource is denied. See 'docker run --help'. root@Tower:~# docker run letsencrypt Unable to find image 'letsencrypt:latest' locally docker: Error response from daemon: pull access denied for letsencrypt, repository does not exist or may require 'docker login': denied: requested access to the resource is denied. See 'docker run --help'. Here's what I get when I do it from the GUI: calibre-web root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='calibre-web' --net='bridge' -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e 'DOCKER_MODS'='linuxserver/calibre-web:calibre' -e '-e'='DOCKER_MODS=linuxserver/calibre-web:calibre' -e 'PUID'='99' -e 'PGID'='100' -p '8083:8083/tcp' -v '/mnt/user/Books/Calibre TOWER/':'/books':'rw' -v '/mnt/user/appdata/calibre-web':'/config':'rw' 'linuxserver/calibre-web' c875805912b8f3698bfef2c25b0b300e4779df636bd4bee4edef344a133919e2 The command finished successfully! swag root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='letsencrypt' --net='bridge' --privileged=true -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e 'EMAIL'='' -e 'URL'='' -e 'SUBDOMAINS'='www' -e 'ONLY_SUBDOMAINS'='false' -e 'DHLEVEL'='4096' -e 'VALIDATION'='dns' -e 'DNSPLUGIN'='cloudflare' -e 'PUID'='99' -e 'PGID'='100' -p '81:80/tcp' -p '443:443/tcp' -v '/mnt/user/appdata/letsencrypt':'/config':'rw' 'linuxserver/swag' 1b027e357b6b3c41e398d9cd24578313cab117de4c96ddf33abb6d56d235db91 The command finished successfully!
  10. Yes I can access it via Sorry I thought this is a reverse proxy issue. If we're confirming this is a calibre-web issue I'll post over there. But re. "SWAG shouldn't be on bridge" — do I need to fix that anyway?
  11. Oh, I installed SWAG/letsencrypt using the unRAID interface and this was all default. Odd that this used to work until now? Can you advise what I should do? I'd hate to mess up my setup, everything has been working fine till Calibre-Web after I updated it. I did switch the letsencrypt repo to SWAG too. Should I follow the instructions here?
  12. They ought to be? This was running fine before and I haven't touched anything. Network type is Bridge, same as the others. I googled some commands to check network: root@Tower:~# docker inspect calibre-web -f "{{json .NetworkSettings.Networks }}" {"bridge":{"IPAMConfig":null,"Links":null,"Aliases":null,"NetworkID":"0659dbe7af4ace39b1e7c124edc8ff3d771db27688183525f1869ccf873aa2a4","EndpointID":"fc13b1021f58a201e0b0dc47c694c467d72dd435fdbf612e31abf3f9604e9786","Gateway":"","IPAddress":"","IPPrefixLen":16,"IPv6Gateway":"","GlobalIPv6Address":"","GlobalIPv6PrefixLen":0,"MacAddress":"02:42:ac:11:00:07","DriverOpts":null}} root@Tower:~# docker inspect letsencrypt -f "{{json .NetworkSettings.Networks }}" {"bridge":{"IPAMConfig":null,"Links":null,"Aliases":null,"NetworkID":"0659dbe7af4ace39b1e7c124edc8ff3d771db27688183525f1869ccf873aa2a4","EndpointID":"aaf360ebf00c5548d3bb902618242a5b9f38574769819b6cf41cf30c7e85b1b9","Gateway":"","IPAddress":"","IPPrefixLen":16,"IPv6Gateway":"","GlobalIPv6Address":"","GlobalIPv6PrefixLen":0,"MacAddress":"02:42:ac:11:00:05","DriverOpts":null}} Maybe there's something wrong with the calibre-web update? This is what I get from calibre-web's log, I noticed there're some warnings: mod-init] Attempting to run Docker Modification Logic [mod-init] Applying linuxserver/calibre-web:calibre files to container [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01-envfile: executing... [cont-init.d] 01-envfile: exited 0. [cont-init.d] 10-adduser: executing... ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by ------------------------------------- To support LSIO projects visit: ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-config: executing... [cont-init.d] 30-config: exited 0. [cont-init.d] 60-calibre-config: executing... Creating symlinks... Symlinking /app/calibre/ebook-device to /usr/bin/ebook-device Symlinking /app/calibre/ebook-meta to /usr/bin/ebook-meta Symlinking /app/calibre/ebook-convert to /usr/bin/ebook-convert Symlinking /app/calibre/ebook-polish to /usr/bin/ebook-polish Symlinking /app/calibre/markdown-calibre to /usr/bin/markdown-calibre Symlinking /app/calibre/web2disk to /usr/bin/web2disk Symlinking /app/calibre/calibre-server to /usr/bin/calibre-server Symlinking /app/calibre/lrf2lrs to /usr/bin/lrf2lrs Symlinking /app/calibre/lrs2lrf to /usr/bin/lrs2lrf Symlinking /app/calibre/calibre-debug to /usr/bin/calibre-debug Symlinking /app/calibre/calibredb to /usr/bin/calibredb Symlinking /app/calibre/calibre-parallel to /usr/bin/calibre-parallel Symlinking /app/calibre/calibre-customize to /usr/bin/calibre-customize Symlinking /app/calibre/fetch-ebook-metadata to /usr/bin/fetch-ebook-metadata Symlinking /app/calibre/calibre-smtp to /usr/bin/calibre-smtp Symlinking /app/calibre/calibre to /usr/bin/calibre Symlinking /app/calibre/lrfviewer to /usr/bin/lrfviewer Symlinking /app/calibre/ebook-viewer to /usr/bin/ebook-viewer Symlinking /app/calibre/ebook-edit to /usr/bin/ebook-edit Setting up command-line completion... Installing zsh completion to: /usr/share/zsh/vendor-completions/_calibre Failed to find directory to install bash completions, using default. Installing bash completion to: /usr/share/bash-completion/completions/ ____________________ WARNING ____________________ Setting up completion failed with error: __________________________________________________ Traceback (most recent call last): File "site-packages/calibre/", line 832, in setup_completion File "site-packages/calibre/", line 574, in write_completion File "site-packages/calibre/gui2/", line 16, in <module> ImportError: cannot import name 'QApplication' from 'PyQt5.Qt' (/app/calibre/lib/python3.8/site-packages/PyQt5/ Setting up desktop integration... ____________________ WARNING ____________________ Setting up desktop integration failed with error: __________________________________________________ Traceback (most recent call last): File "site-packages/calibre/", line 900, in setup_desktop_integration File "site-packages/calibre/", line 885, in install_icons File "site-packages/calibre/", line 875, in install_single_icon File "site-packages/calibre/", line 1219, in render_img ImportError: cannot import name 'QImage' from 'PyQt5.Qt' (/app/calibre/lib/python3.8/site-packages/PyQt5/ Creating un-installer: /usr/bin/calibre-uninstall There were 2 warnings * Setting up completion failed with error: * Setting up desktop integration failed with error: WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Get:1 bionic InRelease [242 kB] Get:2 bionic-updates InRelease [88.7 kB] Get:3 bionic-security InRelease [88.7 kB] Get:4 bionic/universe Sources [11.5 MB] Get:5 bionic/main Sources [1,063 kB] Get:6 bionic/restricted Sources [5,823 B] Get:7 bionic/multiverse Sources [216 kB] Get:8 bionic/universe amd64 Packages [11.3 MB] Get:9 bionic/restricted amd64 Packages [13.5 kB] Get:10 bionic/multiverse amd64 Packages [186 kB] Get:11 bionic/main amd64 Packages [1,344 kB] Get:12 bionic-updates/universe Sources [383 kB] Get:13 bionic-updates/multiverse Sources [7,929 B] Get:14 bionic-updates/main Sources [424 kB] Get:15 bionic-updates/restricted Sources [12.4 kB] Get:16 bionic-updates/restricted amd64 Packages [146 kB] Get:17 bionic-updates/main amd64 Packages [1,406 kB] Get:18 bionic-updates/universe amd64 Packages [1,434 kB] Get:19 bionic-updates/multiverse amd64 Packages [33.9 kB] Get:20 bionic-security/multiverse Sources [3,245 B] Get:21 bionic-security/restricted Sources [8,931 B] Get:22 bionic-security/universe Sources [227 kB] Get:23 bionic-security/main Sources [216 kB] Get:24 bionic-security/universe amd64 Packages [907 kB] Get:25 bionic-security/restricted amd64 Packages [126 kB] Get:26 bionic-security/main amd64 Packages [1,115 kB] Get:27 bionic-security/multiverse amd64 Packages [10.1 kB] Fetched 32.6 MB in 4s (7,797 kB/s) Reading package lists... Building dependency tree... Reading state information... 9 packages can be upgraded. Run 'apt list --upgradable' to see them. WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Reading package lists... Building dependency tree... Reading state information... The following additional packages will be installed: libdrm-amdgpu1 libdrm-common libdrm-intel1 libdrm-nouveau2 libdrm-radeon1 libdrm2 libedit2 libelf1 libgl1 libgl1-mesa-dri libglapi-mesa libglvnd0 libglx-mesa0 libglx0 libllvm10 libpciaccess0 libsensors4 libx11-xcb1 libxcb-dri2-0 libxcb-dri3-0 libxcb-glx0 libxcb-present0 libxcb-sync1 libxdamage1 libxfixes3 libxshmfence1 libxxf86vm1 Suggested packages: pciutils lm-sensors The following NEW packages will be installed: libdrm-amdgpu1 libdrm-common libdrm-intel1 libdrm-nouveau2 libdrm-radeon1 libdrm2 libedit2 libelf1 libgl1 libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa libglvnd0 libglx-mesa0 libglx0 libllvm10 libpciaccess0 libsensors4 libx11-xcb1 libxcb-dri2-0 libxcb-dri3-0 libxcb-glx0 libxcb-present0 libxcb-sync1 libxdamage1 libxfixes3 libxshmfence1 libxxf86vm1 0 upgraded, 28 newly installed, 0 to remove and 9 not upgraded. Need to get 25.5 MB of archives. After this operation, 327 MB of additional disk space will be used. Get:1 bionic/main amd64 libxxf86vm1 amd64 1:1.1.4-1 [10.6 kB] Get:2 bionic-updates/main amd64 libelf1 amd64 0.170-0.4ubuntu0.1 [44.8 kB] Get:3 bionic-updates/main amd64 libdrm-common all 2.4.101-2~18.04.1 [5,560 B] Get:4 bionic-updates/main amd64 libdrm2 amd64 2.4.101-2~18.04.1 [32.3 kB] Get:5 bionic/main amd64 libedit2 amd64 3.1-20170329-1 [76.9 kB] Get:6 bionic-updates/main amd64 libdrm-amdgpu1 amd64 2.4.101-2~18.04.1 [18.2 kB] Get:7 bionic/main amd64 libpciaccess0 amd64 0.14-1 [17.9 kB] Get:8 bionic-updates/main amd64 libdrm-intel1 amd64 2.4.101-2~18.04.1 [60.0 kB] Get:9 bionic-updates/main amd64 libdrm-nouveau2 amd64 2.4.101-2~18.04.1 [16.5 kB] Get:10 bionic-updates/main amd64 libdrm-radeon1 amd64 2.4.101-2~18.04.1 [21.7 kB] Get:11 bionic-updates/main amd64 libglapi-mesa amd64 20.0.8-0ubuntu1~18.04.1 [26.6 kB] Get:12 bionic-updates/main amd64 libllvm10 amd64 1:10.0.0-4ubuntu1~18.04.2 [15.4 MB] Get:13 bionic/main amd64 libsensors4 amd64 1:3.4.0-4 [28.8 kB] Get:14 bionic-updates/main amd64 libgl1-mesa-dri amd64 20.0.8-0ubuntu1~18.04.1 [9,333 kB] Get:15 bionic-updates/main amd64 libglvnd0 amd64 1.0.0-2ubuntu2.3 [47.0 kB] Get:16 bionic-updates/main amd64 libx11-xcb1 amd64 2:1.6.4-3ubuntu0.3 [9,628 B] Get:17 bionic-updates/main amd64 libxcb-dri2-0 amd64 1.13-2~ubuntu18.04 [6,920 B] Get:18 bionic-updates/main amd64 libxcb-dri3-0 amd64 1.13-2~ubuntu18.04 [6,568 B] Get:19 bionic-updates/main amd64 libxcb-glx0 amd64 1.13-2~ubuntu18.04 [22.1 kB] Get:20 bionic-updates/main amd64 libxcb-present0 amd64 1.13-2~ubuntu18.04 [5,552 B] Get:21 bionic-updates/main amd64 libxcb-sync1 amd64 1.13-2~ubuntu18.04 [8,808 B] Get:22 bionic/main amd64 libxdamage1 amd64 1:1.1.4-3 [6,934 B] Get:23 bionic/main amd64 libxfixes3 amd64 1:5.0.3-1 [10.8 kB] Get:24 bionic/main amd64 libxshmfence1 amd64 1.3-1 [5,028 B] Get:25 bionic-updates/main amd64 libglx-mesa0 amd64 20.0.8-0ubuntu1~18.04.1 [139 kB] Get:26 bionic-updates/main amd64 libglx0 amd64 1.0.0-2ubuntu2.3 [28.1 kB] Get:27 bionic-updates/main amd64 libgl1 amd64 1.0.0-2ubuntu2.3 [86.2 kB] Get:28 bionic-updates/main amd64 libgl1-mesa-glx amd64 20.0.8-0ubuntu1~18.04.1 [5,532 B] debconf: unable to initialize frontend: Dialog debconf: (No usable dialog-like program is installed, so the dialog based frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/ line 76, <> line 28.) debconf: falling back to frontend: Readline debconf: unable to initialize frontend: Readline debconf: (Can't locate Term/ in @INC (you may need to install the Term::ReadLine module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.26.1 /usr/local/share/perl/5.26.1 /usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/perl5/Debconf/FrontEnd/ line 7, <> line 28.) debconf: falling back to frontend: Teletype dpkg-preconfigure: unable to re-open stdin: Fetched 25.5 MB in 3s (8,716 kB/s) Selecting previously unselected package libxxf86vm1:amd64. Preparing to unpack .../00-libxxf86vm1_1%3a1.1.4-1_amd64.deb ... Unpacking libxxf86vm1:amd64 (1:1.1.4-1) ... Selecting previously unselected package libelf1:amd64. Preparing to unpack .../01-libelf1_0.170-0.4ubuntu0.1_amd64.deb ... Unpacking libelf1:amd64 (0.170-0.4ubuntu0.1) ... Selecting previously unselected package libdrm-common. Preparing to unpack .../02-libdrm-common_2.4.101-2~18.04.1_all.deb ... Unpacking libdrm-common (2.4.101-2~18.04.1) ... Selecting previously unselected package libdrm2:amd64. Preparing to unpack .../03-libdrm2_2.4.101-2~18.04.1_amd64.deb ... Unpacking libdrm2:amd64 (2.4.101-2~18.04.1) ... Selecting previously unselected package libedit2:amd64. Preparing to unpack .../04-libedit2_3.1-20170329-1_amd64.deb ... Unpacking libedit2:amd64 (3.1-20170329-1) ... Selecting previously unselected package libdrm-amdgpu1:amd64. Preparing to unpack .../05-libdrm-amdgpu1_2.4.101-2~18.04.1_amd64.deb ... Unpacking libdrm-amdgpu1:amd64 (2.4.101-2~18.04.1) ... Selecting previously unselected package libpciaccess0:amd64. Preparing to unpack .../06-libpciaccess0_0.14-1_amd64.deb ... Unpacking libpciaccess0:amd64 (0.14-1) ... Selecting previously unselected package libdrm-intel1:amd64. Preparing to unpack .../07-libdrm-intel1_2.4.101-2~18.04.1_amd64.deb ... Unpacking libdrm-intel1:amd64 (2.4.101-2~18.04.1) ... Selecting previously unselected package libdrm-nouveau2:amd64. Preparing to unpack .../08-libdrm-nouveau2_2.4.101-2~18.04.1_amd64.deb ... Unpacking libdrm-nouveau2:amd64 (2.4.101-2~18.04.1) ... Selecting previously unselected package libdrm-radeon1:amd64. Preparing to unpack .../09-libdrm-radeon1_2.4.101-2~18.04.1_amd64.deb ... Unpacking libdrm-radeon1:amd64 (2.4.101-2~18.04.1) ... Selecting previously unselected package libglapi-mesa:amd64. Preparing to unpack .../10-libglapi-mesa_20.0.8-0ubuntu1~18.04.1_amd64.deb ... Unpacking libglapi-mesa:amd64 (20.0.8-0ubuntu1~18.04.1) ... Selecting previously unselected package libllvm10:amd64. Preparing to unpack .../11-libllvm10_1%3a10.0.0-4ubuntu1~18.04.2_amd64.deb ... Unpacking libllvm10:amd64 (1:10.0.0-4ubuntu1~18.04.2) ... Selecting previously unselected package libsensors4:amd64. Preparing to unpack .../12-libsensors4_1%3a3.4.0-4_amd64.deb ... Unpacking libsensors4:amd64 (1:3.4.0-4) ... Selecting previously unselected package libgl1-mesa-dri:amd64. Preparing to unpack .../13-libgl1-mesa-dri_20.0.8-0ubuntu1~18.04.1_amd64.deb ... Unpacking libgl1-mesa-dri:amd64 (20.0.8-0ubuntu1~18.04.1) ... Selecting previously unselected package libglvnd0:amd64. Preparing to unpack .../14-libglvnd0_1.0.0-2ubuntu2.3_amd64.deb ... Unpacking libglvnd0:amd64 (1.0.0-2ubuntu2.3) ... Selecting previously unselected package libx11-xcb1:amd64. Preparing to unpack .../15-libx11-xcb1_2%3a1.6.4-3ubuntu0.3_amd64.deb ... Unpacking libx11-xcb1:amd64 (2:1.6.4-3ubuntu0.3) ... Selecting previously unselected package libxcb-dri2-0:amd64. Preparing to unpack .../16-libxcb-dri2-0_1.13-2~ubuntu18.04_amd64.deb ... Unpacking libxcb-dri2-0:amd64 (1.13-2~ubuntu18.04) ... Selecting previously unselected package libxcb-dri3-0:amd64. Preparing to unpack .../17-libxcb-dri3-0_1.13-2~ubuntu18.04_amd64.deb ... Unpacking libxcb-dri3-0:amd64 (1.13-2~ubuntu18.04) ... Selecting previously unselected package libxcb-glx0:amd64. Preparing to unpack .../18-libxcb-glx0_1.13-2~ubuntu18.04_amd64.deb ... Unpacking libxcb-glx0:amd64 (1.13-2~ubuntu18.04) ... Selecting previously unselected package libxcb-present0:amd64. Preparing to unpack .../19-libxcb-present0_1.13-2~ubuntu18.04_amd64.deb ... Unpacking libxcb-present0:amd64 (1.13-2~ubuntu18.04) ... Selecting previously unselected package libxcb-sync1:amd64. Preparing to unpack .../20-libxcb-sync1_1.13-2~ubuntu18.04_amd64.deb ... Unpacking libxcb-sync1:amd64 (1.13-2~ubuntu18.04) ... Selecting previously unselected package libxdamage1:amd64. Preparing to unpack .../21-libxdamage1_1%3a1.1.4-3_amd64.deb ... Unpacking libxdamage1:amd64 (1:1.1.4-3) ... Selecting previously unselected package libxfixes3:amd64. Preparing to unpack .../22-libxfixes3_1%3a5.0.3-1_amd64.deb ... Unpacking libxfixes3:amd64 (1:5.0.3-1) ... Selecting previously unselected package libxshmfence1:amd64. Preparing to unpack .../23-libxshmfence1_1.3-1_amd64.deb ... Unpacking libxshmfence1:amd64 (1.3-1) ... Selecting previously unselected package libglx-mesa0:amd64. Preparing to unpack .../24-libglx-mesa0_20.0.8-0ubuntu1~18.04.1_amd64.deb ... Unpacking libglx-mesa0:amd64 (20.0.8-0ubuntu1~18.04.1) ... Selecting previously unselected package libglx0:amd64. Preparing to unpack .../25-libglx0_1.0.0-2ubuntu2.3_amd64.deb ... Unpacking libglx0:amd64 (1.0.0-2ubuntu2.3) ... Selecting previously unselected package libgl1:amd64. Preparing to unpack .../26-libgl1_1.0.0-2ubuntu2.3_amd64.deb ... Unpacking libgl1:amd64 (1.0.0-2ubuntu2.3) ... Selecting previously unselected package libgl1-mesa-glx:amd64. Preparing to unpack .../27-libgl1-mesa-glx_20.0.8-0ubuntu1~18.04.1_amd64.deb ... Unpacking libgl1-mesa-glx:amd64 (20.0.8-0ubuntu1~18.04.1) ... Setting up libedit2:amd64 (3.1-20170329-1) ... Setting up libxcb-present0:amd64 (1.13-2~ubuntu18.04) ... Setting up libglvnd0:amd64 (1.0.0-2ubuntu2.3) ... Setting up libxcb-dri2-0:amd64 (1.13-2~ubuntu18.04) ... Setting up libxcb-dri3-0:amd64 (1.13-2~ubuntu18.04) ... Setting up libxcb-glx0:amd64 (1.13-2~ubuntu18.04) ... Setting up libllvm10:amd64 (1:10.0.0-4ubuntu1~18.04.2) ... Setting up libxdamage1:amd64 (1:1.1.4-3) ... Setting up libxfixes3:amd64 (1:5.0.3-1) ... Setting up libelf1:amd64 (0.170-0.4ubuntu0.1) ... Setting up libxshmfence1:amd64 (1.3-1) ... Setting up libglapi-mesa:amd64 (20.0.8-0ubuntu1~18.04.1) ... Setting up libdrm-common (2.4.101-2~18.04.1) ... Setting up libxcb-sync1:amd64 (1.13-2~ubuntu18.04) ... Setting up libx11-xcb1:amd64 (2:1.6.4-3ubuntu0.3) ... Setting up libpciaccess0:amd64 (0.14-1) ... Setting up libsensors4:amd64 (1:3.4.0-4) ... Setting up libxxf86vm1:amd64 (1:1.1.4-1) ... Setting up libdrm2:amd64 (2.4.101-2~18.04.1) ... Setting up libdrm-intel1:amd64 (2.4.101-2~18.04.1) ... Setting up libdrm-radeon1:amd64 (2.4.101-2~18.04.1) ... Setting up libdrm-nouveau2:amd64 (2.4.101-2~18.04.1) ... Setting up libdrm-amdgpu1:amd64 (2.4.101-2~18.04.1) ... Setting up libgl1-mesa-dri:amd64 (20.0.8-0ubuntu1~18.04.1) ... Setting up libglx-mesa0:amd64 (20.0.8-0ubuntu1~18.04.1) ... Setting up libglx0:amd64 (1.0.0-2ubuntu2.3) ... Setting up libgl1:amd64 (1.0.0-2ubuntu2.3) ... Setting up libgl1-mesa-glx:amd64 (20.0.8-0ubuntu1~18.04.1) ... Processing triggers for libc-bin (2.27-3ubuntu1.2) ... [cont-init.d] 60-calibre-config: exited 0. [cont-init.d] 99-custom-scripts: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-scripts: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done.
  13. Thanks for suggesting that, I never knew there's a sample in there. But I'm still getting the same 502 Bad Gateway error. I'm beginning to suspect it might be Calibre-Web. Someone on Reddit is also getting the same error when his/her reverse proxy worked fine before. This is what I just tried based on the conf included in swag: location /calibre { return 301 $scheme://$host/calibre/; } location ^~ /calibre/ { # enable the next two lines for http auth auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; # enable the next two lines for ldap auth, also customize and enable ldap.conf in the default conf #auth_request /auth; #error_page 401 =200 /ldaplogin; # enable for Authelia, also enable authelia-server.conf in the default site config #include /config/nginx/authelia-location.conf; resolver valid=30s; set $upstream_app calibre; set $upstream_port 8083; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; proxy_set_header Host $http_host; proxy_set_header X-Scheme $scheme; proxy_set_header X-Script-Name /calibre; }
  14. Been a while, the new Linuxserver logo looks great!! Can someone have a look at this reverse proxy for calibre-web (I think I got it from Calibre-Web's github)? It used to work and now I'm getting a 502 Bad Gateway. #Config for Calibre Web location ^~ /calibre/ { auth_basic "Restricted"; auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; proxy_pass; proxy_set_header Host $http_host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Scheme $scheme; proxy_set_header X-Script-Name /calibre; }
  15. Hi all, sorry I have a really dumb question: Am I suppose to be able to read an ebook with the Calibre-Web interface? I've read about the function but I'm not seeing it in the UI after clicking on a book. I see: Mark as read, Edit metadata, Download, and Send to Kindle. I also tried clicking and double-clicking on the book cover. And I've tried this with Firefox and Safari.
  16. I might've ascertained the culprit in ident.cfg as I compared the clean /config with my old /config to copy settings over: # Generated settings: NAME="Tower" timeZone="America/Los_Angeles" COMMENT="Media server" SECURITY="user" WORKGROUP="WORKGROUP" DOMAIN="" DOMAIN_SHORT="" hideDotFiles="no" localMaster="yes" enableFruit="no" USE_NTP="yes" NTP_SERVER1="" NTP_SERVER2="" NTP_SERVER3="" NTP_SERVER4="" DOMAIN_LOGIN="Administrator" DOMAIN_PASSWD="" SYS_MODEL="Custom" SYS_ARRAY_SLOTS="6" SYS_CACHE_SLOTS="1" USE_SSL="no" PORT="8099" PORTSSL="443" LOCAL_TLD="localj" BIND_MGT="no" USE_TELNET="no" PORTTELNET="23" USE_SSH="no" PORTSSH="22" START_PAGE="Main" Default ident.cfg has PORT="80" and USE_TELNET and USE_SSH values of "yes" while my old ident.cfg above had port 8099 and "no" which is weird since I never touched those.
  17. @trurl I did a fresh install, copied my old config over, and still couldn't access the web ui. However, I tried a fresh CLEAN install and can get into the web ui.
  18. I checked the flash drive using Disk Utility and it gave me a exit code of 0 which suggests no errors were found. Backed up the flash drive and will proceed with a flash install. I had a look at the super.dat file in /config and I think it's corrupted. Noticed a super.old file dated Dec 10 which I think is when all this started. Does that file look normal? super.dat super.old
  19. Err no. I was anxious to get this up and running again.
  20. Ah I see your point now, sorry for being so slow. You think there's a chance the flash drive is failing? Maybe I need to get a new one while I'm t it.
  21. Not yet. I jumped the gun and started the array hoping this weird network issue would resolve itself but it didn't. It's now 18% into the parity sync/data rebuild. I've looked through the Shares and have tried watching videos via Kodi, everything else seems to be running normally. When the parity sync is finished I'll do a nice shutdown and do the flash backup etc as you suggest. Even so, that's just kinda starting from scratch and restoring the config though. I still don't know nor understand why I suddenly can't access the web gui and SSH.
  22. Ok ... but that's the least of my concerns right now 😕
  23. Ok, something new: I've not been able to access nor tower.local in the web browser. Can ping, can't SSH. But I have SABnzbd running on unRAID and I can access it via and tower.local:8080/sabnzbd/ in my web browser. Trying directs me to Nginx that I have running as a docker. If I tried explicitly, I get the same unable to connect problem as I thought maybe this is something wrong with the ISP-provided router ARRIS BGW210 (AT&T Fiber). But I had also plugged the unRAID box into my old router, hard-wired my laptop to the router, and also can't access the web gui. So I don't think it's a router issue. Looks like unRAID isn't responding to port 80 and the port 22 that SSH uses. Could something have happened within unRAID to disable those access? How can I check that? Doesn't explain how it was working fine previously and the missing array configuration.
  24. Nope, started the array, got an email notification for "parity sync / data rebuild started" but I STILL CAN'T ACCESS the IP and tower.local. With the array started, I can access all the Shares. I just received an email notification that Template URLs are missing: **** Template URL for docker application EmbyServer is missing. **** **** Template URL for docker application Rclone is missing. **** **** Template URL for docker application speedtest is missing. **** So what's going on??
  25. Great, so that solves that. I'm gonna start up the array and hope everything goes back to normal ...