[[Support] selfhosters.net's Template Repository]

You should be able to go into the prefs.xml file located in your Crushftp9 folder located in your Appdata (if you use the standard locations) share.  Open the XML file and the banned ip's should be listed.  Below is an example of a banned IP.  Look for your ip or the ip of your reverse proxy server and delete that block.

 

<ip_restrictions_subitem type="properties">
			<start_ip>61.75.30.52</start_ip>
			<type>D</type>
			<stop_ip>61.75.30.52</stop_ip>
			<reason>05/29/2019 02:43:48.047:password attempts</reason>

 

After you have deleted the banned ip you can search for the "never_ban" and add your lan range.

 

<never_ban>127.0.0.1,10.0.*,172.*</never_ban>

 

Then save and restart the docker container.  

[[Support] Linuxserver.io - Heimdall]

2 hours ago, greg_gorrell said:

Anyone know why every item I create on the page ends up with a hyperlink of "10.0.0.2:8443/10.0.0.100:80" instead of simply the address to the container  

Are you just entering just the IP address or the full “http://10.0.0.100:80”?  I was having the same problem till I put in http://

[(SOLVED) Can not access an Unassigned Device in Krusader]

Do you have the Unassigned Devices Plus installed?  I believe you need the Plus to be able to read exfat.

[docker containers can't access from the Intelnet]

The problems you are having are due to your network setup and not Unraid.  You would probably get better help by asking questions on reddit r/homelab or 

r/HomeNetworking or another forum that is more specific to networking problems.

 

openwrt is acting as another firewall limiting access to anything on the bridge network which you proved by changing your nginx container to be on br0 which solved your problem.  If you want nginx to work on the bridge network you also need to forward ports from router to openwrt to 192.168.100.1  or you need to change your gateway to the router address.  Either solution should solve your problem.

[docker containers can't access from the Intelnet]

have you tried putting the nginx docker container on the br0 network and assigning it its own ip address and then changing your port forwarding on the router to point to the new docker ip address?

 

Also your network topography isn't very clear from your picture. Looks like you are running openWRT as  a VM and then using that as your gateway?  Yet in our diagram you have your unraid server showing to be routed to the router (192.168.100.100)?  From your routing tables that doesn't seem to be the case.  You have no default route from the unraid server to the router only uraid to br0.  So if I am understanding it correctly it is actually like this:   

unraid server (192.168.100.1) ----> openWRT VM (192.168.100.250) -----> router 192.168.100.100.  ---> modem.  

 

Unless you have the openWRT VM set as the DMZ you should have portforwarding setup from the router to openwrt and then from openwrt to unraid?  So it would need two different levels of portwarding.

 

Have you spun up another docker image besides nginx and then done all of the portforwarding to rule out ngnix being the cause?  And how about taking openwrt out of network and having a default route from unraid to the router?  This would rule out the openwrt vm from being the cause.

 

And how do you know all of your port forwarding is done correctly?  What makes you say that?  

[docker containers can't access from the Intelnet]

Are you able to reach the unraid nginx docker container when using the local address 192.168.100.1:8088 in a web browser?

[[Support] Linuxserver.io - Nextcloud]

Are you issuing those commands on the Unraid terminal command line or the Nextcloud container command line?  Should be in the Nextcloud container.

[MacOS share problems...]

Have you tried using the connect to server function in Finder by hitting command-K and then connecting with the unraid server's IP address instead of hostname?  Should look like this smb://10.0.1.1/SHARE_NAME/ You obviously need to replace the ip with your server ip and share name.  I can rarely connected to my unraid server by clicking on it's icon in a standard finder window and even when I do I occasionally get similar symptoms to you (not being able to write the share)

 

Also if you have the login credentials for the unraid share saved in Keychain Access you can try deleting the credentials there which will force you to re-enter them next time you connect to the share.  This has also solved previous connection issues I've had.

[[Support] Linuxserver.io - Nextcloud]

14 hours ago, IKWeb said:

 

 

What I would like to do tho is add the shares I already have on my UNRAID server into next cloud. 

 

Can this be done? Any info on how to do it? 

 

You can do this with the External Storage app in Nextcloud.  Install that and then map a SMB share from Unraid.