ados

Members
  • Posts

    71
  • Joined

  • Last visited

Recent Profile Visitors

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

ados's Achievements

Rookie

Rookie (2/14)

2

Reputation

  1. Apologies if this is more network related than UNRAID but I think its worth the investigation. I recently switched from consumer routing hardware to a more enterprise solution from Ubiquity, UniFi Dream Machine. Once implemented the UNRAID interface (GUI) was no longer accessible. Since I had setup different VLANs and firewall restrictions following least privileged access I was quick to blame my implementation. I slowly peeled back the restrictions and nothing worked, it still resulted in this: Eventually I lowered all security until there was none and while I can ping the server the GUI would not load. I confirmed using GUI mode that the server was fine and both DHCP and DNS matched the testing desktop devices. Finally I identified that https://IP:443 worked once trusted cert is dismissed. This lead me to the "solution", add the host URL UNRAID redirects to into the PC host file which then works as before. This confirms its the combination of UDM and UNRAID not UNRAID itself but it does raise the question of how to fix at the router or UNRAID level. The most obvious solution would be a custom DNS record for the UDM but agaisnt my knowedge before purchasing the device it doesn't support custom DNS records despite years of cries from customers. Most use a secondary DNS device such as Pi-hole. However that just adds extra complexity and devices to manage, are their any UDM owners out there that have a solution to this? Thanks 😃
  2. I have updated the guide to remove many errors, sorry. 🙁 I have also found a compatibility issue with new versions of NGINX Manager. Through comparing differences in previous backups to new versions I have resolved the issue and added to the guide.
  3. I cannot seem to get this to work for me. Based on what has been said, it does not wait to start the docker but instead starts it and then asks to wait. If that's the case it would explain why its not working for me, I'm intending to control the internal IP order as I need dockers to communicate directly and thus need the IP to remain the same. I am aware of the custom IP but cannot use that, am I up a creek without a paddle?
  4. The main issue with that application is support which has decreased over time. You need to stay on older versions if you wish to have plugin support. Keeping it short as this belongs over on the Deluge forum, you need to be on a 2.0.X version. 2.0.4 is a good one. 😉
  5. Ha ha let me know when virtual beers are a thing. Sorry for the delay, work has been keeping me busy. Good to hear your liking Organizr, it does incorporate all your instances into one place for easy management. Since your using Swag and I don't have too much knowledge on that other than its also NGINX I might not be able to provide much direction. The "include" shouldn't be needed, as for the "auth_request" part you can either have this specified for each sub domain or in the main function of the config file. The reason you would divide it would be to allow greater control over which sub domains are authorisation controlled. However, you can just specify in the sub domain "auth_request off;" to omit it from authentication. As for Ombi, I didn't have that issue as I stopped using it in favor of another platform and I never liked the mobile app. All my interaction was from the web interface which I found better and can be pinned as such to the mobile home screen it more or less functions as an app. Since the Ombi app would have its own http/s requests to the docker instance it would have its own cookies and authentication, this causes an issue as it never contains the authentication cookie for Organiser which is passed in any web browser. I don't think there will be an easy way around this without using a firewall.
  6. Sorry I don't know what your asking. Are you wanting to know if your NGINX is secure?
  7. Don't apologise, looking for improvements and better systems is the idea but for your use case openVPN is the way to go. You already have PIA which is the best place to start for port forwarding servers.
  8. Wireguard is a new VPN protocol written from the ground up as an alternative to the openVPN standard. However, unless its changed fundamentally it works only with UDP and not TCP, for what your doing the slightly slower but more reliable TCP of openVPN will be better. You should also be focusing on support which with Wireguard is less since its new, less server nodes support it and you need nodes with port forwarding support which are already a rare before looking at Wireguard.
  9. Wireguard is not required, if your in this forum then speed is not going to improve anything when you can be using TCP and not UDP.
  10. @wobblewoo if your not too committed to your VPN provider switch to PIA. They are affordable, fast and support port forwarding which you generally need for what your doing.
  11. @tetrapod you might find Organizr interesting, check out the new guide.
  12. For those wanting to restrict login access to their sub domains or sub-folders from public access through NGINX Proxy Manager I have created a guide to use Organizr. Its a powerful SSO based platform for accessing multiple resources and allows for configuration using their API to restrict access to URL resources without authentication to Organizr. Guide:
  13. For those wanting to restrict login access to their sub domains or sub-folders from public access through NGINX Proxy Manager I have created a guide to use Organizr. Its a powerful SSO based platform for accessing multiple resources and allows for configuration using their API to restrict access to URL resources without authentication to Organizr. Guide:
  14. For those wanting to restrict login access to their sub domains or sub-folders from public access through NGINX Proxy Manager I have created a guide to use Organizr. Its a powerful SSO based platform for accessing multiple resources and allows for configuration using their API to restrict access to URL resources without authentication to Organizr. Guide:
  15. For those wanting to restrict login access to their sub domains or sub-folders from public access through NGINX Proxy Manager I have created a guide to use Organizr. Its a powerful SSO based platform for accessing multiple resources and allows for configuration using their API to restrict access to URL resources without authentication to Organizr. Guide: