Djoss

Hopefully I will publish a working image with the latest Filebot version this weekend

Did you try with another browser? If you disable the access list, does it work?

This is currently not something that can be customized. You could try to manually edit files, but these changes would be lost every time the container is re-created/updated.

Are you sure the container is reachable from the internet on port 80 ?

The view the nginx config, it's probably better to look directly at /etc/nginx/nginx.conf inside the container, along with the different included files. You can also look at log files under /mnt/user/appdata/NginxProxyManager/log/nginx/proxy_host-* to maybe get more details on the error.

Is cloud flare reporting the 502 or Nginx Proxy Manger itself? You can look at log files under /mnt/user/appdata/NginxProxyManager/log/nginx/proxy_host-* to see if NPM is actually reached or not.

The issue is now fixed with the latest image. To fix the offline proxy hosts, just edit them and save.

It could be. Maybe logs in the appdata folder could help determining what's happening.

Sorry I'm not enough familiar with the feature to answer. You should try to find how this can be done with pure nginx and if it's possible or not to do it for a particular DNS name. Then we can figure out how to add the config to NPM.

It seems that the "stream" feature of nginx could do the job, but I don't know if this can be mixed with other stuff on the same port...

Port mappings work only when using the bridge network mode. In other modes, you have to work with container's ports (8080 and 4443).

In settings of the Community Apps plugin, you have an option that allow you to get search results from Dockerhub. But since this container is based on jc21's one, you will probably get the same "internal error", which is usually related to an issue with the setup.

It make sense to reverse proxy the admin page. I'm not sure about this the issue you are seeing with the access list, but since there is already a login page, is an access list needed?

What is not working exactly with NPM ? Are you at least able to get the login page?

Update to the latest image, where usage of CRASHPLAN_SRV_MAX_MEM is fixed.

I never tried with iDrive cloud, but if they are offering an S3 compatible API and it doesn't work, maybe you could have better luck if you check with them ?

Yes, keep it to the default value (/output).

Humm privileged mode should not be required. Could you provide the output of : ls -l /dev/sr0 /dev/sg6

In container's log, you should see messages like these, don't you? [cont-init.d] 95-check-optical-drive.sh: executing... [cont-init.d] 95-check-optical-drive.sh: looking for usable optical drives... [cont-init.d] 95-check-optical-drive.sh: found optical drive [/dev/sr0, /dev/sg1], group 19. [cont-init.d] 95-check-optical-drive.sh: exited 0.

ls -l /mnt/user/Downloads ls -l /mnt/user/Downloads/DE

You can look at the "Custom location" tab, but it's much easier and less troubles to use a DNS name for each service you want to reverse-proxy.

Do you see your files in the container ? You can login to the container by clicking its icon (in Docker page) and then select "Console".

Sorry, not sure what happened, maybe a glitch with dupeGuru itself...

Did you check the ownership and permission of /mnt/user/Downloads/DE in unRAID ?

You are in the wrong thread! This container doesn't support Nvidia hardware acceleration...