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

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

-
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).
-
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).
@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 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 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...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. -
To speed up the main site we're setting up a CDN from CloudFlare. This should improve image downloads and speed up things for our US friends.
Hopefully the migration won't affect the site availability more than a few seconds.
We will later look at CDN/caching (at least images) on the forum as well.
-
@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.
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.
-
"Reverse order of thread" sounds good to me. Is this a personal setting I can choose or is it "global"?
-
"Reverse order of thread" sounds good to me. Is this a personal setting I can choose or is it "global"?
-
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.
@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 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...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. -
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.