[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)


Recommended Posts

How I switched to swag that seemed to work:

  1. Create an folder named swag in appdata
  2. Copy all content from letsencrypt folder to swag
    (could also rename it but I did not want to change letscencrypt stuff before I knew swag worked fine)
  3. Install swag template and change settings
  4. Stop letsencrypt docker and start swag
  5. Change letsencrypt to swag in nextcloud config
  6. Done.
Link to comment
On 9/24/2020 at 1:45 PM, saarg said:

You updated them or deleted them and let the container recreate them on restart?

 

Which files in which container did you update?

I have created everything new today, SWAG, Nextcloud, MariaDB and the warning remains. Should be easy to reproduce. I have the add_header line above the line where ssl.conf is included like its suggested in the readme. To not have it twice I disabled the add_header line inside the nextcloud container, message is there anyway though, disabled or not. Any other Ideas?

Link to comment
59 minutes ago, DockX said:

I have created everything new today, SWAG, Nextcloud, MariaDB and the warning remains. Should be easy to reproduce. I have the add_header line above the line where ssl.conf is included like its suggested in the readme. To not have it twice I disabled the add_header line inside the nextcloud container, message is there anyway though, disabled or not. Any other Ideas?

 

Not sure what your issue is, as I don't see it here.

Not sure what is in my cpnfigs, but on mobile arm so can't check until later today.

Link to comment
20 minutes ago, saarg said:

 

Not sure what your issue is, as I don't see it here.

Not sure what is in my cpnfigs, but on mobile arm so can't check until later today.

The issue is, that you always get the "the “ X - Robots - Tag ” HTTP header is not configured to equal to “none” warning, when you configure your swag with "none, noindex, nofollow, nosnippet, noarchive". When you have more than just "none" the warning appears, and only "none" is not enough for all crawlers.

Link to comment
1 hour ago, DockX said:

The issue is, that you always get the "the “ X - Robots - Tag ” HTTP header is not configured to equal to “none” warning, when you configure your swag with "none, noindex, nofollow, nosnippet, noarchive". When you have more than just "none" the warning appears, and only "none" is not enough for all crawlers.

Yes I know what the issue is, but not the solution.

Link to comment

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              http://192.168.1.252:8083;
        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;
    }

 

Edited by vurt
Link to comment
32 minutes ago, vurt said:

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              http://192.168.1.252:8083;
        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;
    }

 

Why not use the proxy conf included in swag?

Link to comment
14 minutes ago, saarg said:

Why not use the proxy conf included in swag?

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 192.168.1.252 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;
}

 

Link to comment

Today I got a info from "Fix Common Problems" the container "letsencrypt" is deprecated. So far so good, I had already read a couple weeks ago that you guys have to switch the name for the container, but I never changed my setting until today.

 

What I did so far:

1. stop the letsencrypt container

2. backup the config folder in appdata (copied to new folder called swag)

3. edit the old "letsencrypt" container

4. changed the name to swag

5. switch to "linuxserver/swag" repo

6. adjusted the config path to the new folder

7. starting the swag container

8. adjusting "trusted_proxies" in the nextcloud config.php in /appdata/nextcloud/www/nextcloud/config to swag

 

Did I miss something?

Link to comment
9 hours ago, vurt said:

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 192.168.1.252 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;
}

 

502 means swag can't connect to the container. Are they in the same docker network?

Link to comment
3 hours ago, bastl said:

Today I got a info from "Fix Common Problems" the container "letsencrypt" is deprecated. So far so good, I had already read a couple weeks ago that you guys have to switch the name for the container, but I never changed my setting until today.

 

What I did so far:

1. stop the letsencrypt container

2. backup the config folder in appdata (copied to new folder called swag)

3. edit the old "letsencrypt" container

4. changed the name to swag

5. switch to "linuxserver/swag" repo

6. adjusted the config path to the new folder

7. starting the swag container

8. adjusting "trusted_proxies" in the nextcloud config.php in /appdata/nextcloud/www/nextcloud/config to swag

 

Did I miss something?

 

I did almost the same, started by just changing name and repository, and then just renaming the app folder to swag

