L0rdRaiden

I think is "custom.cnf" file in mariadb docker folder but be sure your Mariadb docker log (accesible from unraid interface) doesnt give you this warning, you have to fix it changing permisions chmod 0444 cfg/mysql-5.7/custom.cnf

https://docs.nextcloud.com/server/13/admin_manual/configuration_database/bigint_identifiers.html Supossely I can fix this with this command but when I run it on the nextcloud docker console I get root@44d2677c0b9a:/$ sudo -u www-data php occ db:convert-filecache-bigint sudo: unknown user: www-data sudo: unable to initialize policy plugin root@44d2677c0b9a:/$

Take a look to this configuration file https://www.c-rieger.de/nextcloud-installation-guide-apache2/ maybe this expire_logs_days = 10 can help.

I have done a fresh install following spaceinvaders video and I get the following error how can I apply this fix in the docker container? occ db:convert-filecache-bigint

Can you add the lport parameter to the interface?

@aptalca In addition to Modsecurity it would be nice to add as well authelia, is a two factor authentication that would secure anything you publish on the web. https://www.authelia.com/ https://github.com/clems4ever/authelia https://www.reddit.com/r/selfhosted/comments/7gv51h/simple_to_deploy_2fa_nginx_proxy/ Honestly I don't know how hard it would be to add Modsecurity or authelia and make it easy for the less experienced users.

is available for nginx https://www.nginx.com/blog/compiling-and-installing-modsecurity-for-open-source-nginx/ https://github.com/SpiderLabs/ModSecurity-nginx

Are there any plans to include ModSecurity in this docker? https://www.modsecurity.org/ https://hub.docker.com/r/owasp/modsecurity-crs/

Thanks it works now The only issue is that my docker container has a capital leter "Netdata" and only works if I call it "netdata" instead. In the nginx conf file doesn't make any difference if I call it "Netdata" It doesn't bother me a lot but it is possible to have a capital letter in the docker name and change the conf file accordingly?

Oh, thanks, I just watch it and followed it but I'm stuck when I try to change my dockers to the "proxynet" network. previously they were "custom:bro" or "bridge" I get an error like this root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='Radarr' --net='proxynet' --ip='192.168.1.205' --cpuset-cpus='4,6,5,7' -e TZ="Europe/Paris" -e HOST_OS="Unraid" -e 'PUID'='99' -e 'PGID'='100' -p '7878:7878/tcp' -v '/mnt/user/Storage/Downloads/':'/downloads':'rw' -v '/mnt/user/Storage/Movies/':'/movies':'rw' -v '/mnt/user/Docker/Radarr':'/config':'rw' 'linuxserver/radarr' c034520ca18928484bd0140c2cc31100864be179d22fdcee0f7c8fd761191cc1 /usr/bin/docker: Error response from daemon: user specified IP address is supported only when connecting to networks with user configured subnets. how can I fix it? When I dont place a fix IP and I just let fix IP address empty and network type "custom: proxynet" I get this There is nothing in port mappings so it doesn't work either Then is possible to do the same with a webserver that I have in a virtual machine o unraid?

Is there any tutorial on how to setup "something" with this docker? I have been reading a little bit but there are 104 pages and I'm not and IT pro.

I have notice that when something new is downloaded by Rtorrent some other programs, sonarr, plex, etc. have issues to modify or delete the information, and it only works well when I run the "New Permissions" utility in Unraid. Is there a way to avoid this? maybe Rtorrent is writing the files with some special permissions? Thanks in advance.

what is the advantage of using this instead the unraid interface? Is there any incompatibility or issue? BTW I am getting this error, I have ssh enable in unraid, and I have installed netcat

Please register here for the new beta of Storj. https://blog.storj.io/post/175853164878/announcing-the-network-v3-farmer-waitlist

Do we need to install openvm tool package? Or this is only for VMware hypervisor?

What do you mean by automated repo? what it does differently? How is SIA working for those playing with it? I'm not running it since you have to pay 50$ or so to become a miner but I'm thinking again about it. BTW SIA requires a good graphic card but storj does not, right?, maybe this is why SIA isn't working properly for some while using it in docker.

Every time I download something new I dont have permisions to modify it with samba (windows explorer), then I run un unraid tools->new permisions and it works How can I fix this permanently? the share is shared as public.

do you lose lots of peers on Storj when the server is up many hours/days? I start the nodes with around 150 peers, after a day or so I have 30-50 less and the number is smaller every day, so I usually restart the docker. Do you experience the same problem? is normal?

I get this ouput root@MediaCenter:~# docker exec StorjMonitor storjshare stop 8fx70bbceb6xefd9d1325x6b5eeeaf44c0fxxxxx missing node id, try --help root@MediaCenter:~# docker exec StorjMonitor storjshare start 8fx70bbceb6xefd9d1325x6b5eeeaf44c0fxxxxx no config file was given, try --help What am I missing? After a few days some nodes lose almost all peers so this is why I want to restart them. Is this normal?

In case someone has the same problem an run Tool->New permisions and now it works

What network type are you using with StorjMonitor container?

