Danuel

no mate, i still have the problem

mange eventually to add users

i did saw that guide but does not help me from minio terminal, mc admin user add myminio newuser newuser123 if i type minio -h in terminal / # minio -h NAME: minio - High Performance Object Storage DESCRIPTION: Build high performance data infrastructure for machine learning, analytics and application data workloads with MinIO USAGE: minio [FLAGS] COMMAND [ARGS...] COMMANDS: server start object storage server gateway start object storage gateway FLAGS: --certs-dir value, -S value path to certs directory (default: "/root/.minio/certs") --quiet disable startup information --anonymous hide sensitive information from logging --json output server logs and startup information in json format --help, -h show help --version, -v print the version so i don't see any option to add more users

thank you, worked but, there is any way to add more users ?

ignore mu post, i just wake up, did not read properly remove / 'overwrite.cli.url' => 'https://nextcloud.protech.my/', should be => 'https://nextcloud.protech.my',

What do you see in letsencrypts logs ?

i just changed the subdomain server_name nextcloud.*; nextcloud.subdomain.conf

happy that you finally manage made it work

Hi, does anyone have minio.subdomain.conf.sample , if not can anyone please help me with that

does anyone have a Minio.conf.sample file for letsencrypt ?

Well ya, that how i understand, did not worked for me with A record, and only if i enabled proxyed

well, what i have done in close flare i enabled proxyed and i used a wildcard but you have to use a A name if your IP is static and if is dynamic a CNAME

hi, does anyone have a filestash.conf for letsencrypt ?

are you using cloudflare ?

have you look if you have a conflict on port ? do you get any error in the logs ?

can't update docker containers ul 9 17:27:31 Seven nginx: 2020/07/09 17:27:31 [error] 3808#3808: *2519285 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.1.76, server: , request: "GET /plugins/dynamix.docker.manager/include/CreateDocker.php?updateContainer=true&ct[]=binhex-jackett HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.66", referrer: "http://192.168.1.66/FixProblems//Docker"

after i add the collabora conf file i get this message in letsencrypt i get error nginx: [emerg] "resolver" directive is duplicate in /config/nginx/proxy-confs/collabora.subdomain.conf:6 and network is custom a fix that is working for me is to remove the line 6 (resolver 127.0.0.11 valid=30s;) in my case that was on line 6

downgraded to 6.8.2 same problem Jun 22 11:06:27 Tower nginx: 2020/06/22 11:06:27 [error] 19213#19213: *11348 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.1.76, server: , request: "POST /Apps/AddContainer?xmlTemplate=default:/tmp/community.applications/tempFiles/templates-community-apps/BinhexsRepository/binhex-binhexjackett-latest.xml HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.82", referrer: "http://192.168.1.82/Apps/AddContainer?xmlTemplate=default:/tmp/community.applications/tempFiles/templates-community-apps/BinhexsRepository/binhex-binhexjackett-latest.xml" and i can confirm that changing the DNS does not fix the problem

fresh wipe of all HDD, community application installed only try to install 1 docker container Jun 22 10:05:50 Tower nginx: 2020/06/22 10:05:50 [error] 2117#2117: *1789 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.1.76, server: , request: "POST /Apps/AddContainer?xmlTemplate=default:/tmp/community.applications/tempFiles/templates-community-apps/linuxserversRepository/linuxserver-heimdall-latest.xml HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.82", referrer: "http://192.168.1.82/Apps/AddContainer?xmlTemplate=default:/tmp/community.applications/tempFiles/templates-community-apps/linuxserversRepository/linuxserver-heimdall-latest.xml" and i dont even installed letsencrypt or nginx, so is either a problem with OS Unraid 6.8.3 or with community application

another strange thing i noticed after i delete docker.img was, that old docker container were still present

yes on first docker, i had only community application plugin installed and no docker container and still get this error nginx: [error] 2132#2132: but there was no nginx installed or letsencrypt i am formatting now the HDD to see if i will receive same error

