3 ms·

Thanks, took me a while to find the issue. I had a feature where if the same client (by IP address) starts another job, their previous jobs are deleted. But af

by bemmu 7y ago

Thanks, took me a while to find the issue. I had a feature where if the same client (by IP address) starts another job, their previous jobs are deleted. But after I added secure websockets support by proxying through nginx, all IP addresses from the server's point of view became "127.0.0.1" and every job would just be deleted when a new one came in, because they all had the same IP.

uranium 7y ago
I keep getting countdowns from 8 or 15 to 1 [or partway there], and then "onclose", with the UI saying "Lost connection to server, please try again in a bit". For variety now and then I get a 502 somewhere in websocket setup. When it is counting down, it takes 100+% CPU. The sample render looks really cool, though. Nice project; thanks for sharing it.
huhtenberg 7y ago
Cheers, thanks a bunch.