I just added some notes in red to that guide to make it easier to change folder names to your language. I think that will be useful in general.
Thanks
Can I ask you another question? when I set the "data" folder in docker compose, can I use a folder located on another disk, in particular an external disk?
If you are installing from scratch maybe this will be useful for you. It includes an NPM container already configured and other containers that may be useful to you.
This is a great help to me. Thank you! In this guide, the installation of containers does not go through portainers, right?
Your original question was a bit disjointed and it appeared you suggested the problem was docker related.
But it's not true! Someone asked me if I had installed from unknown sources or just containers, and I said “just containers”. I didn't say that the problem was attributable to containers. I just answered a question. Go read the conversation and you'll see that you'll agree with me
Alles anzeigenNope, I'm not joking.
You asked for help but didn't give any information. When asked why you thought it was docker related and to point to the docker you suspected you showed a list of 10 or more dockers with no information and no direction of what one you suspected and why. When asked what you have open to the internet you said only port 80 and no explanation about how it is configured, where is it forwarded to/what are you accessing through it, etc.
When asking for help, releasing pertinent information is needed. If the problem is related to internet things (security, getting hacked, dns errors, etc.) releasing the basic information about how you are configured initially will help people spot problems quicker because they won't have to ask for the basic information so they can decide what direction the questions need to go in.
Asking for help with no information will slow down the process. Something that could be spotted and fixed in a day can now take several days, all the while, the security hole that may have been used to hack into your system is still open all because that basic information is not being released.
I have given you all the information I have to the best of my knowledge.
I have to improve? Of course yes but if I had been better I probably wouldn't have needed help.
I also have a life (that doesn't revolve around my home server) that keeps me very busy so I don't understand why you respond to me this way. If you don't want or don't know how to help me then I still thank you and say goodbye
Your release of information when asking for help is very slow.
Are you joking me?
Alles anzeigenJdownloader and Homarr are ran with no PUID which is the same as run with root.
And homarr has RW access to docker.sock.
If it's similar to Heimdall and no login/password was created, you found your hole.
Enough said...
Delete HOMARR container was the frist thing I did
OP, can you show us any ports you have forwarded in your router, to your server?
port 80 only
Can you show the compose text for each container? Im really curious as how this this happened and which container is the problem (if any)
Why are you sure it was containers in portainer (Your response to votdev made it seem like that's what you suspected)... so you were asked which one, and you provided a list of containers. That's what he meant about providing a list not being helpful, as he was under the impression (as was I) that you suspected a docker container caused this, but didn't bother telling us which one.
I think there's a language barrier/misunderstanding here.
I never said I was sure the containers were to blame. I'm not sure who's responsible
You were asked which container was responsible but you provided a list of ten. How is that helpful?
I only have those
Not informative.
What you need?
May we know which one?
Any idea how you got infected? Container or manually installed packages from suspicious sources?
Containers in portainer
In fact, you should review the services you share on the Internet and your security measures so that it doesn't happen to you again. Additionally, it may be advisable to scan your data in some way to ensure that there is nothing harmful.
I changed config.ini file name and the script doesnt work anymore.
Do a new installation.
No other way? 
Hi everyone. I noticed that the CPU of my self-built NAS with openmediavault is at 100% all the time even if it isn't doing anything. from terminal with the "top" command I discovered that there was a "systemsrvc" file that occupied over 300% of the CPU! with the command ps -eo pcpu,pid,user,args | sort -k 1 -r | head -10 I discovered the path
/opt/systemessentials/
In the same folder there is a file called config.ini which contains this
wallet=84EoskGQwWSCR3qrgKh9YYUk8kjTUPzuz122k4SYHFYtAPAgiYBgVDJ12mgEaDW2n833Xm…………
coin=XMR
rigName=openmediavaultI mean, I think there's a mining script running or something. What do you think? What do you recommend me to do?
- You need to use OMV 3.0 (as stated by Ryecoaaron)
...
Hi. Do you know if this is good for OMV4 too?
Thanks
Do you mind sharing how you did it in the plugin?
You have to got a Plex pass. Then, in Plex server options, you have to enable the hw transcoding
Inviato dal mio ONEPLUS A5010 utilizzando Tapatalk
Managed to fix it by replacing "-H fd://" with "-H unix://" in /etc/systemd/system/docker.service.d/openmediavault.conf
It works for me too. Thank you very much
Same problem here 