recent update after fresh install, same error when trying to install ducker apps Jun 20 08:20:49 Tower nginx: 2020/06/20 08:20:49 [error] 2132#2132: *7757 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.1.76, server: , request: "POST /Apps/AddContainer?xmlTemplate=default:/tmp/community.applications/tempFiles/templates-community-apps/linuxserversRepository/linuxserver-letsencrypt-latest.xml HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.82", referrer: "http://192.168.1.82/Apps/AddContainer?xmlTemplate=default:/tmp/community.applications/tempFiles/templates-community-apps/linuxserversRepository/linuxserver-letsencrypt-latest.xml" i did delete at first the docker.img same result, then i reinstall unraid same error, either is a problem with community application or unraid

Backup with CA backup or just normal backup in windows? And i do not care aboUt disk assignments, i want to wipe all and redo all, because of that error i cant think at other solution

how can i reinstall unraid ? just wipe the USB and reinstall ?

Booting back, i did try to manual update a container and still getting same error even if community application is not installed Jun 14 11:11:08 SEVEN sSMTP[27392]: Creating SSL connection to host Jun 14 11:11:08 SEVEN sSMTP[27392]: SSL connection using TLS_AES_256_GCM_SHA384 Jun 14 11:11:10 SEVEN sSMTP[27392]: Sent mail for d*******@outlook.com (221 2.0.0 closing connection j190sm17707335wmb.33 - gsmtp) uid=0 username=root outbytes=1102 Jun 14 11:18:33 SEVEN webGUI: Successful login user root from 192.168.1.76 Jun 14 11:21:25 SEVEN nginx: 2020/06/14 11:21:25 [error] 8023#8023: *3216 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.1.76, server: , request: "GET /plugins/dynamix.docker.manager/include/CreateDocker.php?updateContainer=true&ct[]=binhex-nzbhydra2 HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.82", referrer: "http://192.168.1.82/Docker" Jun 14 11:21:31 SEVEN kernel: veth7dc0c23: renamed from eth0 Jun 14 11:21:31 SEVEN kernel: docker0: port 4(vetha2aaf22) entered disabled state Jun 14 11:21:33 SEVEN avahi-daemon[4110]: Interface vetha2aaf22.IPv6 no longer relevant for mDNS. Jun 14 11:21:33 SEVEN avahi-daemon[4110]: Leaving mDNS multicast group on interface vetha2aaf22.IPv6 with address fe80::bc21:d2ff:fe7b:9b9e. Jun 14 11:21:33 SEVEN kernel: docker0: port 4(vetha2aaf22) entered disabled state Jun 14 11:21:33 SEVEN kernel: device vetha2aaf22 left promiscuous mode Jun 14 11:21:33 SEVEN kernel: docker0: port 4(vetha2aaf22) entered disabled state Jun 14 11:21:33 SEVEN avahi-daemon[4110]: Withdrawing address record for fe80::bc21:d2ff:fe7b:9b9e on vetha2aaf22. Jun 14 11:22:42 SEVEN kernel: docker0: port 4(veth364205f) entered blocking state Jun 14 11:22:42 SEVEN kernel: docker0: port 4(veth364205f) entered disabled state Jun 14 11:22:42 SEVEN kernel: device veth364205f entered promiscuous mode Jun 14 11:22:42 SEVEN kernel: IPv6: ADDRCONF(NETDEV_UP): veth364205f: link is not ready Jun 14 11:22:42 SEVEN kernel: docker0: port 4(veth364205f) entered blocking state Jun 14 11:22:42 SEVEN kernel: docker0: port 4(veth364205f) entered forwarding state Jun 14 11:22:42 SEVEN kernel: docker0: port 4(veth364205f) entered disabled state Jun 14 11:22:53 SEVEN kernel: eth0: renamed from vethb11e020 Jun 14 11:22:53 SEVEN kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth364205f: link becomes ready Jun 14 11:22:53 SEVEN kernel: docker0: port 4(veth364205f) entered blocking state Jun 14 11:22:53 SEVEN kernel: docker0: port 4(veth364205f) entered forwarding state Jun 14 11:22:54 SEVEN avahi-daemon[4110]: Joining mDNS multicast group on interface veth364205f.IPv6 with address fe80::c84b:eeff:fea2:b1c3. Jun 14 11:22:54 SEVEN avahi-daemon[4110]: New relevant interface veth364205f.IPv6 for mDNS. Jun 14 11:22:54 SEVEN avahi-daemon[4110]: Registering new address record for fe80::c84b:eeff:fea2:b1c3 on veth364205f.*. seven-diagnostics-20200614-1126.zip