Everything seem to work but I can see differences between a new swag XML install and the old install

Example I have this in my "updated one" from the old one:

image.thumb.png.2555fb700da03c760de891ef6c7113d0.png

Which is from the old one, and I still have the old icon?

But everything works

 

Oh and I did apply the fix after running "Fix commen problems" for some config path.... (No errors anymore)

 

 

 

Link to comment
11 minutes ago, casperse said:

Which is from the old one, and I still have the old icon?

Same for me. I had 2048 already set in my old config and as shown in your screenshot it's the default value. Does the new SWAG template have a different value?

The icon for me also doesn't changed to the new one. Not a big deal.

Link to comment
8 minutes ago, DockX said:

Since you both also use nextcloud, how did you configure the X - Robots - Tag ? Do you have an entry for it in SWAG?

I have it set to the below in the default file of nextcloud. Which is the default value.

Quote

add_header X-Robots-Tag none;

That is the only place I have it.

Link to comment
5 hours ago, saarg said:

502 means swag can't connect to the container. Are they in the same docker network?

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":"172.17.0.1","IPAddress":"172.17.0.7","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":"172.17.0.1","IPAddress":"172.17.0.5","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 linuxserver.io
-------------------------------------

To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
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/linux.py", line 832, in setup_completion
File "site-packages/calibre/linux.py", line 574, in write_completion
File "site-packages/calibre/gui2/__init__.py", line 16, in <module>
ImportError: cannot import name 'QApplication' from 'PyQt5.Qt' (/app/calibre/lib/python3.8/site-packages/PyQt5/Qt.abi3.so)

Setting up desktop integration...

____________________ WARNING ____________________
Setting up desktop integration failed with error:
__________________________________________________


