Daniel Iantosca reports that a new installation times out on its news page.

The error is immediately reproducible. The problem is that the URL its referring to for the JSON is wrong.

http://192.168.1.4/rivers/admin/River3.js

I see the problem. There's no port in the URL. This breakage was caused by an optimization I introduced recently. There are URLs in the stats table, and the one we're looking for is there, the problem is that it's not correct. So when we use it, the request fails and the page is broken. We should only use the URL if it works.

Automatically generating the URL is guesswork, and it's problematic. The optimization works great on seasoned installations, but better left alone on new ones. I undid the optimization and released river2suite.viewNews.