portboy

Members
  • Posts

    12
  • Joined

  • Last visited

portboy's Achievements

Noob

Noob (1/14)

0

Reputation

1

Community Answers

  1. Genau was ich suche 👍 Ich melde mich. Welche Zeit passt dir am besten?
  2. Mein Server ist mittlerweile über 8 Jahre alt und ich plane die Anschaffung neuer Hardware. Ich kann UNRAID zwar gut konfigurieren und einsetzen, aber mit Hardware kenne ich mich gar nicht aus 😣 Ich suche eine kommerzielle Kaufberatung, welche mir die richtige Hardware für meine Ansprüche zusammenstellt. Klar gibt es hier viele Konfigurationen, aber selbst die kann ich nicht bewerten. Deswegen die Frage nach einem kommerziellen Anbieter 😇 Und ich hoffe nun kein Shitstrom zu erhalten .... 🙏
  3. No Log in Adguard Home I setup the container with his own ip. I started with the default config. I activate "Protokolle" in settings. I tested the running Server with nslookup (nslookup -debug -type=a www.github.com) I tested some ad sites like msn.com and got no ads. So Adguard is working. but ... The statistics are completely empty ... nothing .. nada Where is the issue for this portboy
  4. So I found time to solve my problem 😁 And the problem was not the route. The problem was the DNS. Passing through the card which was assigned to eth0 was the fail. So I just set the pass-through card to eth3 and the other card to eth0. Now it works fine. I love to solve problems by myself 😅
  5. I have aggregate two network ports with mode 802.3ad. But after this, I have no access to the internet from the server. The internal network still works. I think, there is an issue with the routing table. My Server has 4 Network Cards. 1. (eth0) - pass-through to my VM 2. (eth1) - own VLAN for some Docker Container 3. + 4. (eth2 + eth3) - Main Cards for the Server I attached the config 1. and 2. have access to the internet. 3. and 4. have no access to the internet. Th internal Network works fine. My Table Where is the break?
  6. I changed the slot and this works! Thanks!
  7. My VM and passthrough works fine. So no issues in this. But.. I installed a new network card. And this card is in the same IOMMU group like my graphic card. But I don't need the network card within my VM 🤪 it looks like this: How can I unbind only the network card from this group? So I can use the card for the Host and not the VM? I can only (un)select all. The graphic must be in a/this group. Otherwise my VM won't start.
  8. Thanks for this. It's more a workaround, but it works 👍 I think its a bug that only this kind of mcvlan-setup works with stacks/compose and the preserve option.
  9. I’ve set up several containers to use a mcvlan nework. Now I have the issue, that all containers which are setup with portainer stacks can't find the network after a reboot (network xxx not found). It doesn’t matter if I setup the mcvlan only within portainer or with the UNRAID gui for network and docker. The only different is, that the mcvlan which was setup within portainer is gone after restart. Only the config for the mcvlan is still present. The mcvlan whitch was setup only with the UNRAID gui comes back after a restart (but with a new networkID) If I setup the containers not with portainer stacks or the compose plugin, just with the UNRAID gui for new Containers, the containers can automaticly restart after a reboot - so they find the network. But this is for containers with a lot of variables a pain. The docker settings option “PRESERVE USER DEFINED NETWORKS” is always on. Is this a bug or a misunderstanding feature ?
  10. I was on vacation, so thats why my answer needs time. I found the reason. The root couse was sitting in front of the computer. I made I mistake in the docker conf. So my containers are all running correctly.
  11. Thanks! I've done this several times without success. To test my UNRAID config I used the App "mosquitto official" which installs a docker container too. No success. The app just create folders but no config. So the container don't start. It's very strange. I think I must have a faulty UNRAID config wich is the real root cause. But where ....
  12. I gave up …. I’m just testing to move from OMV to unraid. Very important form e are to migrate all my docker containers. As first sept I installed portainer without any issue, top! After this I started to migrate my mosquitto container. So I moved my config folder to the app folder and to be save I run the tool „New Permissions“ and disabled the cache for appdata. I setup a new stack in portainer and run it. This is my stack/compose file: services: mosquitto: container_name: "mosquitto" image: "eclipse-mosquitto:latest" volumes: - "/mnt/user/appdata/mosquitto/config/mosquitto.conf:/mosquitto/config/mosquitto.conf" - "/mnt/user/appdata/mosquitto/data:/mosquitto/data" - "/mnt/user/appdata/mosquitto/log:/mosquitto/log" - "/etc/localtime:/etc/localtime:ro" network_mode: bridge ports: - "1883:1883" - "9001:9001" restart: always So very simple The container started but mosquito wont run. The log shows the error: “No log line matching the '' filter” – so not able to write to log file. I tested some other container/config, no one will run. I think I have an issue with the access rights to the files/folders. But I don’t know how to fix it … What can I do?