Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Support] binhex - SABnzbdVPN

Featured Replies

partial~ usually means that the file hasn't finished copying to it's final destination.

  • Replies 1.8k
  • Views 423.8k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • i'm aware of the issue guys and i think i have a fix, i shall post back when i have built a fixed image.

  • hi guys, spotted the issue regards dos2unix.sh and corrected it, image now  building, should be done in around an hour.. then pull and you should be back up and running.

  • there are ongoing issues with PIA DNS, you can try setting NAME_SERVERS to the following (removes PIA DNS):- 84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1  

Posted Images

How long does it typically stay that way?  It has been a couple days for a 5 gb file. The downloads folder shows a good and usable file extension.

 

If it stays that way, do you know where I might look to find more information inside my setup to figure out what happened? Thanks

@binhexI starting having issues this morning with been running for over a year and all of the sudden this morning it would not load the internal URL. 

I Removed the Docker and the Config folder and started over and same issue. If i turn off VPN it works but if i Enable it then it wont load the page so i got it down to the VPN. My Network is 172.16.5.0/23 and that is configured in the LAN setting. Here my log any help would be great 

 

 

 

 

supervisord.log

  • Author
11 minutes ago, rguinn said:

@binhexI starting having issues this morning with been running for over a year and all of the sudden this morning it would not load the internal URL. 

I Removed the Docker and the Config folder and started over and same issue. If i turn off VPN it works but if i Enable it then it wont load the page so i got it down to the VPN. My Network is 172.16.5.0/23 and that is configured in the LAN setting. Here my log any help would be great 

 

 

 

 

supervisord.log 22.28 kB · 0 downloads

check your location to are trying to connect to, its either been renamed or doesnt exist any more.

Just now, binhex said:

check your location to are trying to connect to, its either been renamed or doesnt exist any more.

That would be the OVPN file correct? 

 

I also noticed that when VPN is on if i enter the custom port 8083 it will change to 8080 never seen it do that before 

6 minutes ago, rguinn said:

That would be the OVPN file correct? 

 

I also noticed that when VPN is on if i enter the custom port 8083 it will change to 8080 never seen it do that before 

@binhex I DL a new VPN files from PIA website and same issues here a new log 

 

image.png.f2cab970d3ddd6136639f663953a2ef4.png

 

image.png.78b873b2de25bebceeb351ee447de0e6.png

 

not sure what i am doing wrong. Thank you for helping 

supervisord-newlocation.txt

  • Author
5 minutes ago, rguinn said:

@binhex I DL a new VPN files from PIA website and same issues here a new log 

 

image.png.f2cab970d3ddd6136639f663953a2ef4.png

 

image.png.78b873b2de25bebceeb351ee447de0e6.png

 

not sure what i am doing wrong. Thank you for helping 

supervisord-newlocation.txt 20.96 kB · 0 downloads

thats a sucessful start, so check your web browser, ensure the machine you are attempting to connect to sabnzbd web ui is coming from an ip in the range 172.16.5.0/23, ensure no vlan blocking or host firewall.

3 minutes ago, binhex said:

thats a sucessful start, so check your web browser, ensure the machine you are attempting to connect to sabnzbd web ui is coming from an ip in the range 172.16.5.0/23, ensure no vlan blocking or host firewall.

Thank you I am on a ethernet connected machine on the same subnet no VLan or Firewall and I even rebooted the UNRAID Host 

 

image.png.966875f45748dca778e6545cc070b2fe.png

8 minutes ago, rguinn said:

@binhexThank you I am on a ethernet connected machine on the same subnet no VLan or Firewall and I even rebooted the UNRAID Host 

 

image.png.966875f45748dca778e6545cc070b2fe.png

Also DL the docker for firefox on the host and attempted to connect 

image.png.e93083feb54ae8585ab37ba6b1141d8a.png

Edited by rguinn
tag

Out of the blue, I can no longer access the UI via IP address etc. Just says connecting... and never loads the UI. Clearly I've messed something up somewhere. What's the proper way to remove my existing install, including appdata contents, and start again?

5 minutes ago, newoski said:

Out of the blue, I can no longer access the UI via IP address etc. Just says connecting... and never loads the UI. Clearly I've messed something up somewhere. What's the proper way to remove my existing install, including appdata contents, and start again?