I am using storjmonitor container now I have the main node plus 4 more but the container is only mapping 4 ports 172.17.0.2:4000/TCP172.17.0.2:4000 172.17.0.2:4001/TCP172.17.0.2:4001 172.17.0.2:4002/TCP172.17.0.2:4002 172.17.0.2:4003/TCP172.17.0.2:4003 I have fix it adding the port mapping manually. But I think the problem is that it only map the ports the first time you create the container if you change the number after that the port mapping doesn't update Now is working but for some reason, I don't know why, my first node has always a high delta ┌─────────────────────────────────────────────┬─────────┬──────────┬──────────┬─────────┬───────────────┬─────────┬──────────┬───────────┬──────────────┐ │ Node │ Status │ Uptime │ Restarts │ Peers │ Allocs │ Delta │ Port │ Shared │ Bridges │ ├─────────────────────────────────────────────┼─────────┼──────────┼──────────┼─────────┼───────────────┼─────────┼──────────┼───────────┼──────────────┤ │ 6ec5490584a014188a8e3ae366d5e17ed7xxxxxx │ running │ 7m 51s │ 0 │ 138 │ 0 │ 103ms │ 4000 │ 11.99GB │ connected │ │ → /storj/share │ │ │ │ │ 0 received │ │ (TCP) │ (12%) │ │ ├─────────────────────────────────────────────┼─────────┼──────────┼──────────┼─────────┼───────────────┼─────────┼──────────┼───────────┼──────────────┤ │ 4dd54ed8e3b68fe752618e17055e4eec52xxxxxx │ running │ 7m 49s │ 0 │ 139 │ 0 │ 7ms │ 4001 │ 9.92GB │ connected │ │ → /storj/Node_1/share │ │ │ │ │ 0 received │ │ (TCP) │ (10%) │ │ ├─────────────────────────────────────────────┼─────────┼──────────┼──────────┼─────────┼───────────────┼─────────┼──────────┼───────────┼──────────────┤ │ dcea81e7741aeb8db49174ac5821d9035xxxxxxx │ running │ 7m 47s │ 0 │ 93 │ 0 │ 7ms │ 4002 │ 12.02GB │ connected │ │ → /storj/Node_2/share │ │ │ │ │ 0 received │ │ (TCP) │ (12%) │ │ ├─────────────────────────────────────────────┼─────────┼──────────┼──────────┼─────────┼───────────────┼─────────┼──────────┼───────────┼──────────────┤ │ 4428e5e0f2e84b4e9e9e86df57f381dcdxxxxxxx │ running │ 7m 46s │ 0 │ 120 │ 0 │ 2ms │ 4003 │ 8.56GB │ connected │ │ → /storj/Node_3/share │ │ │ │ │ 0 received │ │ (TCP) │ (9%) │ │ ├─────────────────────────────────────────────┼─────────┼─────���────┼──────────┼─────────┼───────────────┼─────────┼──────────┼───────────┼──────────────┤ │ c3c26bcc0e3af7d2d8add82d602a1xxxxxxxxxxx │ running │ 7m 44s │ 0 │ 104 │ 0 │ 8ms │ 4004 │ 1.15GB │ connected │ │ → /storj/Node_4/share │ │ │ │ │ 0 received │ │ (TCP) │ (1%) │ │ └─────────────────────────────────────────────┴─────────┴──────────┴──────────┴─────────┴───────────────┴─────────┴──────────┴───────────┴──────────────┘ BTW how can I restart a node without restarting all of them?

Thanks @Jcloud, does SIA supports multi nodes? How do I add storage folders in the share? Could you explaint please a little bit more the setup until the end? I have followed you steps but right now I don't know if it's working or not. BTW it says that I need 2000 SC (52$) to start to host... I guess I need to put some money in, or is there a way to avoid this? BTW all of you please register in filecoin early miner program https://filecoin.io/ https://docs.google.com/forms/d/e/1FAIpQLSfdFpWhJj8OIGA2iXrT3bnLgVK9bgR_1iLMPdAcXLxr_1d-pw/viewform?c=0&w=1

I have change the default port of rutorrent, in the docker template, software and rtorrent.rc file After many days and restarts I get in my fw (pfsense) many blocks to the port 51413 which was the previous default, it like every minute a get few of those. Does it make sense? why are there IP trying to contact to the old port? is the setting still maybe embeded somewhere in docker? ruttorents reports my current port as open and is working fine bur having so many ip's calling to the old/default rtorrent port smells bad. May 6 00:31:36 WAN Default deny rule IPv4 (1000000103) 91.105.85.183:51043 xx.xxx.xxx.146:51413 TCP:S May 6 00:31:36 WAN Default deny rule IPv4 (1000000103) 91.105.85.183:27913 xx.xxx.xxx.146:51413 UDP May 6 00:31:39 WAN Default deny rule IPv4 (1000000103) 91.105.85.183:51043 xx.xxx.xxx.146:51413 TCP:S May 6 00:31:39 WAN Default deny rule IPv4 (1000000103) 91.105.85.183:27913 xx.xxx.xxx.146:51413 UDP May 6 00:26:04 WAN Default deny rule IPv4 (1000000103) 68.63.214.93:36440 xx.xxx.xxx.146:51413 TCP:S May 6 00:26:05 WAN Default deny rule IPv4 (1000000103) 68.63.214.93:36440 xx.xxx.xxx.146:51413 TCP:S May 6 00:26:07 WAN Default deny rule IPv4 (1000000103) 68.63.214.93:36440 xx.xxx.xxx.146:51413 TCP:S

I'm using this template, I guess is still valid right? https://hub.docker.com/r/oreandawe/storjshare-cli/