[BUG] TLS and Config about zoraxy

[tobychui]

@PassiveLemon Can you take a look at this? Thanks!

[PassiveLemon]

This one i found out, in the unraid template there was a blankspace after /mnt/user/appdata/zoraxy, now the config is stored correctly.

That's good to hear

That first part seems like it has to do with Zoraxy itself so @tobychui would be able to offer the best support

[tobychui]

Its about TLS, if i activate this on a subdomain, the domain is not working and shows 404. On NPM TLS was working normally.

@SaschMie Yes, that is normal. This "Require TLS" is not the same one as the NPM one. The one in Zoraxy means "the proxy target (192.168.50.219 in your case) require HTTPS connection" instead of "Enabling TLS on this subdomain".

Currently there are no per-subdomain TLS support yet and there are only one global toggle (as shown in the homepage of the management panel). We are working on it now in #44 so please keep an eye on that instead.

[SaschMie]

Actual Zoraxy is running in Docker, the config "/zoraxy/config/" is connected to local "/mnt/user/appdata/zoraxy", but that path is empty. So i have the feeling if the docker is updating, all the config is gone

This one i found out, in the unraid template there was a blankspace after /mnt/user/appdata/zoraxy, now the config is stored correctly.

[tobychui]

This one i found out, in the unraid template there was a blankspace after /mnt/user/appdata/zoraxy, now the config is stored correctly.

That's good to hear

That first part seems like it has to do with Zoraxy itself so @tobychui would be able to offer the best support

For the first part, I am not sure what he is asking (and it seems to be that @SaschMie still trying to figure out how things work in zoraxy). So if the 2nd part get solved and merged, I guess we can close this issue.

[SaschMie]

Its about TLS, if i activate this on a subdomain, the domain is not working and shows 404. On NPM TLS was working normally.

[SaschMie]

ah okay, then seems this case can be closed.