mikeylikesrocks

Members
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

3 Neutral

About mikeylikesrocks

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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 yo
  2. 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://
  3. Do you have the Unassigned Devices Plus installed? I believe you need the Plus to be able to read exfat.
  4. 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 a
  5. 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.
  6. Are you able to reach the unraid nginx docker container when using the local address 192.168.100.1:8088 in a web browser?
  7. Are you issuing those commands on the Unraid terminal command line or the Nextcloud container command line? Should be in the Nextcloud container.
  8. 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
  9. You can do this with the External Storage app in Nextcloud. Install that and then map a SMB share from Unraid.
  10. I’m a photographer/videographer that is looking to upgrade my current setup which is an older Mac Mini with DAS Drobo’s. I’ve got local AFP file sharing, a VPN and a CrushFTP server running on it, I also use it backup my laptop with Time Machine and CarbonCopy. I’ve got a bit over 20tb of media at the moment but could easily double that in the coming year (I’m shooting more and more 4k RAW footage as of late). I just use the current setup as an archive and rarely will I edit photos or video off of the setup. Occasionally when I am on the road I will use my vpn to access the mini with VNC a