[Support] binhex - rTorrentVPN


Recommended Posts

40 minutes ago, plantsandbinary said:

but you just said to me earlier this plugin/indicator has been broken for years.

nope, you said that and i corrected you:- 

https://forums.unraid.net/topic/46127-support-binhex-rtorrentvpn/?do=findComment&comment=865127

 

if the indicator at the bottom of the screen is red then you do not have a working incoming port, that plugin IS reliable, at least it is now that it got fixed (was broken for around 2 months).

 

grab your external ip address from settings/bittorrent/ip-host to report to tracker, grab your incoming port from settings/connection/port used for incoming connections and head over to this website:- https://www.yougetsignal.com/tools/open-ports/

 

paste in the ip and port and click on 'check', i think you will find your port is not open.

Link to comment
16 hours ago, binhex said:

nope, you said that and i corrected you:- 

https://forums.unraid.net/topic/46127-support-binhex-rtorrentvpn/?do=findComment&comment=865127

 

if the indicator at the bottom of the screen is red then you do not have a working incoming port, that plugin IS reliable, at least it is now that it got fixed (was broken for around 2 months).

 

grab your external ip address from settings/bittorrent/ip-host to report to tracker, grab your incoming port from settings/connection/port used for incoming connections and head over to this website:- https://www.yougetsignal.com/tools/open-ports/

 

paste in the ip and port and click on 'check', i think you will find your port is not open.

I'm tellin' ya. That thing does not work. 3 sites all tell me it's open. I have never, ever seen a green tick on that thing. Plus I am able to download and upload at line speed. Might want to check it again, but I don't think it's worth the hassle.

 

dfdf.png

Edited by plantsandbinary
Link to comment
7 hours ago, plantsandbinary said:

I'm tellin' ya. That thing does not work. 3 sites all tell me it's open. I have never, ever seen a green tick on that thing. Plus I am able to download and upload at line speed. Might want to check it again, but I don't think it's worth the hassle.

and i'm tellin' ya its always worked for me :-), i have a green icon right now, when it goes red then i check and sure enough the port is closed, my scripts then kick in and reconfigure the port and it goes back to green, dunno what to say dude but for the vast majority of people this just works *shrug*.

Link to comment
7 hours ago, binhex said:

and i'm tellin' ya its always worked for me :-), i have a green icon right now, when it goes red then i check and sure enough the port is closed, my scripts then kick in and reconfigure the port and it goes back to green, dunno what to say dude but for the vast majority of people this just works *shrug*.

Oh well it doesn't matter. Different strokes for different folks hahaha.

 

  

2 hours ago, koth said:

Following up from before, I gave PIA a try instead since it seems this was made to best support it. I removed the container and /config, spun the container back up with PIA, and it seemed to generate a port that showed green at the bottom as I was using the Montreal endpoint. Settings used:

Results were the same as with my other provider, unable to download anything. Hopefully this might give some useful information using a VPN you're more familiar with. Log:

https://pastebin.com/7JCUyHd2

This container works fine with other providers like Mullvad (which imo is the best provider you could ask for). You just need to drop the config file into the directory, restart the docker container and away you go. It's literally that easy.

Edited by plantsandbinary
Link to comment
10 minutes ago, plantsandbinary said:

Oh well it doesn't matter. Different strokes for different folks hahaha.

indeed, its only a indicator, no kittens were sacrificed as far as i know :-).

11 minutes ago, plantsandbinary said:

This container works fine with other providers like Mullvad (which imo is the best provider you could ask for). You just need to drop the config file into the directory, restart the docker container and away you go. It's literally that easy.

im glad you are enjoying my work :-).

Link to comment
2 hours ago, koth said:

Following up from before, I gave PIA a try instead since it seems this was made to best support it. I removed the container and /config, spun the container back up with PIA, and it seemed to generate a port that showed green at the bottom as I was using the Montreal endpoint. Settings used:

ive taken a look at your log and its clean, there are no issues with your docker config, so i think the issue has to lie with file permissions and/or config for rutorrent/rtorrent, check the following:-

 

1. check user with id 1000 and group id 1000 have write permissions to '/mnt/storage/Media'

2. can you screenshot rutorrent/settings/Downloads and rutorrent/settings/Autotools and paste here.

3. can you paste your rtorrent.rc file, it will be located at /config/rtorrent/config/rtorrent.rc

Link to comment
14 hours ago, koth said:

Ran chown just now to be sure