Same Here ! before wiping it out can you do a debug and upload the log just incase there a bigger problem and @binhexcan review 

19 minutes ago, rguinn said:

Same Here ! before wiping it out can you do a debug and upload the log just incase there a bigger problem and @binhexcan review 

Already wiped, using CA tools, and reinstalled. Working fine after I did that

@binhexI was able to remove the app and delete the folder and here what i found if i uses any port other then 8080 on the reinstall it will not work. But if i uses 8080 its working fine. lucky i don't have anything using 8080 so i just do that @newoski thanks you letting me know

last night I noticed some problems with sab. I restarted the docker and now I can not access the UI unless I set the docker to VPN=OFF.

 

here is a log.

 

https://pastebin.com/iV6hfwY9

 

 

I think i figured it out. seems PIA changed from us-texas.privateinternetaccess.com to us-dal.privateinternetaccess.com. Seems there were a few other changes if anyone else is having this issue.

Edited by itskamel

Hi,

 

I have my system set up to back up docker containers every Sunday morning. However, without fail I seem to get a ‘connection failed’ error within SABnzbdVPN upon the container restarting. Frustrating as none of the other containers that rely on the proxy will work either, until I go in and manually restart SABnzbdVPN.

 

Any ideas what might be causing the connection failed? I have a working system otherwise. 

E1F7A0BC-7F1B-47F6-969E-FF9E851118CC.jpeg

 

I have added some logs which I think may show the issue:

 

2020-07-19 07:51:40,542 DEBG 'start-script' stdout output:
Sun Jul 19 07:51:40 2020 ROUTE6: default_gateway=UNDEF
Sun Jul 19 07:51:40 2020 OpenVPN ROUTE6: OpenVPN needs a gateway parameter for a --route-ipv6 option and no default was specified by either --route-ipv6-gateway or --ifconfig-ipv6 options
Sun Jul 19 07:51:40 2020 OpenVPN ROUTE: failed to parse/resolve route for host/network: fc00::/7

Sun Jul 19 07:51:40 2020 OpenVPN ROUTE6: OpenVPN needs a gateway parameter for a --route-ipv6 option and no default was specified by either --route-ipv6-gateway or --ifconfig-ipv6 options
Sun Jul 19 07:51:40 2020 OpenVPN ROUTE: failed to parse/resolve route for host/network: 3000::/4

Sun Jul 19 07:51:40 2020 OpenVPN ROUTE6: OpenVPN needs a gateway parameter for a --route-ipv6 option and no default was specified by either --route-ipv6-gateway or --ifconfig-ipv6 options
Sun Jul 19 07:51:40 2020 OpenVPN ROUTE: failed to parse/resolve route for host/network: 2000::/4

Sun Jul 19 07:51:40 2020 OpenVPN ROUTE6: OpenVPN needs a gateway parameter for a --route-ipv6 option and no default was specified by either --route-ipv6-gateway or --ifconfig-ipv6 options
Sun Jul 19 07:51:40 2020 OpenVPN ROUTE: failed to parse/resolve route for host/network: ::/3


2020-07-19 07:51:40,542 DEBG 'start-script' stdout output:
Sun Jul 19 07:51:40 2020 TUN/TAP device tun0 opened
Sun Jul 19 07:51:40 2020 TUN/TAP TX queue length set to 100
Sun Jul 19 07:51:40 2020 /usr/bin/ip link set dev tun0 up mtu 1500

2020-07-19 07:51:40,543 DEBG 'start-script' stdout output:
Sun Jul 19 07:51:40 2020 /usr/bin/ip addr add dev tun0 10.32.208.193/24 broadcast 10.32.208.255

2020-07-19 07:51:40,544 DEBG 'start-script' stdout output:
Sun Jul 19 07:51:40 2020 /root/openvpnup.sh tun0 1500 1553 10.32.208.193 255.255.255.0 init

2020-07-19 07:51:40,660 DEBG 'start-script' stdout output:
[info] Application does not require port forwarding or VPN provider is != pia, skipping incoming port assignment

2020-07-19 07:51:40,660 DEBG 'start-script' stdout output:
[info] Checking we can resolve name 'www.google.com' to address...

