-
[7.1.2+] Unraid becomes unresponsive when behind an NGINX reverse proxy
Yes, kind of, i have unRAID in a VM on Proxmox (yes i know i know), i have set it up to accept all my vlan's, but in unRAID i have set up my primary ip (no vlan) as main ip, and one of the vlan's for my docker containers, can give diagnostic file or screenshots of the setup it needed
-
-
[7.1.2+] Unraid becomes unresponsive when behind an NGINX reverse proxy
Did anyone solve this? I am struggling with the same, trying to use a domain internally so i dont have that nagging "error" message when i try to access the ip directly (and easier to write the domain name)
-
Cant access smb from different vlan after update from 7.1.3 to 7.1.4
If anyone els have a problem with something similar, i found out that i didnt read the documentation thoroughly enough (suprise suprise), i had set my docker settings to "macvlan" instead of "ipvlan", witch is needed when using docker on a vlan that is untagged from the main lan adapter
-
Cant access smb from different vlan after update from 7.1.3 to 7.1.4
sure, thank you
-
Cant access smb from different vlan after update from 7.1.3 to 7.1.4
no one have any advice to what i can try? can give more details than the diagnostics log if needed
-
Cant access smb from different vlan after update from 7.1.3 to 7.1.4
Hi, im having a weird network issue after upgrading from 7.1.3 to 7.1.4 where i cant access smb shares from other vlans than my main lan, im guessing it has something to do with some network changes in Unraid since i have my docker containers on a different vlan than unraid itself All the containers themselves work fine after the update tho and i can still reach all of them through my nginx reverse proxy (lives outside unraid on my proxmox server) To info, it starts wokring again as soon as i downgrade to 7.1.3 again Ive added the diagnostic data, let me know if i can provide anything more captainamerica-diagnostics-20250716-1757.zip
Exodus
Members
-
Joined
-
Last visited