ok can you set the 'default directory for downloads' to /tmp, this will cause it to write inside the container then delete any torrents and re-download a test torrent and see what happens, i just want to rule out any mount issues and permissions issues.

 

just to confirm - this container does indeed work fine (i use it daily), so there is something local that is causing the issue.

Link to comment

fyi, I had exactly this "problem" with the delugevpn container. It was because I screwed up and pointed downloads to a directory without permissions. A torrent would connect and then disconnect after a second or so because it could not write to the file. As Binhex says, check where the files are being downloaded to!

Link to comment

Hi, changed port in rtorrent.rc to 13438 per my Airvpn settings, but still not getting a green check in rutorrent (and it doesn't appear to be working on any other open port checker). Does rtorrent itself need to be restarted or can I just restart the Docker? Is there a deeper issue?

 

Update: All clear on the Airvpn side, but still have the issue locally with the alert. Seems like maybe my changes to rtorrent.rc aren't saved and submitted to rutorrent?

Edited by drogg
Link to comment

rtorrent was working fine, but suddenly getting the following errors (attached screenshot)

What could be the issue.

 

2020-07-06 20:45:05,333 DEBG 'rutorrent-script' stderr output:
2020/07/06 20:45:05 [error] 713#713: *65 connect() failed (111: Connection refused) while connecting to upstream, client: 172.17.0.1, server: localhost, request: "POST /RPC2 HTTP/1.1", upstream: "scgi://127.0.0.1:5000", host: "192.168.1.106:9080"

1268874882_rtorrenterror.png.c6661443e2bfd219265e205dce6f82e2.png

unmhn-diagnostics-20200706-2042.zip rtorrentlogs.txt

Link to comment
5 hours ago, mhn_10 said:

rtorrent was working fine, but suddenly getting the following errors (attached screenshot)

What could be the issue.

hmm not sure why your plugins are not starting, but there are two easy steps to fix this:-

 

1. restart the container - if this doesnt fix the plugins issue then....

2. left click the icon, select 'edit' change a value of something and then change it back to what it was (so in effect no change) then click on 'apply' at the bottom, this will delete the old (broken) container and re-create it.

Link to comment
13 hours ago, cyriouslydylan said:

I have both this docker and you SABnzvd-VPN dockers, but I can't launch them at the same time, it gives me a server error. So there must be some sort of conflict with having both?

most probably it will be privoxy port clash on the host side, so change port 8118 on the host side to be unique for one of the containers, or if you arent using privoxy then remove the port.

Link to comment

Search has been broken for quite a while. Typing anything into the instant search field throws this error and the search does not execute:

image.png.84f5e0a30f532b87b7ebf20e84635686.png

 

I googled and found this:

https://github.com/Novik/ruTorrent/issues/1989

 

Maybe something needs to be updated in the container, or is this just on my end that I need to do something?
Recreating the container did not fix it.

Tried manually updating to the newer https://github.com/Micdu70/rutorrent-instantsearch, the one in the folder on my system was from 2010, but this did also not fix it.

EDIT: It seems that the manual updating to the newer instantsearch plugin worked! :) maybe it was a cache issue after updating it.

Edited by JohanSF
Link to comment

Is there a good guide to setting up rtorrentVPN someplace? I did what I've done to set up Transmission, qbittorrent, and delugeVPN, and nothing is working right. Somehow I was able to download a torrent from one of my private trackers, but then it won't seed ("Connection refused") and then everything I've tried to fix that has somehow screwed things up further, such that rtorrent isn't communicating with rutorrent, and sometimes the web interface doesn't even connect.

 

And of course I haven't even tried turning on the VPN portion yet....

Link to comment

Hi, things had been rock solid for some time, but now I am having problems.  First, when the container is running I get a lot of "The requst to rTorrent" has timed out errors, even though it appears the torrents are running.  Then, after a while things seem to lock up, and when I try to shut down the container it hangs. Here are the last few pages of logs. Unfortunately, the container seems to hang every day so it's not really usable unless I can solve this.

 

2020-07-18 17:52:16,632 DEBG 'watchdog-script' stdout output:

[warn] Incoming port site 'https://canyouseeme.org/' failed to web scrape, marking as failed

2020-07-18 17:52:50,737 DEBG 'rutorrent-script' stderr output:

2020/07/18 17:52:50 [error] 6379#6379: *162114 upstream timed out (110: Connection timed out) while connecting to upstream, client: 172.17.0.1, server: localhost, request: "GET /plugins/autodl-irssi/getlines.php?cid=1989910093&_=1595016892263 HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "localhost:9080", referrer: "http://localhost:9080/"

2020-07-18 17:53:02,124 DEBG 'rutorrent-script' stderr output:

2020/07/18 17:53:02 [error] 6379#6379: *162482 upstream timed out (110: Connection timed out) while connecting to upstream, client: 172.17.0.1, server: localhost, request: "GET /plugins/autodl-irssi/getlines.php?cid=1989910098&_=1594948550914 HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "localhost:9080", referrer: "http://localhost:9080/"

2020-07-18 17:53:51,732 DEBG 'rutorrent-script' stderr output:

2020/07/18 17:53:51 [error] 6379#6379: *162501 upstream timed out (110: Connection timed out) while connecting to upstream, client: 172.17.0.1, server: localhost, request: "GET /plugins/autodl-irssi/getlines.php?cid=1989910093&_=1595016892265 HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "localhost:9080", referrer: "http://localhost:9080/"

2020-07-18 17:54:05,125 DEBG 'rutorrent-script' stderr output:

2020/07/18 17:54:05 [error] 6379#6379: *162508 upstream timed out (110: Connection timed out) while connecting to upstream, client: 172.17.0.1, server: localhost, request: "GET /plugins/autodl-irssi/getlines.php?cid=1989910098&_=1594948550917 HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "localhost:9080", referrer: "http://localhost:9080/"

2020-07-18 17:55:05,149 DEBG 'rutorrent-script' stderr output:

2020/07/18 17:55:05 [error] 6379#6379: *162508 upstream timed out (110: Connection timed out) while connecting to upstream, client: 172.17.0.1, server: localhost, request: "GET /plugins/autodl-irssi/getlines.php?cid=1989910093&_=1595016892268 HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "localhost:9080", referrer: "http://localhost:9080/"

2020-07-18 17:55:06,412 DEBG 'rutorrent-script' stderr output:

2020/07/18 17:55:06 [error] 6379#6379: *162526 upstream timed out (110: Connection timed out) while connecting to upstream, client: 172.17.0.1, server: localhost, request: "GET /plugins/autodl-irssi/getlines.php?cid=1989910098&_=1594948550919 HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "localhost:9080", referrer: "http://localhost:9080/"

2020-07-18 17:55:15,068 DEBG 'rutorrent-script' stderr output:

2020/07/18 17:55:15 [error] 6379#6379: *162530 upstream timed out (110: Connection timed out) while connecting to upstream, client: 172.17.0.1, server: localhost, request: "POST /plugins/rss/action.php HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "localhost:9080", referrer: "http://localhost:9080/"

2020-07-18 17:55:21,940 DEBG 'rutorrent-script' stderr output:

2020/07/18 17:55:21 [error] 6378#6378: *162534 upstream timed out (110: Connection timed out) while connecting to upstream, client: 172.17.0.1, server: localhost, request: "GET /plugins/diskspace/action.php?_=1594948550920 HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "localhost:9080", referrer: "http://localhost:9080/"

2020-07-18 17:55:37,076 DEBG 'rutorrent-script' stderr output:

2020/07/18 17:55:37 [error] 6379#6379: *162536 upstream timed out (110: Connection timed out) while connecting to upstream, client: 172.17.0.1, server: localhost, request: "POST /plugins/rss/action.php HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "localhost:9080", referrer: "http://localhost:9080/"

2020-07-18 17:56:22,010 DEBG 'rutorrent-script' stderr output:

2020/07/18 17:56:22 [error] 6378#6378: *162534 upstream timed out (110: Connection timed out) while connecting to upstream, client: 172.17.0.1, server: localhost, request: "GET /plugins/autodl-irssi/getlines.php?cid=1989910093&_=1595016892271 HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "localhost:9080", referrer: "http://localhost:9080/"

2020-07-18 17:56:34,078 DEBG 'rutorrent-script' stderr output:

2020/07/18 17:56:34 [error] 6379#6379: *162546 upstream timed out (110: Connection timed out) while connecting to upstream, client: 172.17.0.1, server: localhost, request: "GET /plugins/autodl-irssi/getlines.php?cid=1989910098&_=1594948550921 HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "localhost:9080", referrer: "http://localhost:9080/"

2020-07-18 17:56:37,089 DEBG 'rutorrent-script' stderr output:

