L0rdRaiden
-
Posts
568 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by L0rdRaiden
-
-
Are there any plans to include ModSecurity in this docker?
-
59 minutes ago, aptalca said:
First set it to the regular bridge and set up your port forwards if you like. Save and exit. Go into the container settings one more time, change it to proxynet, don't enter an ip and hit save.
Unraid doesn't recognize your proxynet as a custom bridge network (assumes it is macvlan) so if you try to change port mappings after selecting proxynet, unraid won't do it properly.
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"
Quoteinclude /config/nginx/proxy.conf;
resolver 127.0.0.11 valid=30s;
set $upstream_netdata Netdata;
proxy_pass http://$upstream_netdata:19999;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.
-
Terminal doesn't work it I get a
502 Bad Gateway
nginx Error and the log says this. What I can do? Before upgrading to 6.6 it was working
Sep 22 11:43:15 MediaCenter nginx: 2018/09/22 11:43:15 [error] 5547#5547: *124623 upstream prematurely closed connection while reading response header from upstream, client: 192.168.1.110, server: , request: "GET /webterminal/ HTTP/2.0", upstream: "http://unix:/var/run/ttyd.sock:/", host: "192.168.1.200", referrer: "https://192.168.1.200/Dashboard"
Sep 22 11:43:27 MediaCenter nginx: 2018/09/22 11:43:27 [error] 5547#5547: *124623 connect() to unix:/var/run/ttyd.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.110, server: , request: "GET /webterminal/ HTTP/2.0", upstream: "http://unix:/var/run/ttyd.sock:/", host: "192.168.1.200", referrer: "https://192.168.1.200/Dashboard"
Sep 22 11:43:51 MediaCenter nginx: 2018/09/22 11:43:51 [error] 5547#5547: *124623 connect() to unix:/var/run/ttyd.sock failed (111: Connection refused) while connecting to upstream, client: 192.168.1.110, server: , request: "GET /webterminal/ HTTP/2.0", upstream: "http://unix:/var/run/ttyd.sock:/", host: "192.168.1.200", referrer: "https://192.168.1.200/Dashboard" -
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.
-
-
It would be nice if someone can assemble a docker with accestream and a proxy
Acestream: http://www.acestream.org/
Some "unofficial dockers:
https://github.com/munkie/acestream-docker
https://github.com/ikatson/docker-acestream-proxy
https://github.com/sergelevin/docker-acestream-debproxy
A proxy:
https://github.com/ikatson/docker-acestream-proxy
The purpose is to use acestream to stream content and use the proxy to be able to reproduce it in plex or any other media player.
How I would like to use it, is just opening acestream to enter the "url" (or send the url somehow with the smartphone) and then automatically the http proxy would start to publish the content.
In any case, thanks in advance.
- 1
-
Please register here for the new beta of Storj.
https://blog.storj.io/post/175853164878/announcing-the-network-v3-farmer-waitlist
-
On 7/1/2018 at 6:17 PM, SimonF said:
Anyone else noticed an issue with the performance of VM when parity check running. When VM becomes unresponsive CPU on both cores allocated is 100%. VM is Win10 with graphics card passthru.
Diags attached, but i cannot see any issues logged in syslog etc. I do also have Plex running in Docker with DVR recording also.
I dont recall seeing same symptoms on 6.5.2, currently Parity Check is at 86%
I have similar problems when another VM or unraid is doing something heavy, VMs and unraid does not respond well, I think qemu is not well implemented because on proxmox everything is rock solid no matter what load it has
-
I have a Ryzen 2400G so for know I guess it will be mission impossoble to passthrough the iGPU.
Taking into account this is there any way to play simple 2D games on Windows 10?
I have tried with QXL but when I run the game nothing happens, is there any alternative or any way to get 2D or 3D games acceleration? like in virtualbox
-
4 hours ago, saarg said:
I don't think ryzen was released when kernel 2.16 was released ?
Might be 4.16 then ?
-
Do we need to install openvm tool package? Or this is only for VMware hypervisor?
-
I have a ryzen 2400g is there any way to passthrough the iGPU to win 10?
I read somewhere that it might require kernel 2.16, it's true? Can't I do it with the current version?
-
On 6/12/2018 at 9:06 PM, Jcloud said:
Good line-item to note there. I wasn't able to play around much with that feature yet, as I have no Sia-coin to for the collateral portion of contract.
For those interested in bleeding-edge I've finally gotten around to making an automated build repo for my Storj. Bad news is, I can't make repo zugz/r8mystorj be automatic without first deleting it - which might be confusing. So, if you want the automated repo, in your Docker template change, "zugz/r8mystorj:latest" to "zugz/r8mystorj-auto"
Second, I'm a bit stunned: there have been 1.7K pulls of my repo! I know this count includes repeated pulls (ie not unique users; just total pulls) but dang, I'm impressed by the number.
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?
-
On 5/6/2018 at 2:24 PM, Jcloud said:
Nope not that I what I can tell. Also the value of the market, and the fact they have have no corporate customers, I wouldn't worry about it.
Should be possible to use the Docker container as a blockchain miner using CPU resources. That is a limit setup by Sia, I'm sure it's part of their ICO to create value in the token, it's pay-up or mine for the quantity. Also, I think the cash/tokens are used as collateral if you fail as host in your contract.
Yeah the template doesn't change auto-magically, you do have to make the changes manually. Correct, it will only list the four ports, because those are the only ones "exposed," by the Dockerfile, but since you've added the port field on the container; then listed 4000-4010 (or whatever is the range which covers your number of nodes) it will work - Should list (TCP) for all of them, if you see (UPNP) then in the config file for effected node change: (from false)
"doNotTraverseNat": true,
docker exec yourStorjContainerName storjshare stop dcea81e7741aeb8db49174ac5821d9035xxxxxxx docker exec yourStorjContainerName storjshare start dcea81e7741aeb8db49174ac5821d9035xxxxxxx
I get this ouput
root@MediaCenter:~# docker exec StorjMonitor storjshare stop 8fx70bbceb6xefd9d1325x6b5eeeaf44c0fxxxxx
missing node id, try --help
root@MediaCenter:~# docker exec StorjMonitor storjshare start 8fx70bbceb6xefd9d1325x6b5eeeaf44c0fxxxxxno 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?
-
On 5/6/2018 at 7:25 PM, Connor Moloney said:
I may be wrong but I had similar issues when the files weren't named with their extension in the name e.g. .mkv or whatever the media type is
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?
-
12 hours ago, Jcloud said:
Yeah that's the official docker 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:4003I 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
-
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 -
4 hours ago, Jcloud said:
I just did a search for "Storj" and found my template in CA store. I would try deleting the container (your contracts should be on storage array and be untouched) and image in webui, then click on Add container scroll through and find the saved entry for Storj, and rebuild. - That's what I would try first, it would be much easier, and should be just as effective. Then go back to auto-updates plugins & containers; disable and re-enable auto update for Storj.
I've had terrible luck try to take multiple containers and have them run under a single daemon.
FYI: the code tweak was a bug for new users, and the multiple node creation routine.
I'm using this template, I guess is still valid right?
https://hub.docker.com/r/oreandawe/storjshare-cli/
[Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)
in Docker Containers
Posted
is available for nginx https://www.nginx.com/blog/compiling-and-installing-modsecurity-for-open-source-nginx/
https://github.com/SpiderLabs/ModSecurity-nginx