2020-07-19 07:51:40,663 DEBG 'start-script' stdout output:
[debug] Having issues resolving name 'www.google.com', sleeping before retry...

2020-07-19 07:51:45,599 DEBG 'start-script' stdout output:
Sun Jul 19 07:51:45 2020 /usr/bin/ip route add 134.19.179.242/32 via 172.17.0.1

2020-07-19 07:51:45,600 DEBG 'start-script' stdout output:
Sun Jul 19 07:51:45 2020 /usr/bin/ip route add 0.0.0.0/1 via 10.32.208.1

2020-07-19 07:51:45,601 DEBG 'start-script' stdout output:
Sun Jul 19 07:51:45 2020 /usr/bin/ip route add 128.0.0.0/1 via 10.32.208.1

2020-07-19 07:51:45,602 DEBG 'start-script' stdout output:
Sun Jul 19 07:51:45 2020 WARNING: OpenVPN was configured to add an IPv6 route over tun0. However, no IPv6 has been configured for this interface, therefore the route installation may fail or may not work as expected.

 

Edited by stridemat
Added logs

  • Author
On 7/19/2020 at 8:06 AM, stridemat said:

I have my system set up to back up docker containers every Sunday morning.

that depends on how you have it set, i believe there is an option to 'pause' containers during backup, you must NOT use this option with any of my vpn docker images as they will not play nicely with pause/resume, you have to perform a shutdown of the container, backup, then a startup.

5 hours ago, binhex said:

that depends on how you have it set, i believe there is an option to 'pause' containers during backup, you must NOT use this option with any of my vpn docker images as they will not play nicely with pause/resume, you have to perform a shutdown of the container, backup, then a startup.

Thanks for the quick response - I shall take a look though I do think CA Auto Update Applications does shutdown, instead of pausing.

  • Author
27 minutes ago, stridemat said:

I shall take a look though I do think CA Auto Update Applications does shutdown, instead of pausing.

CA Auto Update is not used for backups,  that is used to auto update apps, the backup plugin is called 'CA Appdata Backup/Restore v2', check the settings.

1 minute ago, binhex said:

CA Auto Update is not used for backups,  that is used to auto update apps, the backup plugin is called 'CA Appdata Backup/Restore v2', check the settings.

Yeah. Wrong plugin. I will take a look at the settings when I finish work. 

  • 2 weeks later...
On 7/18/2020 at 1:41 PM, itskamel said:

last night I noticed some problems with sab. I restarted the docker and now I can not access the UI unless I set the docker to VPN=OFF.

 

here is a log.

 

https://pastebin.com/iV6hfwY9

 

 

I think i figured it out. seems PIA changed from us-texas.privateinternetaccess.com to us-dal.privateinternetaccess.com. Seems there were a few other changes if anyone else is having this issue.

Hit a similar problem this evening. Sorted by confirming that ovpn i was using was responding very slowly. Switched routing with another vpn config, no changes at all to docker , and all now working. seems PIA have been making changes.

On 7/19/2020 at 8:06 AM, stridemat said:

Hi,

 

I have my system set up to back up docker containers every Sunday morning. However, without fail I seem to get a ‘connection failed’ error within SABnzbdVPN upon the container restarting. Frustrating as none of the other containers that rely on the proxy will work either, until I go in and manually restart SABnzbdVPN.

 

Any ideas what might be causing the connection failed? I have a working system otherwise. 

E1F7A0BC-7F1B-47F6-969E-FF9E851118CC.jpeg

 

I have added some logs which I think may show the issue:

 


2020-07-19 07:51:40,542 DEBG 'start-script' stdout output:
Sun Jul 19 07:51:40 2020 ROUTE6: default_gateway=UNDEF
Sun Jul 19 07:51:40 2020 OpenVPN ROUTE6: OpenVPN needs a gateway parameter for a --route-ipv6 option and no default was specified by either --route-ipv6-gateway or --ifconfig-ipv6 options
Sun Jul 19 07:51:40 2020 OpenVPN ROUTE: failed to parse/resolve route for host/network: fc00::/7