2020/07/18 17:56:37 [error] 6379#6379: *162550 upstream timed out (110: Connection timed out) while connecting to upstream, client: 172.17.0.1, server: localhost, request: "POST /plugins/rss/action.php HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "localhost:9080", referrer: "http://localhost:9080/"

2020-07-18 17:56:38,058 DEBG 'rutorrent-script' stderr output:

2020/07/18 17:56:38 [error] 6379#6379: *162536 upstream timed out (110: Connection timed out) while connecting to upstream, client: 172.17.0.1, server: localhost, request: "GET /plugins/diskspace/action.php?_=1594948550922 HTTP/1.1", upstream: "fastcgi://127.0.0.1:7777", host: "localhost:9080", referrer: "http://localhost:9080/"

2020-07-18 17:57:00,137 WARN received SIGTERM indicating exit request

2020-07-18 17:57:00,150 DEBG killing watchdog-script (pid 199) with signal SIGTERM

2020-07-18 17:57:00,152 INFO waiting for logrotate-script, rutorrent-script, start-script, watchdog-script to die

2020-07-18 17:57:01,163 DEBG fd 26 closed, stopped monitoring <POutputDispatcher at 140187461548016 for <Subprocess at 140187461546096 with name watchdog-script in state STOPPING> (stdout)>

2020-07-18 17:57:01,165 DEBG fd 30 closed, stopped monitoring <POutputDispatcher at 140187461548064 for <Subprocess at 140187461546096 with name watchdog-script in state STOPPING> (stderr)>

2020-07-18 17:57:01,168 INFO stopped: watchdog-script (terminated by SIGTERM)

2020-07-18 17:57:01,190 DEBG received SIGCHLD indicating a child quit

2020-07-18 17:57:01,203 DEBG killing start-script (pid 197) with signal SIGTERM

2020-07-18 17:57:01,218 DEBG fd 25 closed, stopped monitoring <POutputDispatcher at 140187461547488 for <Subprocess at 140187461488496 with name start-script in state STOPPING> (stderr)>

2020-07-18 17:57:01,225 DEBG fd 21 closed, stopped monitoring <POutputDispatcher at 140187461488544 for <Subprocess at 140187461488496 with name start-script in state STOPPING> (stdout)>

2020-07-18 17:57:01,227 INFO stopped: start-script (terminated by SIGTERM)

2020-07-18 17:57:01,229 DEBG received SIGCHLD indicating a child quit

2020-07-18 17:57:01,232 DEBG killing rutorrent-script (pid 196) with signal SIGTERM

2020-07-18 17:57:02,235 DEBG fd 16 closed, stopped monitoring <POutputDispatcher at 140187461488352 for <Subprocess at 140187461488304 with name rutorrent-script in state STOPPING> (stdout)>

2020-07-18 17:57:02,236 DEBG fd 20 closed, stopped monitoring <POutputDispatcher at 140187461547200 for <Subprocess at 140187461488304 with name rutorrent-script in state STOPPING> (stderr)>

2020-07-18 17:57:02,239 INFO stopped: rutorrent-script (terminated by SIGTERM)

2020-07-18 17:57:02,242 DEBG received SIGCHLD indicating a child quit

2020-07-18 17:57:02,245 DEBG killing logrotate-script (pid 194) with signal SIGTERM

2020-07-18 17:57:02,252 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 140187461794448 for <Subprocess at 140187461795024 with name logrotate-script in state STOPPING> (stdout)>

2020-07-18 17:57:02,254 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 140187461546288 for <Subprocess at 140187461795024 with name logrotate-script in state STOPPING> (stderr)>

2020-07-18 17:57:02,256 INFO stopped: logrotate-script (terminated by SIGTERM)

2020-07-18 17:57:02,258 DEBG received SIGCHLD indicating a child quit

Link to comment

I've been getting this error that is causing fatal errors and requiring rtorrent to have a restart. The only bandaid fix for this I've found was disabling encryption entirely. Is there any plans to updating rtorrent to something beyond 0.9.6 it doesn't seem to appear in the newer versions and I would like to have the option to accept encrypted connections. Error log from a recent crash below:

 

