CloudFlare

[daulagari]

About the forum, see also http://forum.mysensors.org/topic/213/can-not-reply-on-the-forum-or-locked, I can not post or reply using Firefox.

[hek]

Ok, CloudFlare has now been deployed for http://www.mysensors.org. Guess it takes a couple of hours for caches to be filled with content.

Would be great if someone in US/Asia region could give some feedback. Do you notice any speed change when browsing the build instructions?

[BulldogLowell]

@hek said:

Ok, CloudFlare has now been deployed for http://www.mysensors.org. Guess it takes a couple of hours for caches to be filled with content.

Would be great if someone in US/Asia region could give some feedback. Do you notice any speed change when browsing the build instructions?

I'm in China in a small village and can see it is improved.

[hek]

@BulldogLowell said:

I'm in China in a small village and can see it is improved.

Ha.. good to have the mysesnors family team spread around the globe :smile:

[Yveaux]

@BulldogLowell just wondering ; how are your postal delivery times when ordering from China?

[BulldogLowell]

@Yveaux

Well, when I'm home in the US it is usually four weeks. Sometimes three.

Here in china I don't really get the chance to shop!

[Yveaux]

@BulldogLowell thought you were living in China and shopped the hell out there :) It must be electronics heaven over there!

[jendrush]

@hek said:

Ha.. good to have the mysesnors family team spread around the globe

Agree!!!! This is nice:)

[marceltrapman]

@hek maybe things improved for others but since today I have terrible issues with the forum.
Empty topics, boards not showing up, I need to click several times to reply to a topic.

Me not happy :(

[hek]

Strange. The forum should be unaffected. Nothing in the forum.mysensors.org domain is passed through the CDN.
I've kept an eye on the load on the server and it has been low since we separated forum and web to different machines (it's all virtual digitalocean stuff.. ) a couple of days ago. Hmm.. Keep me posted on your status.

[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.