Toby Chui

Closing due to inactive and unable to reproduce issues.

It is interesting to see you reported an issue from a feature that Zoraxy doesn't yet support! (TLS support on management interface) For the warning message `Failed to get network...

Closing this as this issue is inactive and the redirection is not a bug caused by Zoraxy

@thespyboss Glad that you like this project! I can provide you 1 to 1 support for exchanging a quick start guide written by you :D Please contact me directly via...

Here is the [Getting Started](https://github.com/tobychui/zoraxy/wiki/Getting-Started) guide. Closing this issue as no one picking this up and write the wiki page.

@barto95100 I am guessing you have another reverse proxy sits between Zoraxy and the web server that handle websocket request, in which the reverse proxy override some of the critical...

@AzAel76 From what I know, the bad handshake error was not raised from the code base of Zoraxy. I guess it is from much lower level ([gorilla websocket](https://github.com/gorilla/websocket/issues/780) I guess)...

I am not sure about opnsense and running inside proxmox, but there are users who run their Zoraxy inside proxmox and ACME tools is usable when Zoraxy is directly exposed...

Hi @Dvalin21, As Zoraxy is not Apache or Nginx that has their own static web server (at least not before 2.6.7), the proxy root is designed for you to forward...

Closing this due to inactive and outdated.