bigmak
-
Posts
22 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by bigmak
-
-
Note this is showing up on multiple browsers (Chrome/Firefox/Edge) and multiple devices (Windows/Android). It is also happening when accessing the server from both the IP and the hostname. I've also verified that the server can reach the internet (Terminal -> ping).
-
Hello all. Shut down my Unraid server in preparation for Hurricane Ian and then it would not reboot. Examined logs, saw kernel panics, figured out USB drive was on the fritz. Was able to get the /config folder off prior to it dying.
The issue is with my new USB drive, the replace the registration key button does not show up. I tried 6.9.2 and 6.11.0 with the same issue; just says upcTrigger.default. Any tips or help?
-
I'm having trouble getting this container to use anything other than port 5005. Any tips on how to make it work on port 80? I have tried a ton of things including manually installing the docker container, not using the template, with no luck...
-
I've been trying for way too long to get a split tunnel VPN working... I've searched this post repeatedly but still am a bit confused.
My goal: I want to use my home DNS (dual piholes), have access to local IPs, with all external network data skipping the tunnel (limited upload at site).
I have a fully working remote tunneled access setup, wg0. This works perfectly on numerous clients.
[Interface] #wg0 PrivateKey=deleted= Address=10.253.0.1 ListenPort=51820 PostUp=logger -t wireguard 'Tunnel WireGuard-wg0 started' PostDown=logger -t wireguard 'Tunnel WireGuard-wg0 stopped' [Peer] #01 PublicKey=deleted= PresharedKey=deleted= AllowedIPs=10.253.0.2 ===================================== [Interface] #01 PrivateKey=deleted= Address=10.253.0.2/32 DNS=192.168.1.112,192.168.1.111 [Peer] #rehoboam PresharedKey=deleted= PublicKey=deleted= Endpoint=deleted.com:51820 AllowedIPs=0.0.0.0/0
I have been trying (unsuccessfully) to get a split tunnel up. Here's my current not working config for wg1.
[Interface] #wg1 PrivateKey=deleted= Address=10.253.1.1 ListenPort=51821 PostUp=logger -t wireguard 'Tunnel WireGuard-wg1 started' PostDown=logger -t wireguard 'Tunnel WireGuard-wg1 stopped' [Peer] #01 PublicKey=deleted= PresharedKey=deleted= AllowedIPs=10.253.1.2,192.168.0.0/21 ====================================== [Interface] #01 PrivateKey=deleted= Address=10.253.1.2/32 DNS=192.168.1.112,192.168.1.111 [Peer] #rehoboamsplit PresharedKey=deleted= PublicKey=deleted= Endpoint=deleted.com:51821 AllowedIPs=10.253.1.1/32, 192.168.1.0/24
I have repeated all configuration changes for the new tunnel including adding static routes and port forwarding.
Static routes
Port forwarding overview
Detail of the new wg1 address, matches 51820
Resulting WAN in firewall
Any tips what I'm doing wrong?
-
Upgraded 6.9.1 to 6.9.2 successfully.
Only issue I'm seeing is that all help sections are starting expanded and some can't be minimized.
-
What's the type of device? If it's a Windows PC running the Wireguard client, you have to edit the tunnel and disable "Block untunneled traffic (kill-switch)".
-
1
-
-
3 minutes ago, Squid said:
Think so.
Static, non pi-hole DNS lookup on main network settings seems to have cleared it up. I'll look through the pihole logs to see if I can see what is being blocked to add to a whitelist.
Thanks for the help @Squid, all you do is appreciated.
-
5 minutes ago, Squid said:
Probably. No real reason to use piHole as the DNS for the server as there are no ads within the server.
Shutting array down to change to static public DNS addresses.
One question: will changing this make all docker containers on the server now use these for DNS and bypass my piholes? I know this isn't necessarily the right section to ask this question...
-
On 2/15/2021 at 12:32 PM, Squid said:
Everything seems to be fine for me.
I'm currently experiencing problems as well. I assumed it was DNS, made some changes, then came here and saw others are having issues as well. Do you know what specific domain it's trying to reach? Maybe pihole is blocking it on accident?
Download of appfeed failed. Community Applications requires your server to have internet access. The most common cause of this failure is a failure to resolve DNS addresses. You can try and reset your modem and router to fix this issue, or set static DNS addresses (Settings - Network Settings) of 208.67.222.222 and 208.67.220.220 and try again. Alternatively, there is also a chance that the server handling the application feed is temporarily down. Last JSON error Recorded: Syntax error
-
31 minutes ago, zdkxlepb7VHyjz07oopI said:
I've tried doing some keyword searches in this topic and in the Wireguard support topic without any luck.
At this point I have SWAG set up with a half dozen subdomains and it works beautifully from within and outside the local network. The peculiar thing is that I have a wireguard server set up in Unraid as well and if I use a "remote tunneled access" client, all the NGINX subdomains time-out and cannot be accessed.If I use the individual internal IP addresses + port I can still access the dockers though. The remote tunneled access clients can also successfully connect to my home network, SMB shares, browse the internet, ping/tracert the subdomains in question, etc... so I'm fairly certain the issue lies in how SWAG is set up and not Wireguard.
I feel like I'm missing something obvious and would greatly appreciate it if someone's heard of this issue before and can point me in the right direction.Are you proxying through cloudflare by chance? Cuz you can't proxy wireguard, has to be set to dns only.
-
Figured I'd post an update to this.
I got home, shut the server down, and pulled the USB drive. I then looked through the edited files and saw that when it died, the only changes were in the Wireguard section of the settings. I deleted the Wireguard folder and then reinstalled into the server. It then booted up and ran.
Must have created some IP conflict with my changes; I haven't had a chance to do a post-mortem on the files to see what was wrong.
-
So I failed to follow the old adage of "don't screw with any settings when you're several states away" and got myself into a pickle. Was hoping I could get some advice.
Today, I decided to change some settings with my Wireguard configuration. I normally use Wireguard to touch my server over a remote tunneled access, but because I was changing settings I instead did a Chrome Remote Desktop to another PC at my house so I wouldn't drop my connection. From that PC I then browsed local to the server.
While I was changing settings (only in the Wireguard section), at one point it paused on hitting Save/Apply which was unusual. I then realized that Unraid was completely unresponsive over the network from that local box. All services (containers, reverse proxies) immediately were offline.
My Unraid server doesn't have any remote KVM capabilities. I had my wife tap the power button and a few minutes later it did eventually shutdown. I had her reboot it afterwards.
It is still completely unresponsive over the network. Doesn't respond to ping, webpage doesn't load with either the IP address or the servername (both bare and .localdomain). I do see in my Unifi panel some data traffic which is confusing; only 30 MB in the past few hours.
Is it possible that something in the config files got borked when saving the Wireguard configuration? Is the best course of action to just pull the USB and modify something in there? I'm just trying to figure out what I should do next... I'll be near the server in a few days.
-
1 hour ago, spants said:
what is the server IP and the Pihole ip?
Server is .244, pihole is .32 set through br0. I can see on my router (unifi) something at .32 has reached out to the router.
-
Having trouble getting this to start. I have experience both with docker containers on Unraid as well as pihole running on other systems (pis, hyper-v).
On startup, it's getting stuck at the following point in the log shown below. I can't get the web console to work.
Starting crond Starting pihole-FTL (no-daemon) as root Starting lighttpdHere's what I've tried so far:
- chmod 777 on the appdata folder
- Tried both latest version and v4.3.4
- Privileged and unprivileged levels
- Verified that the IP shows up on my network (I can see the client in Unifi)
- Removed the default extra parameters from the template
Here's my full docker run command.
root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='pihole' --net='br0' --ip='192.168.1.32' -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'TCP_PORT_53'='53' -e 'UDP_PORT_53'='53' -e 'UDP_PORT_67'='67' -e 'TCP_PORT_80'='80' -e 'TCP_PORT_443'='443' -e 'DNS1'='1.1.1.1' -e 'DNS2'='1.0.0.1' -e 'TZ'='America/New_York' -e 'WEBPASSWORD'='supersecret' -e 'INTERFACE'='br0' -e 'ServerIP'='192.168.1.32' -e 'ServerIPv6'='' -e 'IPv6'='False' -e 'DNSMASQ_LISTENING'='all' -v '/mnt/disk1/appdata/pihole1/pihole/':'/etc/pihole/':'rw' -v '/mnt/disk1/appdata/pihole1/dnsmasq.d/':'/etc/dnsmasq.d/':'rw' --cap-add=NET_ADMIN --dns 1.1.1.1 --dns 1.0.0.1 --restart=unless-stopped 'pihole/pihole:latest'Any tips on what to try?
-
1 hour ago, shooga said:
I'm using this container successfully as a proxy for several other containers and also for a VM running Home Assistant. I modified the included config so that it would work with the VM and it seems fine except for websockets in some of the hassio add-ons. Websockets work fine via the local IP address, but not via the proxy.
Is there a reason that I can't simply add the necessary websocket config lines to the / location? That seems to kill the whole thing. As it is, I have tried to add another location for the base url of the add-on that I'm trying to enable websockets for (esphome here, but I've also tried vscode). It's not working and I believe it's most likely because I'm not configuring the proxy correctly.
Proxy config is below. Any help would be greatly appreciated!
server { listen 443 ssl; listen [::]:443 ssl; server_name homeassistant.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app 192.168.1.205; set $upstream_port 8123; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } location /api/websocket { resolver 127.0.0.11 valid=30s; set $upstream_app 192.168.1.205; set $upstream_port 8123; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Host $host; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } location /a0d7b954_esphome/ { resolver 127.0.0.11 valid=30s; set $upstream_app 192.168.1.205; set $upstream_port 8123; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Host $host:443; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } }Did you try dropping the slash after esphome? Also, why do you have :443 after proxy_set_header Host?
My configuration is otherwise the same except I do not have the proxy_set_header x-forwarded... set. See mine below. Note that /endpoint/ui is for Node-RED.
# make sure that your dns has a cname set for homeassistant and that your homeassistant container is not using a base url server { listen 443 ssl; listen [::]:443 ssl; server_name homeassistant.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app 192.168.1.31; set $upstream_port 8123; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } location /api/websocket { resolver 127.0.0.11 valid=30s; set $upstream_app 192.168.1.31; set $upstream_port 8123; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; proxy_set_header Host $host; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } location /api/hassio_ingress { resolver 127.0.0.11 valid=30s; set $upstream_app 192.168.1.31; set $upstream_port 8123; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; proxy_set_header Host $host; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } location /endpoint/ui { resolver 127.0.0.11 valid=30s; set $upstream_app 192.168.1.31; set $upstream_port 1880; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; proxy_set_header Host $host; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } } -
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.
-
1 hour ago, xuereb.dev said:
@linuxserver.io you should probably update the first post to reflect the new github
For those that haven't heard, this container is being renamed.
-
I had the same issue; container updated and then it stops working with a 500 error.
Looks like there was an update to Dokuwiki that causes some plugins to auto crash. I haven't gone into the details yet to see which plugins specifically are killing my wiki.
There are people commenting on the github repo for this LinuxServer container at the following link with more details:
-
I have a docker container (mikenye/adsbexchange) that uploads data online and then allows me to view the status through a specific address on their website.
https://www.adsbexchange.com/api/feeders/?feed=YOUR-UUID-HEREWhen I put in the WebUI field a path to this external address, the container updates successfully but the WebUI link does not show up in the overflow menu.
Are only internal network addresses allowed in the WebUI field?
If so, is there any way to add additional addresses in the overflow menu? It would be convenient on containers to have more than one path, pointing at for instance Docker Hub as well as the related GitHub.
-
On 6/5/2020 at 8:30 PM, Danietech said:
thanks?
To add this variable to a docker container, do the following.
- Edit the container
- Switch view to advanced at top right
- In "extra parameters", add the following text:
-e MAXMINDDB_LICENSE_KEY=[type key here, no brackets]
- The "-e" means it's an environment variable
- The next thing after that is the name of the variable
- Value of variable is then set to the right.
I'm also really new to Docker containers and have been figuring this out on the fly.
-
Any chance anyone can post their working Dokuwiki nginx configuration as well as any changes to settings they made within Dokuwiki itself? I've been trying various things without any success. There have been a few comments in this thread on the subject but nobody ever confirmed what the final configuration was actually...
edit: OK, finally figured out what was wrong. In the nginx configuration file, I was updating the port number to match the docker container when it needs to remain as the app port number. Also, zero changes were required within dokuwiki to make it work. Dumb on my part, I know; I'm still learning...
"Replace Key" function not working
in General Support
Posted
OK I think I figured it out; had to install My Servers to get that page to load properly. Now it's saying I already replaced my key in the past 12 months which isn't true...