How to not allocate server's 80 and 443 ports just to sniproxy?

[engAmirEng]

hey and thanks for your awesome project,
I wonder if there is a way for me to serve some web applications on the same server as I use to run sniproxy,
I tried to change bind_http and bind_https yaml options but then the my devices failed to connect to the server as dns sever,
what I'm doing wrong? can I put sniproxy http ports behind reverse proxy(Nginx)?

[mosajjal]

your devices (phone PC etc) will not get the info about your port changes, so they blindly try 80 and 443 and nothing else. if you want to re-use 443 and 80 on your server to host other web services as well as sniproxy, you need to either:

• use nginx as the basic listener for 80 and 443, and sniproxy as upstream (without breaking TLS in nginx)
• use 80 and 443 for sniproxy by default, but use the override ACL for your "regular" website and make the upstream nginx or whatever services your TLS-enabled website.

the second option is supported by sniproxy and should be fairly easy to set up.