Forum Activity for @brian

minor bug report

Using Jamroom

I was thinking about this a bit I bet this is the reason you're only seeing 1 account online:

https://easyengine.io/tutorials/nginx/forwarding-visitors-real-ip/

You need to setup nginx to forward the real IP of the user. Let me know if that helps.
updated by @brian: 02/27/18 06:48:40AM

Seo Audit Says "Server should use compression (e.g., gzip)" ?

Using Jamroom

I wanted to follow up on this with some (hopefully) good news - I was looking into this earlier to get an idea of the work involved, and I got an idea of how to possibly make it work without a lot changes. I've coded in the changes needed and it is working - so right now we are just testing it, but if everything goes good it will be in Core 6.1.7 - so coming soon hopefully

The audio import not working

Using Jamroom


Yes - it should be able to handle any number of sub directories. My import test here has ~100 directories (based on artist).

minor bug report

Using Jamroom


Update to version 1.0.2 - I just pushed that out to the marketplace. The "reset" button has been removed since it's functionality is replaced by the core Reset Caches tool.

audio import

Using Jamroom


This is fixed in Audio 2.0.2 - update and profiles should now be active after importing.

minor bug report

Using Jamroom

No - that's not how it works.

minor bug report

Using Jamroom

Like I posted above, I am not able to replicate your issue on any site. I have personally updated multiple sites to use the latest Redis module and do not see your issue. I assume you have enabled bot sessions?

It's not clear what you mean by "when i try reset keys from server browser (thinking that might reset sessions and get it to show right) i get an error". What does that mean? What are you clicking? What error do you get?

minor bug report

Using Jamroom


Yep - click on "View Changelog": https://www.jamroom.net/the-jamroom-network/networkmarket/406/redis-cache

minor bug report

Using Jamroom

The User Accounts 2.3.0 module update changed how "bot sessions" are handled - by default bots no longer create sessions, since there's really no reason to waste system resources on bots. If you really want to see what bots are online, then you need to go into ACP -> Users -> Users -> "sessions" tab and check the "Enable Bot Sessions" option and save. That will re-enable sessions for bots.

This was changed because we've been seeing an increase in how "aggresive" bots are - some are hitting our JR hosting sites dozens of times a second, and they are also tweaking their agent strings and such that thousands of NEW sessions were being created pretty quickly. One site on our network had over 500,000 bot sessions in their session table which was making all session access take about 10 times as long as normal.

So turn it on if you want - I'd recommend leaving it off unless for some reason you really want to see the bots.

Seo Audit Says "Server should use compression (e.g., gzip)" ?

Using Jamroom

Yep I hear you - I've got the work needed on my todo list, but it's kind of "big job" so it will likely be a Core 6.2 or 6.3 feature.