1595149504 C Caught internal_error: 'Read past initial payload after incoming encrypted handshake.'.
---DUMP---
/usr/lib/libtorrent.so.19(_ZN7torrent14internal_error10initializeERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE+0x25a) [0x7fa11ec7d89a]
/usr/bin/rtorrent(_ZN7torrent14internal_errorC1EPKc+0xb1) [0x55aa2cf27db1]
/usr/lib/libtorrent.so.19(+0x3cfe2) [0x7fa11ec72fe2]
/usr/lib/libtorrent.so.19(_ZN7torrent9PollEPoll7performEv+0xca) [0x7fa11ec9891a]
/usr/lib/libtorrent.so.19(_ZN7torrent9PollEPoll7do_pollEli+0x79) [0x7fa11ec98a39]
/usr/lib/libtorrent.so.19(_ZN7torrent11thread_base10event_loopEPS0_+0x123) [0x7fa11ecc9583]
/usr/bin/rtorrent(+0x4542c) [0x55aa2ceca42c]
/usr/lib/libc.so.6(__libc_start_main+0xf2) [0x7fa11e851002]
/usr/bin/rtorrent(+0x45c6e) [0x55aa2cecac6e]

 

 

Link to comment

Hi, one more update, before I posted the log when I tried to stop the container and it wouldn't. Here's the log for when the container hangs in the first place.  It appears to be related to privoxy possibly

 

2020-07-19 16:14:45,301 DEBG 'watchdog-script' stdout output:

[warn] Exit code '6' from curl != 0 or no response body received

[info] 2 retries left

[info] Retrying in 2 secs...

2020-07-19 16:14:49,314 DEBG 'watchdog-script' stdout output:

[warn] Exit code '6' from curl != 0 or no response body received

[info] 1 retries left

[info] Retrying in 2 secs...

2020-07-19 16:14:51,332 DEBG 'watchdog-script' stdout output:

[warn] Exit code '6' from curl != 0 or no response body received, exhausted retries

1

2020-07-19 16:14:51,364 DEBG 'watchdog-script' stdout output:

[warn] Incoming port site 'https://portchecker.co/' failed to web scrape, marking as failed

2020-07-19 16:15:11,454 DEBG 'watchdog-script' stdout output:

[warn] Exit code '6' from curl != 0 or no response body received

[info] 5 retries left

[info] Retrying in 2 secs...

2020-07-19 16:15:21,507 DEBG 'watchdog-script' stdout output:

[warn] Exit code '6' from curl != 0 or no response body received

[info] 4 retries left

[info] Retrying in 2 secs...

2020-07-19 16:15:29,528 DEBG 'watchdog-script' stdout output:

[warn] Exit code '6' from curl != 0 or no response body received

[info] 3 retries left

[info] Retrying in 2 secs...

2020-07-19 16:15:35,552 DEBG 'watchdog-script' stdout output:

[warn] Exit code '6' from curl != 0 or no response body received

[info] 2 retries left

[info] Retrying in 2 secs...

2020-07-19 16:15:39,592 DEBG 'watchdog-script' stdout output:

[warn] Exit code '6' from curl != 0 or no response body received

[info] 1 retries left

[info] Retrying in 2 secs...

2020-07-19 16:15:41,605 DEBG 'watchdog-script' stdout output:

[warn] Exit code '6' from curl != 0 or no response body received, exhausted retries

2020-07-19 16:15:41,607 DEBG 'watchdog-script' stdout output:

1

2020-07-19 16:15:41,632 DEBG 'watchdog-script' stdout output:

[warn] Incoming port site 'https://canyouseeme.org/' failed to web scrape, marking as failed

Link to comment

I've noticed recently that the docker is getting stuck on starting up at this line in the log

 

2020-07-19 23:05:22,411 DEBG 'start-script' stdout output:
Sun Jul 19 23:05:22 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]199.229.249.192:1198
Sun Jul 19 23:05:22 2020 UDP link local: (not bound)
Sun Jul 19 23:05:22 2020 UDP link remote: [AF_INET]199.229.249.192:1198

 

Any thoughts as to why?

Link to comment

Yet another update..... I had 1500 torrents running, so I deleted 1000 of them. I am still getting various "rTorrent is not responding" errors periodically but so far the container hasn't seized up.  So perhaps the issue is just too many torrents.  Does anyone know if there is some setting change I can make to allow for more torrents? I've already increased memory and processor allocation to Docker quite a bit.

Link to comment

Hi all,

 

this container has been working fine for me for ages, but in the last couple of days I've been seeing this error:

 

2020-07-20 09:39:43,246 DEBG 'start-script' stdout output:
[info] Attempting to get dynamically assigned port...

