Mainfrezzer

most likely not the reason for the problem. The problem is that port 79 is by default "banned" on firefox, chrome etc. You could remove the restriction of the browser by diging in their configs but youre probably way faster with modifying the ident.cfg. as mentioned above

https://docs.unraid.net/unraid-os/release-notes/6.12.4/#fix-for-macvlan-call-traces

https://docs.unraid.net/unraid-os/release-notes/6.12.4/#fix-for-macvlan-call-traces

"Header custom text color" should be the one

"Header custom background color" does affect it aswell

Docker container on a (macvlan/ipvlan)-bridge can reach each other.

The security aspect is network isolation between any of the virtualized enviroments to the host system.

Besides that, theres a checkbox to remove it.

networks: default: name: eth0 external: true Wäre das mindeste, das in der yaml irgendwo stehen sollte, um, in diesem Fall, ins Heimnetzwerk zu kommen.

eth0 wird halt einfach umbenannt zu dem Netzwerk welches gewollt ist.

https://docs.docker.com/compose/networking/#use-a-pre-existing-network

First off all, update to 6.12.4 and apply changes according to the release notes https://docs.unraid.net/unraid-os/release-notes/6.12.4/#fix-for-macvlan-call-traces

or dont use macvlan


secondly, your pcie ssd is the culprit. The cause for it could be multiple things, but the outcome is the same, it drops offline.

Via the GUI you just simply edit the container and add a new path with container path as where its available inside the container and host path where it is on the host machine.

indepth information about docker and bind mounts can be found here https://docs.docker.com/storage/bind-mounts/

It amazes me how one can break stuff and be surprised all of the sudden. 

Turn off the server, plug the unraid usb into a pc and edit the config files so that the vm service(domain.cfg) doesnt start anymore and any other files you edited before. who know what those are.

maybe the syslinux config, any modprobes, etc etc.

those are all nfo files, exclude them. its pointless to checksum them


Those are my settings. 

In the file. the file content has to be flipped by hand. The client_login has to be ID-KEY

The stupid file only gets created once but never edited. So its absolutely pointless to even set the enviroment variables in the first place

Edit:

I just noticed. Your text and image is confusing.

 
 
But the screenshots shows the other way around


12345-abCdeF123gHiJk456789 if thats what you currently have and the key is 12345, it would need to be flipped. Thats what confused me.


Since i dont have an account, this is as far as i can get 

with this file 


i would say, thats enough on my part. no more errors. For any account related inquiries on a varity of website im no help^^


Heres the template ive set up, in case somebody at some point is looking for that particular container aswell
my-hath.xml

Once placed on the usb, you can install it via the "Apps" tab under "previous Apps" or on the docker page via "add container" and then via the drop-down of the templates 

if you have the backup on the array, its relatively simple.

First, install the unassigned devices plugin.

Then, on the main page, you should see all currently not assigned drives listed under "Unassigned Devices"



The red square above will tell you which of the drives has a filesystem, so you can already pick out the drives that are actually data containing drives.

Now you click the upper cogwheels of one drive, that has a filesystem


once on the new page, you enable following setting



then you press save in the bottom left and done afterwards.

Back on the main page, you can mount the drive you just have set to read only. Once mounted, you can explore the disks content
by clicking on the blue links here



and look for the backup.

If the backup is not on that particular disk, take the next disk and continue the steps for each drive until you found the backup. Download it and then you can restore it to your flashdrive.


Edit: I forgot to mention. it probably needs the dynamix file manager aswell. So that would be needed to be installed aswell.

turn low-power mode off

Damit das funktioniert muss bei Docker Host Access enabled sein.

https://docs.unraid.net/unraid-os/release-notes/6.12.4/#fix-for-macvlan-call-traces

FUSE ist nen bisschen funky.

Wenn man /user/ benutzen möchte dann müsste man statt "mv" "cp" nehmen und dann anschließen die original Dateien löschen.

 
#!/bin/bash # Define the path to your BackupScript.sh on the host host_script_path="/mnt/user/misc/scripts/BackupMSSQLdatabases.sql" container_script_path="/home" # define backup locations host_backup_path="/mnt/user/appdata/mssql-production/backup" backup_share="/mnt/user/backup/backup-wawi" # Specify the name or ID of your MSSQL container container_name="MS-SQL-Server-Production" docker cp "$host_script_path" "$container_name":"$container_script_path" docker exec "$container_name" /opt/mssql-tools/bin/sqlcmd -S localhost -U sa -P xxxxx -i /home/BackupMSSQLdatabases.sql # move files to central backup share cp "$host_backup_path"/*.bak "$backup_share/" rm "$host_backup_path"/*.bak  

whats the output if you open the command prompt in windows and type in "nslookup homeserver"? (only the internal ips, if anything shows up)

That seems to be the normal modus operandi for the unraid-api docker, if its the same were talking about. It seems to scrape the webui and you do have to enter your credentials.

Try adding 1.1.1.1 or 8.8.8.8 as dns in unraids networksettings and see if that fixes it.

The Server under 5.X.XXX.112 doesnt seem to have a dns server running

So, ive set it up on my end for visual guidance.

Binhex

 


Chrome:



What you need to enter into the binhex console
 
iptables -A OUTPUT -s 172.17.0.0/16 -d 10.0.0.0/24 -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT && iptables -A INPUT -s 10.0.0.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -m tcp --dport 8080 -j ACCEPT
Change the 10.0.0.0/24 to whatever your network is. 192.168.0.0/24 for example.

Now you can access your Binhex Interface on UNRAID-IP:8181 and your chrome docker is UNRAID-IP:8080


From the chrome docker you can just access the rest from the 172.17.0.X:PORT



As mentioned before, if you go the privoxy route, which i highly recommend, it looks like this:

You change in binhex the Key 8: (ENABLE_PRIVOXY) to "yes"

you open your firefox, chrome, edge, whatever. Go to setting and search for "Proxy"

You set the http proxy to your unraidip:8118

now your browser gets routed through the vpn container and can access 172.17.0.X natively and you dont need to use the iptables command on every binhex-container start.

Die ganze Konfiguration war schon richtig. Das Problem ist der Speedport bzw Unraids implementierung von Wireguard. Das ausbleiben von "Ping" antworten, ich hab nicht genau geguckt welche spezifische icmp Abfrage da gestartet wird, macht Unraids Wireguardclient unnutzbar. Wundert mich dass das nicht schon vorher bemerkt wurde. Die ollen Telekomrouter sind ja doch sehr verbreitet. Aber ich denke mal dass die Leute die sowas hier aufsetzen ne Fritzbox haben und die hat, solange man nicht die Box manipuliert, keine möglichkeit ipv4 icmp anfragen zu blocken.

Achja:
Ich habs jetzt einfach so gelassen dass sich Server 2 zu Server 1 verbindet. Ist ja im Endeffekt egal und wahrscheinlich auch besser weil so Server 1 nicht warten muss dass die öffentliche IP von Server 2 geupdated wird.

The auto-start order is determined by the order the containers are listed on the docker page, from top to bottom. Pre 6.12 you can just drag and drop to change the order, Post 6.12 you need to hit the little lock icon on the right hand side of the menu bar before youre able to do so.

your nic, which i assume is in this case eth1 should show up there and then youll have this option there



that turns eth1 into br1



this is how its looking for me right now

xfs is only available for single disk pools. your option would be zfs mirror in that case.