Traceback (most recent call last):
File "site-packages/calibre/linux.py", line 900, in setup_desktop_integration
File "site-packages/calibre/linux.py", line 885, in install_icons
File "site-packages/calibre/linux.py", line 875, in install_single_icon
File "site-packages/calibre/linux.py", line 1219, in render_img
ImportError: cannot import name 'QImage' from 'PyQt5.Qt' (/app/calibre/lib/python3.8/site-packages/PyQt5/Qt.abi3.so)

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 http://archive.ubuntu.com/ubuntu bionic InRelease [242 kB]
Get:2 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
Get:3 http://archive.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
Get:4 http://archive.ubuntu.com/ubuntu bionic/universe Sources [11.5 MB]
Get:5 http://archive.ubuntu.com/ubuntu bionic/main Sources [1,063 kB]
Get:6 http://archive.ubuntu.com/ubuntu bionic/restricted Sources [5,823 B]
Get:7 http://archive.ubuntu.com/ubuntu bionic/multiverse Sources [216 kB]
Get:8 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages [11.3 MB]
Get:9 http://archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages [13.5 kB]
Get:10 http://archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages [186 kB]
Get:11 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages [1,344 kB]
Get:12 http://archive.ubuntu.com/ubuntu bionic-updates/universe Sources [383 kB]
Get:13 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse Sources [7,929 B]
Get:14 http://archive.ubuntu.com/ubuntu bionic-updates/main Sources [424 kB]
Get:15 http://archive.ubuntu.com/ubuntu bionic-updates/restricted Sources [12.4 kB]
Get:16 http://archive.ubuntu.com/ubuntu bionic-updates/restricted amd64 Packages [146 kB]
Get:17 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [1,406 kB]
Get:18 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [1,434 kB]
Get:19 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 Packages [33.9 kB]
Get:20 http://archive.ubuntu.com/ubuntu bionic-security/multiverse Sources [3,245 B]
Get:21 http://archive.ubuntu.com/ubuntu bionic-security/restricted Sources [8,931 B]
Get:22 http://archive.ubuntu.com/ubuntu bionic-security/universe Sources [227 kB]
Get:23 http://archive.ubuntu.com/ubuntu bionic-security/main Sources [216 kB]
Get:24 http://archive.ubuntu.com/ubuntu bionic-security/universe amd64 Packages [907 kB]
Get:25 http://archive.ubuntu.com/ubuntu bionic-security/restricted amd64 Packages [126 kB]
Get:26 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages [1,115 kB]
Get:27 http://archive.ubuntu.com/ubuntu 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 http://archive.ubuntu.com/ubuntu bionic/main amd64 libxxf86vm1 amd64 1:1.1.4-1 [10.6 kB]
Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libelf1 amd64 0.170-0.4ubuntu0.1 [44.8 kB]
Get:3 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libdrm-common all 2.4.101-2~18.04.1 [5,560 B]
Get:4 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libdrm2 amd64 2.4.101-2~18.04.1 [32.3 kB]
Get:5 http://archive.ubuntu.com/ubuntu bionic/main amd64 libedit2 amd64 3.1-20170329-1 [76.9 kB]
Get:6 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libdrm-amdgpu1 amd64 2.4.101-2~18.04.1 [18.2 kB]
Get:7 http://archive.ubuntu.com/ubuntu bionic/main amd64 libpciaccess0 amd64 0.14-1 [17.9 kB]
Get:8 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libdrm-intel1 amd64 2.4.101-2~18.04.1 [60.0 kB]
Get:9 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libdrm-nouveau2 amd64 2.4.101-2~18.04.1 [16.5 kB]
Get:10 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libdrm-radeon1 amd64 2.4.101-2~18.04.1 [21.7 kB]
Get:11 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libglapi-mesa amd64 20.0.8-0ubuntu1~18.04.1 [26.6 kB]
Get:12 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libllvm10 amd64 1:10.0.0-4ubuntu1~18.04.2 [15.4 MB]
Get:13 http://archive.ubuntu.com/ubuntu bionic/main amd64 libsensors4 amd64 1:3.4.0-4 [28.8 kB]
Get:14 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libgl1-mesa-dri amd64 20.0.8-0ubuntu1~18.04.1 [9,333 kB]
Get:15 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libglvnd0 amd64 1.0.0-2ubuntu2.3 [47.0 kB]
Get:16 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libx11-xcb1 amd64 2:1.6.4-3ubuntu0.3 [9,628 B]
Get:17 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libxcb-dri2-0 amd64 1.13-2~ubuntu18.04 [6,920 B]
Get:18 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libxcb-dri3-0 amd64 1.13-2~ubuntu18.04 [6,568 B]
Get:19 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libxcb-glx0 amd64 1.13-2~ubuntu18.04 [22.1 kB]
Get:20 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libxcb-present0 amd64 1.13-2~ubuntu18.04 [5,552 B]
Get:21 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libxcb-sync1 amd64 1.13-2~ubuntu18.04 [8,808 B]
Get:22 http://archive.ubuntu.com/ubuntu bionic/main amd64 libxdamage1 amd64 1:1.1.4-3 [6,934 B]
Get:23 http://archive.ubuntu.com/ubuntu bionic/main amd64 libxfixes3 amd64 1:5.0.3-1 [10.8 kB]
Get:24 http://archive.ubuntu.com/ubuntu bionic/main amd64 libxshmfence1 amd64 1.3-1 [5,028 B]
Get:25 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libglx-mesa0 amd64 20.0.8-0ubuntu1~18.04.1 [139 kB]
Get:26 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libglx0 amd64 1.0.0-2ubuntu2.3 [28.1 kB]
Get:27 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libgl1 amd64 1.0.0-2ubuntu2.3 [86.2 kB]
Get:28 http://archive.ubuntu.com/ubuntu 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/Dialog.pm line 76, <> line 28.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (Can't locate Term/ReadLine.pm 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/Readline.pm 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.

 

Edited by vurt
Link to comment
3 hours ago, vurt said:

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":"172.17.0.1","IPAddress":"172.17.0.7","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":"172.17.0.1","IPAddress":"172.17.0.5","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 linuxserver.io
-------------------------------------

To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
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/linux.py", line 832, in setup_completion
File "site-packages/calibre/linux.py", line 574, in write_completion
File "site-packages/calibre/gui2/__init__.py", line 16, in <module>
ImportError: cannot import name 'QApplication' from 'PyQt5.Qt' (/app/calibre/lib/python3.8/site-packages/PyQt5/Qt.abi3.so)

