Unless I am overlooking some bit of configuration, it is not possible to utilize OWTF on a remote server. The access to the file storage, which is normally assigned to port 8010, only seems to work for localhost:8010 i.e. you have to have a local OWTF server.
This seems like a shortcoming if you want to share a server with a small workgroup as a collaboration aid during testing.
Additionally, the config options that do exist (SERVER_ADDR, UI_SERVER_PORT, FILE_SERVER_PORT) don't seem to offer the possibility of utilizing OWTF remotely over a single standard web port, like 443.
I have also not discovered an effective way of inserting a reverse-proxy, like nginx, to solve this dilemma. The browser client seems to "think it knows best" in trying to reference files on 'localhost' directly, instead of just relying on a URI scheme that would allow a proxy to direct requests to appropriate endpoints/ports, if that sort of backend architecture is truly desirable.
Unless I am overlooking some bit of configuration, it is not possible to utilize OWTF on a remote server. The access to the file storage, which is normally assigned to port 8010, only seems to work for localhost:8010 i.e. you have to have a local OWTF server.
This seems like a shortcoming if you want to share a server with a small workgroup as a collaboration aid during testing.
Additionally, the config options that do exist (SERVER_ADDR, UI_SERVER_PORT, FILE_SERVER_PORT) don't seem to offer the possibility of utilizing OWTF remotely over a single standard web port, like 443.
I have also not discovered an effective way of inserting a reverse-proxy, like nginx, to solve this dilemma. The browser client seems to "think it knows best" in trying to reference files on 'localhost' directly, instead of just relying on a URI scheme that would allow a proxy to direct requests to appropriate endpoints/ports, if that sort of backend architecture is truly desirable.