Starting a few hours, the 502 err started again for me. Since then it was VERY consistent. Always 502 err bad gateway. I was using Win10/Mozilla.
Trying to debug a little, when tested with Tor under a Debian 8 VMware machine, EEVblog was consistently working just fine.
Under Mozilla/Win10 I use to access EEVblog by clicking a bookmark saved long time ago. My Mozilla/Win10 bookmark was pointing to "
https://www.eevblog.com/forum/". If I edit the link in the address bar to use https, "
https://www.eevblog.com/forum/" then it's working OK.
To sum up:VMware/Linux/Tor/http - always working
VMware/Linux/Tor/https - always working
Win10/Mozilla/http - 502 bad gateway
Win10/Mozilla/https - always working
In conclusion, using
https instead of
http helped me to get rid of the 502 error on Win10/Mozila.