November 25, 20241 yr Please read Setup notes: https://raw.githubusercontent.com/bmartino1/unraid-docker-templates/refs/heads/main/Guides/Quick Start Guide For Rejeto HFS.txt Support from the developer of hfs: https://github.com/rejetto/hfs/discussions Rejetto HFS Access via web your files directly from your disk You be the server! Share files fresh from your disk, with unlimited space and bandwidth. Fast! Try zipping 100GB, downloads starts immediately! Share even a single file with our virtual file system, even with a different name, all without touching the real file. Present things the way you want! Watch all activities in real-time. Control bandwidth: decide how much to give. No intermediaries: give a huge file to your friend without waiting for it to be uploaded on a server first. Intelligent: HFS tries to detect problems and suggest solutions. Expandable: find the right plugin, or make you own. Runs on Node.js has custom plugin support: https://github.com/rejetto/hfs/blob/main/dev-plugins.md Edited November 25, 20241 yr by bmartino1
November 25, 20241 yr Author Currently working with Dev on some fixes to easily streamline the unraid setup, install and go process. For the time being please follow the setup note WIP Discusions: Example: (self singed certs) https://github.com/rejetto/hfs/discussions/801 VFS single docker line for a mount: https://github.com/rejetto/hfs/discussions/792 Other information can be found in the wiki: https://github.com/rejetto/hfs/wiki This app is still in Beta there are some growing pains... Edited November 29, 20241 yr by bmartino1
November 28, 20241 yr Hey, Thanks for releasing the RejettoHFS3 Beta on UNRAID community app. I want to access RejettoHFS3 with my own subdomain (hfs3.mysubdomain.com) using nginx proxy manager. I dont want to upload HTTPS Certificate files or keys; I want NPM to take care of the certificates. I have assigned a static ip (192.168.1.123) to RejettoHFS3 container and set HFS_FORCE_HTTPS: false. Also set HFS_HTTPS_PORT:9443 and HFS_PORT: 9000 on the UNRAID Docker. I can confirm I can access the HFS with http://192.168.1.123:9000/ but when I try to access over https with NPM and my subdomain, I get 502 Bade Gateway openresty error In the HFS options menu below are my settings: What am I doing wrong here? All the other HFS instances on windows PCs are working with the same settings and NPM. Any help would be appreciated! Thanks again!!!
November 29, 20241 yr Author Dealing with ssl certs and sub domain can be a bit tricky. My recommendation is make a self-signed cert and use the reverse proxy subdomain tie in to point to the hfs IP. I'm not 100% familiar with NPM and node JS to assist here. My data on NPM is limited, I have used it in the past. This may not be possible, and I recommend opening a discussion on Rejetto Github Discussion board for further support with reverse proxy and subdomain additions on HFS3. Review previous topics lets encrypt: https://github.com/rejetto/hfs/discussions/346 npm: https://github.com/rejetto/hfs/discussions/822 make a post: https://github.com/rejetto/hfs/discussions *github account... What I can say is in order to make this compatible with Unraid and to set up some things pre-defined in the config. I had to have some duplicate options. *You may need to edit add variables to docker or remove them in favor of editing HFS config in the config folder for some settings... You may need to change some of the default config options, as these will overwrite the hfs config at a docker reboot. Review some of the other template options that are hidden: *Advance Toggle > Show more settings. As you can see, I have an HFS_cert option and HFS_Private_Key option. These may need to point to your custom folder. By Default for use of a self-signed cert the default places the certs to be used in the config folder when created: Example: Since this is in Beta, But to use the certificate folder as I also made a custom path exist for some use case when using your own supplied certificate... One would need to edit HFS_Cert and HFS_Private_Key to point to that within the docker. (or replace the certs in the config folder...) To use a custom "lets encrypt" certificate. This can be done with in the docker by removing the advance hidden .key and .cer option and use the default values which point to where the certs would be when consoled inside the docker per the path folder created. Example: would be: The key is fickle it must be .key format... You can edit your key file as text and copy and paste the data and save the key as ###.key to fix a OpenSSL generated key Edited November 29, 20241 yr by bmartino1 typo-data
November 29, 20241 yr Author 10 hours ago, parhamsan said: Hey, Thanks for releasing the RejettoHFS3 Beta on UNRAID community app. I want to access RejettoHFS3 with my own subdomain (hfs3.mysubdomain.com) using nginx proxy manager. I dont want to upload HTTPS Certificate files or keys; I want NPM to take care of the certificates. I have assigned a static ip (192.168.1.123) to RejettoHFS3 container and set HFS_FORCE_HTTPS: false. Also set HFS_HTTPS_PORT:9443 and HFS_PORT: 9000 on the UNRAID Docker. I can confirm I can access the HFS with http://192.168.1.123:9000/ but when I try to access over https with NPM and my subdomain, I get 502 Bade Gateway openresty error In the HFS options menu below are my settings: What am I doing wrong here? All the other HFS instances on windows PCs are working with the same settings and NPM. Any help would be appreciated! Thanks again!!! you may need to edit the advance option and set http port to 9000 instead of 80 this will server hfs via http over port 9000 However. You're encountering a "502 Bad Gateway" error when attempting to access RejettoHFS3 via your subdomain through Nginx Proxy Manager (NPM). This issue often arises due to misconfigurations in network settings or proxy configurations. Here's how you can troubleshoot and resolve the problem: 1. Network Configuration: Ensure Consistent Docker Networks: NPM and the RejettoHFS3 container should be on the same Docker network to facilitate proper communication. If they're on different networks, NPM might not be able to route requests correctly, leading to a 502 error. Check Current Networks: Use docker network ls to list all networks and docker inspect <container_name> to view the network details of each container. Connect Containers to the Same Network: If they're on different networks, you can connect them to a common network using: docker network connect <network_name> <container_name> Replace <network_name> with the desired network and <container_name> with the name of your container. Enable Host Access to Custom Networks: In Unraid, navigate to Settings > Docker and set "Host access to custom networks" to "Enabled." This allows containers on custom networks to communicate with the host and other networks. 2. Nginx Proxy Manager Configuration: Proxy Host Settings: Scheme Selection: Since you've set HFS_FORCE_HTTPS to false, RejettoHFS3 is serving content over HTTP. In NPM, ensure that the "Scheme" for your proxy host is set to http:// and not https://. Forward Hostname/IP: Use the static IP 192.168.1.123 that you've assigned to the RejettoHFS3 container. Forward Port: Set this to 9000, matching the HFS_PORT you've configured. SSL Configuration: SSL Certificate: In NPM, enable the SSL certificate for your subdomain (hfs3.mysubdomain.com). NPM will handle the HTTPS termination and communicate with RejettoHFS3 over HTTP. Force SSL: Enable this option to ensure all HTTP requests are redirected to HTTPS. Websockets Support: If RejettoHFS3 utilizes Websockets, ensure this option is enabled. 3. Additional Considerations: Firewall and Security Groups: Ensure that there are no firewall rules or security group settings blocking traffic between NPM and the RejettoHFS3 container on port 9000. Container Health: Verify that the RejettoHFS3 container is running properly and listening on the correct port. You can test this by accessing http://192.168.1.123:9000/ directly from a browser or using curl from within the NPM container. DNS Resolution: Confirm that hfs3.mysubdomain.com correctly resolves to your NPM's public IP address. By systematically verifying these configurations, you should be able to identify and resolve the cause of the 502 Bad Gateway error. If the issue persists, consider checking the NPM logs for more detailed error messages, which can provide further insights into the problem. Edited November 29, 20241 yr by bmartino1 data
December 9, 20241 yr Hi and thanks for your effort: I did install the docker several months ago, but I was unable to solve a problem with folders permission (i had to set 777 to the one I'm sharing, as PUID PGID definition wasn't enough?). Where you able to overcome this problem? If yes I don't mind to switch to your container.
December 9, 20241 yr Author 9 hours ago, kaneda79 said: Hi and thanks for your effort: I did install the docker several months ago, but I was unable to solve a problem with folders permission (i had to set 777 to the one I'm sharing, as PUID PGID definition wasn't enough?). Where you able to overcome this problem? If yes I don't mind to switch to your container. I have not had any folder share issues and this sounds like a permission "owner" issues not a permission rwx issues. chmod 777 -R * chown nobody:users -R * *I would advise you rerun docker safe permissions. Unraid Web > tools > docker safe permission... *Turn off docker to apply the permission correctly! Otherwise its how you are telling the dockers PUID, PGID and UMASK 0 - root 99 - nobody 100 - users you can add this to assist in file access... to help answer who touched what where. PUID: PGID: Each docker is different in how it handles these variables... Be sure that key is set to PUID, PGID and UMASK ... Review/see more: Anyways to help understand. In rejetto hfs3 unriad template, I have this set to auto add this folder to the VFS as the main root file system: So in my case /mnt/user/Users is my website root/home page and the folders/files are web accessible. I also don't have any issues with the default template, as it is written in the CA template. I can upload download etc but I do have 777 nobody:users set in that folder. Please double-check your folder pathing and file permissions. Edited December 9, 20241 yr by bmartino1 Data-tyoo
December 10, 20241 yr Thanks, That is more or less what I did. At least I have the confirmation that this is the right path to follow.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.