502 on Tunnel while IP:port still works

I also have the same problem. 502 will appear after running for a while, but accessing through ip:port is normal.

Please do not hijack other topics with similar, yet completely unrelated issues. It makes it harder for the Community to help either of you. I have moved your post to its own topic so that you may provide more details about your specific problem without having a negative impact on anyone else.