Setting up desktop integration...

____________________ WARNING ____________________
Setting up desktop integration failed with error:
__________________________________________________


Traceback (most recent call last):
File "site-packages/calibre/linux.py", line 900, in setup_desktop_integration
File "site-packages/calibre/linux.py", line 885, in install_icons
File "site-packages/calibre/linux.py", line 875, in install_single_icon
File "site-packages/calibre/linux.py", line 1219, in render_img
ImportError: cannot import name 'QImage' from 'PyQt5.Qt' (/app/calibre/lib/python3.8/site-packages/PyQt5/Qt.abi3.so)

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 http://archive.ubuntu.com/ubuntu bionic InRelease [242 kB]
Get:2 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
Get:3 http://archive.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
Get:4 http://archive.ubuntu.com/ubuntu bionic/universe Sources [11.5 MB]
Get:5 http://archive.ubuntu.com/ubuntu bionic/main Sources [1,063 kB]
Get:6 http://archive.ubuntu.com/ubuntu bionic/restricted Sources [5,823 B]
Get:7 http://archive.ubuntu.com/ubuntu bionic/multiverse Sources [216 kB]
Get:8 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages [11.3 MB]
Get:9 http://archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages [13.5 kB]
Get:10 http://archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages [186 kB]
Get:11 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages [1,344 kB]
Get:12 http://archive.ubuntu.com/ubuntu bionic-updates/universe Sources [383 kB]
Get:13 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse Sources [7,929 B]
Get:14 http://archive.ubuntu.com/ubuntu bionic-updates/main Sources [424 kB]
Get:15 http://archive.ubuntu.com/ubuntu bionic-updates/restricted Sources [12.4 kB]
Get:16 http://archive.ubuntu.com/ubuntu bionic-updates/restricted amd64 Packages [146 kB]
Get:17 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [1,406 kB]
Get:18 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [1,434 kB]
Get:19 http://archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 Packages [33.9 kB]
Get:20 http://archive.ubuntu.com/ubuntu bionic-security/multiverse Sources [3,245 B]
Get:21 http://archive.ubuntu.com/ubuntu bionic-security/restricted Sources [8,931 B]
Get:22 http://archive.ubuntu.com/ubuntu bionic-security/universe Sources [227 kB]
Get:23 http://archive.ubuntu.com/ubuntu bionic-security/main Sources [216 kB]
Get:24 http://archive.ubuntu.com/ubuntu bionic-security/universe amd64 Packages [907 kB]
Get:25 http://archive.ubuntu.com/ubuntu bionic-security/restricted amd64 Packages [126 kB]
Get:26 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages [1,115 kB]
Get:27 http://archive.ubuntu.com/ubuntu 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 http://archive.ubuntu.com/ubuntu bionic/main amd64 libxxf86vm1 amd64 1:1.1.4-1 [10.6 kB]
Get:2 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libelf1 amd64 0.170-0.4ubuntu0.1 [44.8 kB]
Get:3 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libdrm-common all 2.4.101-2~18.04.1 [5,560 B]
Get:4 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libdrm2 amd64 2.4.101-2~18.04.1 [32.3 kB]
Get:5 http://archive.ubuntu.com/ubuntu bionic/main amd64 libedit2 amd64 3.1-20170329-1 [76.9 kB]
Get:6 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libdrm-amdgpu1 amd64 2.4.101-2~18.04.1 [18.2 kB]
Get:7 http://archive.ubuntu.com/ubuntu bionic/main amd64 libpciaccess0 amd64 0.14-1 [17.9 kB]
Get:8 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libdrm-intel1 amd64 2.4.101-2~18.04.1 [60.0 kB]
Get:9 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libdrm-nouveau2 amd64 2.4.101-2~18.04.1 [16.5 kB]
Get:10 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libdrm-radeon1 amd64 2.4.101-2~18.04.1 [21.7 kB]
Get:11 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libglapi-mesa amd64 20.0.8-0ubuntu1~18.04.1 [26.6 kB]
Get:12 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libllvm10 amd64 1:10.0.0-4ubuntu1~18.04.2 [15.4 MB]
Get:13 http://archive.ubuntu.com/ubuntu bionic/main amd64 libsensors4 amd64 1:3.4.0-4 [28.8 kB]
Get:14 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libgl1-mesa-dri amd64 20.0.8-0ubuntu1~18.04.1 [9,333 kB]
Get:15 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libglvnd0 amd64 1.0.0-2ubuntu2.3 [47.0 kB]
Get:16 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libx11-xcb1 amd64 2:1.6.4-3ubuntu0.3 [9,628 B]
Get:17 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libxcb-dri2-0 amd64 1.13-2~ubuntu18.04 [6,920 B]
Get:18 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libxcb-dri3-0 amd64 1.13-2~ubuntu18.04 [6,568 B]
Get:19 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libxcb-glx0 amd64 1.13-2~ubuntu18.04 [22.1 kB]
Get:20 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libxcb-present0 amd64 1.13-2~ubuntu18.04 [5,552 B]
Get:21 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libxcb-sync1 amd64 1.13-2~ubuntu18.04 [8,808 B]
Get:22 http://archive.ubuntu.com/ubuntu bionic/main amd64 libxdamage1 amd64 1:1.1.4-3 [6,934 B]
Get:23 http://archive.ubuntu.com/ubuntu bionic/main amd64 libxfixes3 amd64 1:5.0.3-1 [10.8 kB]
Get:24 http://archive.ubuntu.com/ubuntu bionic/main amd64 libxshmfence1 amd64 1.3-1 [5,028 B]
Get:25 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libglx-mesa0 amd64 20.0.8-0ubuntu1~18.04.1 [139 kB]
Get:26 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libglx0 amd64 1.0.0-2ubuntu2.3 [28.1 kB]
Get:27 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 libgl1 amd64 1.0.0-2ubuntu2.3 [86.2 kB]
Get:28 http://archive.ubuntu.com/ubuntu 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/Dialog.pm line 76, <> line 28.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (Can't locate Term/ReadLine.pm 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/Readline.pm 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.

 

