so i’ve updated from v1.1 to v3.1 and i have everything running However, i have noticed that our older topics, that are quite a few years old, are having issues. Here is an example - i have a topic created in 2016 - it has 111 posts. It marked as having a new recent post. If i click on it it takes me to the middle of the time frame history - somewhere in 2020. If i use the scroller on the right to quick jump it wont go past the current post - it also wont go back to the first post in 2016, it only operates somewhere in the middle. If i scroll up and down, then more posts become available, and the scroller will now work in those time frames, but if i go back to 2016 things get a bit buggy - some posts are not displaying at all - refreshing, i can get them up again, but if i go out of the topic, and go back in, im in the same predicament that it drops me in the middle with limited scrolling back and forth. I’m grabbing the time handle top right and dropping it november 2022 and its throwing me back to aug 2019. Try to go to June 2016 and it throws me to April 2019 If i go verrry slowwly and hold the timeline longer it sometimes works. its like a caching issue. EDIT: Just to add - if i go to one that goes back to 2008 and drag the timeline back there - it does nothing - if i then try to browse to another area of the forums i get a server error - and continue to get one until i refresh

It’s so much easier with the URL! Your problem is that you are using the theme-component Post Badges. It’s awful for performance, so please remove it ASAP. Don’t forget to re-enable all you disabled during this journey and thanks for persisting.

[תמונה] bobpies: i get a server error Can you please look for the error on the /logs page and share it here?

there’s nothing in the logs related to it

If you get a server error it will be in /logs. Otherwise it may be a browser level error, so check your browser DevTools.

so couldn’t quite figure out why i’d be getting this, but after checking my own IP on the forums i realised i had cloudflare enabled, so i’m thinking the rate limit is coming because of the cloudflare IPs - have just seen there is a cloudflare template, so i’m rebuilding now. Will let you know if that solves the issue

So no - just to update, My IP has correctly updated inside discourse, but i am still being rate limited. The error page is 429 Too Many Requests NGNIX I’ve checked the logs and the correct IP is being passed through to discourse. Error logs show 2023/02/06 11:32:20 [error] 573#573: *4053 limiting requests, excess: 12.844 by zone "flood", client: xxxx, server: _, request: "POST /mini-profile tried disabling the proxy option in cloudflare to DNS only - no change just clicking on a topic that has had lots of replies throws 429 console errors when receiving even avatar pictures. Running a standard installation on Digital Ocean droplet

You can remove (or comment out) the rate limit template on the first lines of your app.yml and rebuild to see if it “fixes” your issue.

The Nginx 429 has been replaced with Slow down, too many requests from this IP address. Please retry again in 4 seconds. Error code: id_10_secs_limit.

Do you have many tabs open for this site? Close all but one. Also check your phone and other devices. Remove the site from the DiscourseHub app if you are using it.

well i had the logs open but other than that no - i removed from discourse hub but same issue

היסטוריית נושאים לא נטענת כראוי לאחר העברה

תמיכה

bobpies 4 בפברואר,‏ 2023,‏ 2:44pm 5

yes lots in the console - all 429 errors

נושא		תגובות	צפיות
Topics jumping to wrong post Bug	22	1719	28 באוגוסט,‏ 2023
Unfortunately I had to pull the plug Community Building	98	13052	24 בדצמבר,‏ 2022
Real-time updating of topics freezes under high activity Product Support	89	9050	26 בפברואר,‏ 2022
Performance improvements on long topics? Product Support	29	5966	12 ביולי,‏ 2018
Discourse jumps back 20 posts in post history when navigating to new topic Bug	23	3179	28 באוגוסט,‏ 2023

היסטוריית נושאים לא נטענת כראוי לאחר העברה

נושאים קשורים