g0nz0
-
Posts
18 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by g0nz0
-
-
I believe the issue now maybe down to docker.io rate limiting / blocking IPs due to the number of pull requests. There are 2 parts to this bug:
1) How docker hub banns IPs that are in the general public sphere making it difficult to get them released once blocked.
2) how unraid is making request to see updated version of containers to docker hub thus getting the IPs blocked in the first instance.
I've filed a bug report with unraid, but I've not seen any movement on it yet. I've also put a request in to get my static IP unblocked by docker, but there is still no movement there either yet.
-
I believe it maybe something to do with maintainers using git directly to manage their images, and the unraid system is now unable to monitor for versions. Given how many have switched over to this method, I'm hoping it can be patched soon. There is very little on how to resolve it out that I've been able to find, but about 2/3rds of my containers are now in this state.
Forcing a re-download of the container by adding / canging a dead envrionment variable will force it to update, but it's impossible to say if it's needed on any given 'broken' container at present.-
1
-
-
35 minutes ago, Civic1201 said:
For the "issue" docker not available try this:
Thanks, that's worked for me.
-
1 hour ago, darcon said:
Is anyone else having problems updating the app since yesterday? Both Tdarr and Tdarr Node.
Yup, same here. Hopefully it will resolve itself soon.
-
1
-
-
Will we likely see an update to this container soon so that the log4j vulnerability is patched out? Needs controller version 6.5.54 or above to no longer be vulnerable.
-
9 minutes ago, binhex said:
ok its fairly simple, unraid web ui/docker tab/left click and edit crafty container, scroll down to the bottom and click on 'Add another Path, Port, Variable, Label or Device' select config type of 'port' then define the container and host ports you want to add, if you want to do a range then use a hyphen between the port range, an example:-
click on save and apply.
Thanks, I hacked it in by adding an additional variable (-p <port range>:<port range>) in the advanced tab which work, but this way looks more sensible. I'll update my config in a bit to use this method.
-
1
-
-
2 minutes ago, binhex said:
sure!, nothing stopping you adding additional ports to the container.
Thanks. I'm too used to running raw docker or docker under rancher, so just trying to get to grips with how to do it under un-raid. But I know there are far less technically minded people around that this feature would be super useful for.
-
12 hours ago, SkinnySkelly said:
Ok after SEVERAL grusome hours i have fixed it.
First: change to Privileged mode in the unraid settings for the crafty container
2nd: make sure to make the logs folder and put the latest.log file in it (it can be blank)
so in your folder you made for your server it will be SERVERNAME/logs/latest.log
3rd made a server.properties file (also blank)
put this in the main SERVERNAME folder
4th make a eula.txt file and put this in it : eula=true
put this in the main SERVERNAME folder
it SHOULD boot right up after that.
wish i knew how broken this application was before trying it out. Not rocket science to have all these items premade no idea why the crafty developers don't already do this.
If you have a blank directory with just the jar in, when crafy kicks the jar off for the first time it should auto create everything you mentions above but fail to start the server until you make the edits (including setting the eula to true) that you want.
I had no issues with it, and for me, that side of things worked as expected first time. No different to if you kicked an MC server off the old fashioned way under screen etc. -
Is it possible to map a port range back to the container like with your minos container? It'd be useful for running types of server MC server under a single solution given the admin console supports it.
Other than that excellent work, and a nice upgrade from mineos which was showing it's age in terms of supported servers. -
Marking as solved. I've now confirmed that the unraid server itself isn't the bottleneck by getting 1Gb speeds between unraid and my firewall.
-
1
-
-
Thanks. I'll see if I can confirm using my firewall to bounce off too. It's possible that the inline cable has an issue, but is is reporting as a 1G connection to the switch. Hope it's no the in wall cable that's acting up!
-
First test is the standard Gigabit connection, second is bonded (still playiong around with the bonded connection, but show I should at least get the same speeds from this client).
Client logs:
C:\Users\gonzo\Documents\iperf-3.1.3-win64>iperf3.exe -c 10.250.1.100 Connecting to host 10.250.1.100, port 5201 [ 4] local 10.250.1.110 port 57137 connected to 10.250.1.100 port 5201 [ ID] Interval Transfer Bandwidth [ 4] 0.00-1.00 sec 8.12 MBytes 68.0 Mbits/sec [ 4] 1.00-2.01 sec 11.4 MBytes 94.9 Mbits/sec [ 4] 2.01-3.00 sec 11.2 MBytes 94.9 Mbits/sec [ 4] 3.00-4.01 sec 11.4 MBytes 94.9 Mbits/sec [ 4] 4.01-5.00 sec 11.2 MBytes 94.9 Mbits/sec [ 4] 5.00-6.00 sec 11.2 MBytes 94.5 Mbits/sec [ 4] 6.00-7.00 sec 11.4 MBytes 95.3 Mbits/sec [ 4] 7.00-8.00 sec 11.2 MBytes 94.3 Mbits/sec [ 4] 8.00-9.00 sec 11.2 MBytes 94.6 Mbits/sec [ 4] 9.00-10.01 sec 11.5 MBytes 95.8 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth [ 4] 0.00-10.01 sec 110 MBytes 92.2 Mbits/sec sender [ 4] 0.00-10.01 sec 110 MBytes 92.1 Mbits/sec receiver iperf Done. C:\Users\gonzo\Documents\iperf-3.1.3-win64>iperf3.exe -c 10.250.1.253 Connecting to host 10.250.1.253, port 5201 [ 4] local 10.250.1.110 port 57141 connected to 10.250.1.253 port 5201 [ ID] Interval Transfer Bandwidth [ 4] 0.00-1.00 sec 8.25 MBytes 69.2 Mbits/sec [ 4] 1.00-2.00 sec 11.2 MBytes 94.3 Mbits/sec [ 4] 2.00-3.00 sec 11.4 MBytes 95.5 Mbits/sec [ 4] 3.00-4.01 sec 11.4 MBytes 94.9 Mbits/sec [ 4] 4.01-5.01 sec 11.4 MBytes 94.9 Mbits/sec [ 4] 5.01-6.00 sec 10.9 MBytes 92.0 Mbits/sec [ 4] 6.00-7.00 sec 11.2 MBytes 94.6 Mbits/sec [ 4] 7.00-8.00 sec 11.4 MBytes 95.2 Mbits/sec [ 4] 8.00-9.01 sec 11.4 MBytes 94.9 Mbits/sec [ 4] 9.01-10.00 sec 11.2 MBytes 94.9 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth [ 4] 0.00-10.00 sec 110 MBytes 92.0 Mbits/sec sender [ 4] 0.00-10.00 sec 110 MBytes 92.0 Mbits/sec receiver iperf Done.Server side:
root@nas:~# iperf3 -s ----------------------------------------------------------- Server listening on 5201 ----------------------------------------------------------- Accepted connection from 10.250.1.110, port 57136 [ 5] local 10.250.1.100 port 5201 connected to 10.250.1.110 port 57137 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 7.30 MBytes 61.2 Mbits/sec [ 5] 1.00-2.00 sec 11.3 MBytes 94.9 Mbits/sec [ 5] 2.00-3.00 sec 11.3 MBytes 94.9 Mbits/sec [ 5] 3.00-4.00 sec 11.3 MBytes 94.9 Mbits/sec [ 5] 4.00-5.00 sec 11.3 MBytes 94.9 Mbits/sec [ 5] 5.00-6.00 sec 11.3 MBytes 94.9 Mbits/sec [ 5] 6.00-7.00 sec 11.3 MBytes 94.9 Mbits/sec [ 5] 7.00-8.00 sec 11.3 MBytes 94.9 Mbits/sec [ 5] 8.00-9.00 sec 11.3 MBytes 94.9 Mbits/sec [ 5] 9.00-10.00 sec 11.3 MBytes 94.8 Mbits/sec [ 5] 10.00-10.07 sec 838 KBytes 94.8 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate [ 5] 0.00-10.07 sec 110 MBytes 91.5 Mbits/sec receiver ----------------------------------------------------------- Server listening on 5201 ----------------------------------------------------------- Accepted connection from 10.250.1.110, port 57140 [ 5] local 10.250.1.253 port 5201 connected to 10.250.1.110 port 57141 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 7.40 MBytes 62.0 Mbits/sec [ 5] 1.00-2.00 sec 11.3 MBytes 94.9 Mbits/sec [ 5] 2.00-3.00 sec 11.3 MBytes 94.9 Mbits/sec [ 5] 3.00-4.00 sec 11.3 MBytes 94.9 Mbits/sec [ 5] 4.00-5.00 sec 11.3 MBytes 94.9 Mbits/sec [ 5] 5.00-6.00 sec 11.0 MBytes 92.0 Mbits/sec [ 5] 6.00-7.00 sec 11.3 MBytes 94.9 Mbits/sec [ 5] 7.00-8.00 sec 11.3 MBytes 94.9 Mbits/sec [ 5] 8.00-9.00 sec 11.3 MBytes 94.9 Mbits/sec [ 5] 9.00-10.00 sec 11.3 MBytes 94.9 Mbits/sec [ 5] 10.00-10.07 sec 838 KBytes 94.7 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate [ 5] 0.00-10.07 sec 110 MBytes 91.3 Mbits/sec receiver ----------------------------------------------------------- Server listening on 5201 ----------------------------------------------------------- -
Hi All,
I'm having issues with only getting 10 MB transfers speeds over the network from my unraid box. This is when using either SMB or scp.
However, when I connect a USB external storage, I'm getting 100M+ transfer speeds. I've so far not been able to identify the issue, but I'm getting it on several different NIC's while a docker containers is able to download off the internet at my full internet bandwidth (when I'm not throttling it) at 20MB so I don't think it's a hardware issue at any point, but a network stack issue.
The server is on a bonded 4 port gigabit nic into a gigabite managed switch which all appears to be working fine, so accept when then disks are over worked, I should expect to see around 100MB transfer speeds.
Can any one help me diagnose and resolve please, it's no fun having to run up and down with an external HDD to do large file transfers. Especially as it should be twice as fast over the network over the manual fetch and carry.
Attached are my unraid diagnostics. -
2 minutes ago, g0nz0 said:
If not, this is a copy paste from the docker container edit page:
Name: letsencrypt Repository: linuxserver/letsencrypt Network Type: Custom: br2.2502 Fixed IP address (optional): 10.250.2.101 Subnet: 10.250.2.0/24 Console shell command: Shell Privileged: ON http: Container Port: 80 https: Container Port: 443 Email: [email protected] Domain Name: g0nz0.me.uk Subdomain(s): unifi,plex,firewall, Only Subdomains: true Diffie Hellman: 2048 Validation: http AppData Config Path: /mnt/user/appdata/letsencryptSeriously, it's working again now. The issue must have been an error coming back from the letsencrypt API or certbot and just not being handled well in the code.
If you're a / the dev on this project, let me know if you want some log extracts (specifically what you want from the logs etc) and I'll get them to you to investigate.
-
13 minutes ago, g0nz0 said:
Sorry to be dense, but are they in an xml file somewhere like with rancher and it's API?
If not, this is a copy paste from the docker container edit page:
Name: letsencrypt Repository: linuxserver/letsencrypt Network Type: Custom: br2.2502 Fixed IP address (optional): 10.250.2.101 Subnet: 10.250.2.0/24 Console shell command: Shell Privileged: ON http: Container Port: 80 https: Container Port: 443 Email: [email protected] Domain Name: g0nz0.me.uk Subdomain(s): unifi,plex,firewall, Only Subdomains: true Diffie Hellman: 2048 Validation: http AppData Config Path: /mnt/user/appdata/letsencrypt -
4 hours ago, aptalca said:
Post your container settings
Sorry to be dense, but are they in an xml file somewhere like with rancher and it's API?
-
I'm trying to use this container, which I had working for a single subdomain, but now I'm getting the following after trying to add additional domains:
Plugins selected: Authenticator standalone, Installer None An unexpected error occurred: Traceback (most recent call last): File "/usr/lib/python3.7/site-packages/urllib3/connection.py", line 157, in _new_conn (self._dns_host, self.port), self.timeout, **extra_kw File "/usr/lib/python3.7/site-packages/urllib3/util/connection.py", line 61, in create_connection for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM): File "/usr/lib/python3.7/socket.py", line 748, in getaddrinfo for res in _socket.getaddrinfo(host, port, family, type, proto, flags): socket.gaierror: [Errno -3] Try againI've treid rebuilding the container etc, but I'm not unable to get past this error.
Any one able to help or point me in the right direction as this appears to be an issue with custom internal code so I'm at a loss at being able to debug the issue myself.
Thanks for the help.
Docker containers showing "not available" under the version column.
in General Support
Posted
None of mine are hotio containers 😔