Djoss

It seems have ways to set the default gateway of a container in bridge network mode: https://stackoverflow.com/a/37047070 I think that if your Docker VPN is also in bridge network mode, you could set the default gw of another container to point to the internal IP of the Docker VPN.

Did you try to increase the resolution of the window with "Display Width" and "Display Height" in container's settings?

Check the few last posts, @Karatekid had the same issue. But you probably need to add the following under the Advanced tab of your proxy host: add_header X-Frame-Options "SAMEORIGIN"; Then environment variable is only for the NginxProxyManager UI itself.

Which VPN docker are you using?

If you trust your local network, then it make sense. Enabling SSL for apps allow traffic between NPM and the apps to be encrypted.

You don't need to remove them. Just let these settings without value and create a new "Path".

Correct, port 443 is needed.

This is done by the client (browser). So the browser connects to port 80, then the web server (NPM) sends a redirect to the client and finally the browser follow the redirect and connects to port 443.

Humm the SSL port is normally used. For example, on the Internet side, when someone connects to port 80 (non-ssl), it gets redirected to the SSL port 443. An SSL connection is never done on port 80.

The Force SSL option redirects users connecting to the non-secure HTTP port (80) to the secure HTTPs port (443). Since NPM is mainly used to access services over the Internet, having an encrypted connection is always better.

But it seems that you still have multiple mount points (multiple '-v' parameters)... Try with only these relevant parts: -e 'AMC_INPUT_DIR'='/media/watch' -e 'AMC_OUTPUT_DIR'='/media/output' -v '/mnt/cache/Media':'/media':'rw' In unRAID you can create the required folders: mkdir /mnt/cache/Media/watch mkdir /mnt/cache/Media/output chown -R nobody:users /mnt/cache/Media

It should work... can you describe the issue you have?

There is no config for this, but you can create a proxy host to access NginxProxyManager UI over HTTPs.

Do you have anything interesting in the container's log?

With your last test, why you are moving file from /media/Temp instead of /media/watch ? For sure, you need to have a single mapping: '/mnt/cache/Media/':'/media':'rw' If you create multiple mount points and you try to move files between them, it won't work.

Then you should look on FileBot forum if there is a known issue about discord web hooks. If FileNot properly reports the configured hook, it seems to me that the issue if with FileBot itself...

So did you add a new Path which maps /mnt/cache/Media from unRAID to /media in the container? And the "Automated Media Center: Input Directory" variable is set to "/media/watch" and "Automated Media Center: Output Directory" variable is set to "/media/output" ?

So probably that the file was not moved within the same physical disk? An instant move could be tricky to achieve, depending on the configuration of your share and if it uses or not the cache drive. Note that some people are mapping their folders under /mnt/cache/ to avoid this issue.

This is possible by adding a "Custom location" under your proxy host. But note that this method is more complex and the application your are proxying may not support this scenario or may require additional configuration.

See :

Yes there are multiple ways you can achieve this. You could for example add a new "Path" for "/media" in the container. Then set the "Input Directory" variable to "/media/<your input folder>" and the "Output Directory" variable to "/media/<your output folder>".

Try the solution described here to make sure new windows are open in new tabs: https://support.mozilla.org/en-US/questions/1193456

Yes, the data is always encrypted. By default, the account password is used to perform the encryption. The save button is disabled only because you have to do some change before being able to save.

Did you installed the correct container via Community Apps? You can also share a screenshot of the container's settings.

No, because there is no version of Flash compatible with Alpine Linux...