g0nz0

None of mine are hotio containers 😔

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.

Thanks, that's worked for me.

Yup, same here. Hopefully it will resolve itself soon.

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.

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.

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.

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.

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

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

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 again I'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.