Sun Jul 19 07:51:40 2020 OpenVPN ROUTE6: OpenVPN needs a gateway parameter for a --route-ipv6 option and no default was specified by either --route-ipv6-gateway or --ifconfig-ipv6 options
Sun Jul 19 07:51:40 2020 OpenVPN ROUTE: failed to parse/resolve route for host/network: 3000::/4

Sun Jul 19 07:51:40 2020 OpenVPN ROUTE6: OpenVPN needs a gateway parameter for a --route-ipv6 option and no default was specified by either --route-ipv6-gateway or --ifconfig-ipv6 options
Sun Jul 19 07:51:40 2020 OpenVPN ROUTE: failed to parse/resolve route for host/network: 2000::/4

Sun Jul 19 07:51:40 2020 OpenVPN ROUTE6: OpenVPN needs a gateway parameter for a --route-ipv6 option and no default was specified by either --route-ipv6-gateway or --ifconfig-ipv6 options
Sun Jul 19 07:51:40 2020 OpenVPN ROUTE: failed to parse/resolve route for host/network: ::/3


2020-07-19 07:51:40,542 DEBG 'start-script' stdout output:
Sun Jul 19 07:51:40 2020 TUN/TAP device tun0 opened
Sun Jul 19 07:51:40 2020 TUN/TAP TX queue length set to 100
Sun Jul 19 07:51:40 2020 /usr/bin/ip link set dev tun0 up mtu 1500

2020-07-19 07:51:40,543 DEBG 'start-script' stdout output:
Sun Jul 19 07:51:40 2020 /usr/bin/ip addr add dev tun0 10.32.208.193/24 broadcast 10.32.208.255

2020-07-19 07:51:40,544 DEBG 'start-script' stdout output:
Sun Jul 19 07:51:40 2020 /root/openvpnup.sh tun0 1500 1553 10.32.208.193 255.255.255.0 init

2020-07-19 07:51:40,660 DEBG 'start-script' stdout output:
[info] Application does not require port forwarding or VPN provider is != pia, skipping incoming port assignment

2020-07-19 07:51:40,660 DEBG 'start-script' stdout output:
[info] Checking we can resolve name 'www.google.com' to address...

2020-07-19 07:51:40,663 DEBG 'start-script' stdout output:
[debug] Having issues resolving name 'www.google.com', sleeping before retry...

2020-07-19 07:51:45,599 DEBG 'start-script' stdout output:
Sun Jul 19 07:51:45 2020 /usr/bin/ip route add 134.19.179.242/32 via 172.17.0.1

2020-07-19 07:51:45,600 DEBG 'start-script' stdout output:
Sun Jul 19 07:51:45 2020 /usr/bin/ip route add 0.0.0.0/1 via 10.32.208.1

2020-07-19 07:51:45,601 DEBG 'start-script' stdout output:
Sun Jul 19 07:51:45 2020 /usr/bin/ip route add 128.0.0.0/1 via 10.32.208.1

2020-07-19 07:51:45,602 DEBG 'start-script' stdout output:
Sun Jul 19 07:51:45 2020 WARNING: OpenVPN was configured to add an IPv6 route over tun0. However, no IPv6 has been configured for this interface, therefore the route installation may fail or may not work as expected.

 

So this is still happening every Sunday morning and I’m at a loss as to why.  The setting within ‘CA Appdata Backup/Restore v2’ are as below. Looks ok to me and no other app has this issue. 


A329CA92-AF65-4C72-A07E-B1FA31BC6F1C.thumb.jpeg.dcd953fe4a79569bc6a58599cea79525.jpeg

Edited by stridemat

Since the latest update I've been getting this error. Any idea?

 