SWAG shouldn't be on bridge, it should be on a network just for your containers that you're procuring.

Link to comment
48 minutes ago, bigmak said:

SWAG shouldn't be on bridge, it should be on a network just for your containers that you're procuring.

Oh, I installed SWAG/letsencrypt using the unRAID interface and this was all default.

 

1877877425_ScreenShot2020-09-27at12_16_22PM.thumb.png.b6a973e388fc5ea953b6701622d2b867.png

 

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?

 

Quote

If you are using unraid, create a custom network in command line via docker network create [networkname], then go to docker service settings (under advanced) and set the option Preserve user defined networks: to Yes. Then in each container setting, including the LetsEncrypt container, in the network type dropdown, select Custom : [networkname]. This is a necessary step as the bridge network that unraid uses by default does not allow container to container communication.

 

Edited by vurt
Link to comment
2 minutes ago, vurt said:

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?

 

 

Did you check if you can access calibre-web locally? If that doesn't work, this issue should be in the calibre-web thread instead.

Link to comment
Just now, saarg said:

Did you check if you can access calibre-web locally? If that doesn't work, this issue should be in the calibre-web thread instead.

Yes I can access it via http://192.168.1.252:8083/.

 

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?

Link to comment
2 minutes ago, vurt said:

Yes I can access it via http://192.168.1.252:8083/.

 

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?

Then it's a reverse proxy issue.

 

Post the docker run command of bothe swag and calibre-web.

 

You need to use a custom docker network bridge if you want to take advantage of using the container names for communication.

 

 

Link to comment
23 minutes ago, saarg said:

Then it's a reverse proxy issue.

 

Post the docker run command of bothe swag and calibre-web.

 

You need to use a custom docker network bridge if you want to take advantage of using the container names for communication.

 

 

 

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'='[email protected]' -e 'URL'='domain.net' -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!

 

Edited by vurt
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.