CloudFlare

[marceltrapman]

@hek I will. Maybe it is just a coincidence but it sure was terrible today.
I will let you know when I experience the same issues tomorrow or the day after.

[marceltrapman]

OK, included are 2 screenshots.
One was taken while loading (or not) a topic and the other was taken while loading the boards/home page.
The time interval was a little over 2 hours.
And no, I did not make the screenshot before or while loading but really after (during loading there is a cross visible on the right hand side of the input field.

[Yveaux]

@marceltrapman Don't worry man! It's not cloudflare, but the forum software :-)
I'm also having the same troubles, especially on Android...

[hek]

Yea, something is definitely wrong (I've gotten the blank page also). But it is problematic to find the source. I'm suspecting a ngnix misconfiguration. See lots of the following in the nginx log (while nodebb report nothing suspicious):

2014/07/29 18:01:44 [error] 37#0: *356437 upstream timed out (110: Connection timed out) while connecting to upstream, client: XXXXXXX, server: forum.mysensors.org, request: "GET /topic/242/wireless-nrf24l01-sniffer-for-mysensors/404 HTTP/1.1", upstream: "http://XXXXXXXX:4567/topic/242/wireless-nrf24l01-sniffer-for-mysensors/404", host: "forum.mysensors.org", referrer: "http://forum.mysensors.org/topic/242/wireless-nrf24l01-sniffer-for-mysensors/38"
2014/07/29 18:01:53 [error] 37#0: *356439 upstream timed out (110: Connection timed out) while connecting to upstream, client:XXXXXXXXX, server: forum.mysensors.org, request: "GET /api/widgets/render?location=sidebar&template=home.tpl&url= HTTP/1.1", upstream: "http://172.17.0.3:4567/api/widgets/render?location=sidebar&template=home.tpl&url=", host: "forum.mysensors.org", referrer: "http://forum.mysensors.org/"
2014/07/29 18:02:04 [error] 33#0: *356496 upstream timed out (110: Connection timed out) while connecting to upstream, client: XXXXXXXXX, server: forum.mysensors.org, request: "GET /plugins/nodebb-plugin-emoji-extended/images/grinning.png HTTP/1.1", upstream:       "http://172.17.0.3:4567/plugins/nodebb-plugin-emoji-extended/images/grinning.png", host: "forum.mysensors.org", referrer: "http://forum.mysensors.org/topic/175/open-source-home-automation-software/66"
2014/07/29 18:02:05 [error] 37#0: *356400 upstream timed out (110: Connection timed out) while connecting to upstream, client: XXXXXXXXX, server: forum.mysensors.org, request: "GET /socket.io/1/xhr-polling/DUIl4fNbuNdLgvgIVTj9?t=1406656614013 HTTP/1.1", upstream: "http://XXXXXXXXX:4567/socket.io/1/xhr-polling/DUIl4fNbuNdLgvgIVTj9?t=1406656614013", host: "forum.mysensors.org", referrer: "http://forum.mysensors.org/search/hc-sr501"

Need some time to investigate (read google).

[Yveaux]

@hek Sorry can't help you with this one...
Good luck! Would be great if all difficulties could be solved as many of us experience them.
(Btw I'd rather have you spend your precious time on the MySensors library, but that's the price you pay for fame :facepunch: )

[hek]

@Yveaux

(Btw I'd rather have you spend your precious time on the MySensors library, but that's the price you pay for fame facepunch )

Yeah, me too!

Any good sysadmin out there with some time over?

[hek]

Turned off proxy_buffering. Lets test this for a while to see if it helps.

Also noting we're running an pretty old ngnix version. Will update this as well.

[hek]

nginx updated to 1.6.0

[marceltrapman]

@hek said:

nginx updated to 1.6.0

Let's hope this improves things.
I still wonder why this issue first popped up only yesterday and not before...

[hek]

@marceltrapman

Could be because of this change:
http://forum.mysensors.org/topic/213/can-not-reply-on-the-forum-or-locked/6
Unlikely but possible.
Websocket proxying was pretty new when we picked up nginx 8 months ago. Hopefully the update I just did stabilize things.

[Damme]

@hek For the last couple of days the forum have been somewhat unsuable for me. And the worst is long threads, it only loads a small number of posts at the time, and alot of times it just stops and dont load the latest one.

[hek]

@Damme

Yes, I know. I've experienced this for longer than a couple of days also. Using the arrows in header works for me (but they don't exist on mobile!). The forum software is buggy and I'm keeping an eye on the development regarding this issue.

One alternative is to reverse order of thread (latest first) until this has been fixed. There is also an pagination alternative in the admin but nothing happens if i select it.

[korttoma]

"Reverse order of thread" sounds good to me. Is this a personal setting I can choose or is it "global"?

[Yveaux]

@korttoma the the 'sort by' button on the bottom right of the page...

[Yveaux]

@hek said:

There is also an pagination alternative in the admin but nothing happens if i select it.

Even worse, I tried urning it on and previous/next page buttons appear on the bottom of the screen. If you press them nothing happens, so view is limited to first 20 replies in a topic...
I still experience the empty page displays now and then...

[hek]

@Yveaux

Ahh. yes.. now I see the pagination! Didn't realize I had to activate it for my own user. Thanks! Paging seems to work fine here in chrome (mac) and on my Android.

Yes, I also still get 504 (time-out) sporadically on the websocket connection. Mostly after my computes has been asleep.

[Yveaux]

@hek said:

work fine here in chrome

Not in chrome x64 on Win7....