ERROR 11 hours ago [03/Aug/2020:09:21:28] ENGINE Error in HTTPServer.tick
Traceback (most recent call last):
  File "/usr/lib/python3.8/site-packages/cheroot/server.py", line 1776, in serve
    self.tick()
  File "/usr/lib/python3.8/site-packages/cheroot/server.py", line 1999, in tick
    conn = self.connections.get_conn(self.socket)
  File "/usr/lib/python3.8/site-packages/cheroot/connections.py", line 180, in get_conn
    return self._from_server_socket(server_socket)
  File "/usr/lib/python3.8/site-packages/cheroot/connections.py", line 199, in _from_server_socket
    s, ssl_env = self.server.ssl_adapter.wrap(s)
  File "/usr/lib/python3.8/site-packages/cheroot/ssl/builtin.py", line 243, in wrap
    s = self.context.wrap_socket(
  File "/usr/lib/python3.8/ssl.py", line 500, in wrap_socket
    return self.sslsocket_class._create(
  File "/usr/lib/python3.8/ssl.py", line 1040, in _create
    self.do_handshake()
  File "/usr/lib/python3.8/ssl.py", line 1309, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLError: [SSL: VERSION_TOO_LOW] version too low (_ssl.c:1108)

 

image.thumb.png.862235bf104b36d03326d78c3c51cfd6.png

  • Author
On 8/4/2020 at 4:02 AM, Fiala06 said:

Since the latest update I've been getting this error. Any idea?

looks like this is a match:-

https://github.com/sabnzbd/sabnzbd/issues/1437

 

it looks like its cherrypy spewing the error but that issue above is not clear on how to fix it other than switching sabnzbd to pyopenssl, which cant be easily done as its hard coded to use builtin. i think the error maybe caused by accessing the web ui over https, if that is the case trying switching to plain http and see if the error continues.

Sabnzbdvpn runs without problems when I set the network settings to "Bridge".

 

If I go to "br0" here to get an IP address different from the host, the web interface doesn't work anymore or can't be accessed.

 

Sabnzbd and Privoxy are listening on the correct ports when I look at the log, but the web interface is not accessible and a portscan only shows that Privoxy is running.

tower-diagnostics-20200808-1458.zip

Sabnzbdvpn Log.txt

Edited by aurevo

On 7/19/2020 at 8:06 AM, stridemat said:

Hi,

 

I have my system set up to back up docker containers every Sunday morning. However, without fail I seem to get a ‘connection failed’ error within SABnzbdVPN upon the container restarting. Frustrating as none of the other containers that rely on the proxy will work either, until I go in and manually restart SABnzbdVPN.

 

Any ideas what might be causing the connection failed? I have a working system otherwise. 

E1F7A0BC-7F1B-47F6-969E-FF9E851118CC.jpeg

 

I have added some logs which I think may show the issue:

 


2020-07-19 07:51:40,542 DEBG 'start-script' stdout output:
Sun Jul 19 07:51:40 2020 ROUTE6: default_gateway=UNDEF
Sun Jul 19 07:51:40 2020 OpenVPN ROUTE6: OpenVPN needs a gateway parameter for a --route-ipv6 option and no default was specified by either --route-ipv6-gateway or --ifconfig-ipv6 options
Sun Jul 19 07:51:40 2020 OpenVPN ROUTE: failed to parse/resolve route for host/network: fc00::/7

Sun Jul 19 07:51:40 2020 OpenVPN ROUTE6: OpenVPN needs a gateway parameter for a --route-ipv6 option and no default was specified by either --route-ipv6-gateway or --ifconfig-ipv6 options
Sun Jul 19 07:51:40 2020 OpenVPN ROUTE: failed to parse/resolve route for host/network: 3000::/4

Sun Jul 19 07:51:40 2020 OpenVPN ROUTE6: OpenVPN needs a gateway parameter for a --route-ipv6 option and no default was specified by either --route-ipv6-gateway or --ifconfig-ipv6 options
Sun Jul 19 07:51:40 2020 OpenVPN ROUTE: failed to parse/resolve route for host/network: 2000::/4

Sun Jul 19 07:51:40 2020 OpenVPN ROUTE6: OpenVPN needs a gateway parameter for a --route-ipv6 option and no default was specified by either --route-ipv6-gateway or --ifconfig-ipv6 options
Sun Jul 19 07:51:40 2020 OpenVPN ROUTE: failed to parse/resolve route for host/network: ::/3


2020-07-19 07:51:40,542 DEBG 'start-script' stdout output:
Sun Jul 19 07:51:40 2020 TUN/TAP device tun0 opened
Sun Jul 19 07:51:40 2020 TUN/TAP TX queue length set to 100
Sun Jul 19 07:51:40 2020 /usr/bin/ip link set dev tun0 up mtu 1500

2020-07-19 07:51:40,543 DEBG 'start-script' stdout output:
Sun Jul 19 07:51:40 2020 /usr/bin/ip addr add dev tun0 10.32.208.193/24 broadcast 10.32.208.255

2020-07-19 07:51:40,544 DEBG 'start-script' stdout output:
Sun Jul 19 07:51:40 2020 /root/openvpnup.sh tun0 1500 1553 10.32.208.193 255.255.255.0 init

2020-07-19 07:51:40,660 DEBG 'start-script' stdout output:
[info] Application does not require port forwarding or VPN provider is != pia, skipping incoming port assignment

2020-07-19 07:51:40,660 DEBG 'start-script' stdout output:
[info] Checking we can resolve name 'www.google.com' to address...

2020-07-19 07:51:40,663 DEBG 'start-script' stdout output:
[debug] Having issues resolving name 'www.google.com', sleeping before retry...

2020-07-19 07:51:45,599 DEBG 'start-script' stdout output:
Sun Jul 19 07:51:45 2020 /usr/bin/ip route add 134.19.179.242/32 via 172.17.0.1

2020-07-19 07:51:45,600 DEBG 'start-script' stdout output:
Sun Jul 19 07:51:45 2020 /usr/bin/ip route add 0.0.0.0/1 via 10.32.208.1

2020-07-19 07:51:45,601 DEBG 'start-script' stdout output:
Sun Jul 19 07:51:45 2020 /usr/bin/ip route add 128.0.0.0/1 via 10.32.208.1

2020-07-19 07:51:45,602 DEBG 'start-script' stdout output:
Sun Jul 19 07:51:45 2020 WARNING: OpenVPN was configured to add an IPv6 route over tun0. However, no IPv6 has been configured for this interface, therefore the route installation may fail or may not work as expected.

 

 

On 8/3/2020 at 6:53 AM, stridemat said:

So this is still happening every Sunday morning and I’m at a loss as to why.  The setting within ‘CA Appdata Backup/Restore v2’ are as below. Looks ok to me and no other app has this issue. 


A329CA92-AF65-4C72-A07E-B1FA31BC6F1C.thumb.jpeg.dcd953fe4a79569bc6a58599cea79525.jpeg

 So still having this issue and at a loss to why. Looking at the Unraid logs and not just the docker logs the following is noted:

 

Quote

Aug 16 07:16:10 Tower kernel: docker0: port 6(veth2477b33) entered disabled state
Aug 16 07:16:10 Tower kernel: device veth2477b33 left promiscuous mode
Aug 16 07:16:10 Tower kernel: docker0: port 6(veth2477b33) entered disabled state
Aug 16 07:16:10 Tower avahi-daemon[5008]: Withdrawing address record for fe80::e09d:52ff:fe52:f7eb on veth2477b33.
Aug 16 07:16:10 Tower kernel: docker0: port 6(vethd37a551) entered blocking state
Aug 16 07:16:10 Tower kernel: docker0: port 6(vethd37a551) entered disabled state
Aug 16 07:16:10 Tower kernel: device vethd37a551 entered promiscuous mode
Aug 16 07:16:10 Tower kernel: IPv6: ADDRCONF(NETDEV_UP): vethd37a551: link is not ready
Aug 16 07:16:10 Tower kernel: docker0: port 6(vethd37a551) entered blocking state
Aug 16 07:16:10 Tower kernel: docker0: port 6(vethd37a551) entered forwarding state
Aug 16 07:16:10 Tower kernel: eth0: renamed from veth23107a7
Aug 16 07:16:10 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethd37a551: link becomes ready
Aug 16 07:16:11 Tower avahi-daemon[5008]: Joining mDNS multicast group on interface vethd37a551.IPv6 with address fe80::e80b:bcff:fe53:3afa.
Aug 16 07:16:11 Tower avahi-daemon[5008]: New relevant interface vethd37a551.IPv6 for mDNS.
Aug 16 07:16:11 Tower avahi-daemon[5008]: Registering new address record for fe80::e80b:bcff:fe53:3afa on vethd37a551.*.

 That’s the output when restarting the docker container manually having had the connection failed issue. I do not have IPv6 set up in the docker. Would this be cashing my issue?

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

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.