2020-07-20 09:39:43,372 DEBG 'start-script' stdout output:
[warn] Exit code '56' from curl != 0 or no response body received
[info] 12 retries left
[info] Retrying in 10 secs...

2020-07-20 09:39:53,431 DEBG 'start-script' stdout output:
[warn] Exit code '52' from curl != 0 or no response body received
[info] 11 retries left
[info] Retrying in 10 secs...

...

2020-07-20 09:41:44,100 DEBG 'start-script' stdout output:
[warn] Exit code '56' from curl != 0 or no response body received, exhausted retries

2020-07-20 09:41:44,101 DEBG 'start-script' stdout output:
[warn] Unable to download file from url 'http://209.222.18.222:2000/?client_id=d69a030e782a094400b7a58b95cd54440c69b881358170e6b28ea3c437f4f223', exiting script...

2020-07-20 09:41:44,101 DEBG 'start-script' stdout output:
[warn] PIA VPN port assignment API currently down, terminating OpenVPN process to force retry for incoming port...

2020-07-20 09:41:44,102 DEBG 'start-script' stdout output:
Mon Jul 20 09:41:44 2020 event_wait : Interrupted system call (code=4)

Neither privoxy or rtorrent works.

 

Any ideas what is causing this?

Edited by dvd.collector
Link to comment
16 hours ago, kirk8999 said:

Hi, one more update, before I posted the log when I tried to stop the container and it wouldn't. Here's the log for when the container hangs in the first place.  It appears to be related to privoxy possibly

 

2020-07-19 16:14:45,301 DEBG 'watchdog-script' stdout output:

[warn] Exit code '6' from curl != 0 or no response body received

[info] 2 retries left

[info] Retrying in 2 secs...

2020-07-19 16:14:49,314 DEBG 'watchdog-script' stdout output:

[warn] Exit code '6' from curl != 0 or no response body received

[info] 1 retries left

[info] Retrying in 2 secs...

2020-07-19 16:14:51,332 DEBG 'watchdog-script' stdout output:

[warn] Exit code '6' from curl != 0 or no response body received, exhausted retries

1

2020-07-19 16:14:51,364 DEBG 'watchdog-script' stdout output:

[warn] Incoming port site 'https://portchecker.co/' failed to web scrape, marking as failed

2020-07-19 16:15:11,454 DEBG 'watchdog-script' stdout output:

[warn] Exit code '6' from curl != 0 or no response body received

[info] 5 retries left

[info] Retrying in 2 secs...

2020-07-19 16:15:21,507 DEBG 'watchdog-script' stdout output:

[warn] Exit code '6' from curl != 0 or no response body received

[info] 4 retries left

[info] Retrying in 2 secs...

2020-07-19 16:15:29,528 DEBG 'watchdog-script' stdout output:

[warn] Exit code '6' from curl != 0 or no response body received

[info] 3 retries left

[info] Retrying in 2 secs...

2020-07-19 16:15:35,552 DEBG 'watchdog-script' stdout output:

[warn] Exit code '6' from curl != 0 or no response body received

[info] 2 retries left

[info] Retrying in 2 secs...

2020-07-19 16:15:39,592 DEBG 'watchdog-script' stdout output:

[warn] Exit code '6' from curl != 0 or no response body received

[info] 1 retries left

[info] Retrying in 2 secs...

2020-07-19 16:15:41,605 DEBG 'watchdog-script' stdout output:

[warn] Exit code '6' from curl != 0 or no response body received, exhausted retries

2020-07-19 16:15:41,607 DEBG 'watchdog-script' stdout output:

1

2020-07-19 16:15:41,632 DEBG 'watchdog-script' stdout output:

[warn] Incoming port site 'https://canyouseeme.org/' failed to web scrape, marking as failed

do the following:-

https://github.com/binhex/documentation/blob/master/docker/faq/help.md

Link to comment
11 hours ago, Spies said:

I've noticed recently that the docker is getting stuck on starting up at this line in the log

 

2020-07-19 23:05:22,411 DEBG 'start-script' stdout output:
Sun Jul 19 23:05:22 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]199.229.249.192:1198
Sun Jul 19 23:05:22 2020 UDP link local: (not bound)
Sun Jul 19 23:05:22 2020 UDP link remote: [AF_INET]199.229.249.192:1198

 

Any thoughts as to why?

do the following:-

https://github.com/binhex/documentation/blob/master/docker/faq/help.md

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.