Site has been slow to load ?

[Ricekila]

Problems ?

[Dwight55]

Problems ?

Nahhh . . . just slow pokes I think . . .

I got the same problem most of the time

May God bless,
Dwight

[Ricekila]

I'm getting a few - 503's - before anything comes up alsi --

[Chiefster23]

Slow loading problems this morning too.

[T-Man 1066]

Al Gore's Amazing Internet... sometimes not so amazing. Hmm...

[hawgrider]

Yesterday was slow load for me today seems much better so far.

[Prepared One]

Was slow yesterday for me, but then again, I am pretty slow at times myself.

[Big Ken]

I know sometimes there's an elevated surge in bots, right now I see 564 users online and 6 members, I don't think that number would slow this site but maybe yesterday there were more? I think all sites gets these at certain times of the month as these are mainly from other countries either researching or just seeing in they can get into systems.

[Mad Trapper]

It's been fuked up two days now.

Try to post stuff don't happen, quite a while.......................oh shit! it posted now..........

I'm still happy to have this place. Be good folks....

[MoreAmmoOK]

Been real slow for a couple days for me too. Never know if it's the site or a bottleneck somewhere between me and the site.

[Ricekila]

i usually wait a day or two - before I post anything ---- after all -- I gots verizon -- pure xhit --

[hawgrider]

Could have been the server not sure. Seems to load OK today so far.

[hawgrider]

Slow again today. Ticket submitted to host.

[White Shadow]

Given the average age of the membership, I bet a lot of us are running slow again today.

[MoreAmmoOK]

I seem to be getting hung up on a Swedish owned server in Dallas. Yesterday was the same.

6 49 ms * 55 ms e0-31.core2.okc1.he.net [184.105.253.33]
7 * * * Request timed out.
8 62 ms 30 ms 32 ms dls-b23-link.ip.twelve99.net [62.115.176.9]

[hawgrider]

I seem to be getting hung up on a Swedish owned server in Dallas. Yesterday was the same.

6 49 ms * 55 ms e0-31.core2.okc1.he.net [184.105.253.33]
7 * * * Request timed out.
8 62 ms 30 ms 32 ms dls-b23-link.ip.twelve99.net [62.115.176.9]

Can't say I ever saw that before.

[Mad Trapper]

It's slow here and I'm getting multiple posts of my same post.

[BucketBack]

Quit triple posting when the wheel is spinning :welcomelast:

[MoreAmmoOK]

Looks like I go from my place to my service provider (360communications),
to a Hurricane Electric server in OKC (he.net),
a couple of Swedish owned servers (twelve99) that I believe are in California,
a German owned server (gtt) that I believe is also in CA,
a server that may be in VA,
and finally the OTP server.

Traffic seems to be hanging up between hop 6 and 8. Hop 7 seems to be unreachable so it fails over to the server at hop 8.
Other users may have a totally different route. It all depends on what your service providers server sees as the next hop.

C:\Users\>tracert theoutdoortradingpost.com

Tracing route to theoutdoortradingpost.com [104.192.220.59]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms 192.168.1.1
2 37 ms 13 ms 21 ms 140.82.137.129.360broadband.net [140.82.137.129]
3 39 ms 10 ms 11 ms 140.82.159.149.360broadband.net [140.82.159.149]
4 61 ms 36 ms 26 ms 140.82.158.25.360broadband.net [140.82.158.25]
5 56 ms 46 ms 26 ms 208.93.126.105.threesixtycomm.net [208.93.126.105]
6 * * 46 ms e0-31.core2.okc1.he.net [184.105.253.33]
7 * * * Request timed out.
8 52 ms 42 ms 40 ms dls-b23-link.ip.twelve99.net [62.115.176.9]
9 54 ms 67 ms 31 ms gtt-ic-332415.ip.twelve99-cust.net [213.155.141.19]
10 62 ms 74 ms 61 ms ae14.cr5-lax2.ip4.gtt.net [89.149.180.234]
11 110 ms 85 ms 81 ms fe0-pronethosting.cust.lax02.packetexchange.net [216.193.192.162]
12 108 ms 83 ms 80 ms 104.192.220.59

Trace complete.

[Sasquatch]

Hey, anyone else notice things are running slow? Think I'll go start another thread about it.

Seriously though, it keeps logging me out.

[StratBastard]

Hey, anyone else notice things are running slow? Think I'll go start another thread about it.

Seriously though, it keeps logging me out.

It's doing better now it seems, but yeah sluggish as all hell for awhile.

[hawgrider]

Host is giving me the run around.... no resolve to the issue same shit different day.

[Mad Trapper]

Host is giving me the run around.... no resolve to the issue same shit different day.

Could have to do with recent SCOTUS ruling and loss of 1st amendment rights. FUCKERS CAN CENSOR WHAT EVER THEY WANT TO!!!

[hawgrider]

Seems ok at the moment.

How bout for you?

[StratBastard]

Could have to do with recent SCOTUS ruling and loss of 1st amendment rights. FUCKERS CAN CENSOR WHAT EVER THEY WANT TO!!!

I saw that too. They seem to have said the plaintiffs couldn't prove they were harmed by it. WTF?

[Mad Trapper]

I saw that too. They seem to have said the plaintiffs couldn't prove they were harmed by it. WTF?

ALL Americans WERE HARMED by it. They must have a lot of dirt on the 6.

[MoreAmmoOK]

Still painfully slow for me.

[SOCOM42]

Been slow as shit since yesterday evening, even this posting took a while to load.

I have Spectrum, know nothing about getting from here to there, AND DON'T WANT TO KNOW EITHER.

I swore off of learning anymore about this shit 30+ years ago, refuse to learn anymore about it either.

[hawgrider]

The host seems to be ignoring the problem. I not getting help or answers this time.

[Ricekila]

To me on my end --- for whatever reason -- alot better than it was --

[Coastie dad]

This has been happening on other sites since the 19th. Supposedly has something to do with an update.

Still sounds like government bullshit to me.

[hawgrider]

This is the reason supposedly-

"CPU resource limit of your account was exceeded and which seems to be caused the issue."

Caused by- "I can see that most of the hits came from the bot "facebookexternalhit" and this can be the possible reason for the resource issue."

So yeah not much I can do.... no Idea what facebookexternalhit shit is or how to stop it.

[MoreAmmoOK]

This is the reason supposedly-

"CPU resource limit of your account was exceeded and which seems to be caused the issue."

Caused by- "I can see that most of the hits came from the bot "facebookexternalhit" and this can be the possible reason for the resource issue."

So yeah not much I can do.... no Idea what facebookexternalhit shit is or how to stop it.

Here is a link to solutions. I don't know who has access to implement them.

https://wordpress.org/support/topic/facebookexternalhit-1-1-thousands-of-requests/

[MoreAmmoOK]

The link I posted earlier talks about a file called "robots.txt" that can have "bot" names added to it and it will block the "bots" on the list.

[MoreAmmoOK]

Another solution might be to block the Facebook IP range (157.240.0.0 - 157.240.255.255). If the bot is coming from FB IP space blocking the range would stop it. This would also stop any direct communication from FB to OTP, that may not be a bad thing.

[hawgrider]

Another solution might be to block the Facebook IP range (157.240.0.0 - 157.240.255.255). If the bot is coming from FB IP space blocking the range would stop it. This would also stop any direct communication from FB to OTP, that may not be a bad thing.

Tbe host said there is a robot txt file that can be used. I have no skills for that so I asked them if they will do it. Waiting for a response.

I may also try what you suggested I have the ability to do that I think....

[hawgrider]

The link I posted earlier talks about a file called "robots.txt" that can have "bot" names added to it and it will block the "bots" on the list.

This is the file the host mentioned! You have done this before haven't you MoreAmmoOK

[hawgrider]

Just got a message from the host that said the Facebook bot was disallowed.

Hopefully that helps. Seem like I'm able to navigate smoothly at the momment.

[MoreAmmoOK]

This is the file the host mentioned! You have done this before haven't you MoreAmmoOK

25 years as a hospital Network Administrator left me with a couple skills. I don't have access to the network tools I had at the hospital and don't really want them. I retired last September and have done very little network stuff since but it's 100+ degrees outside and I was bored so I did some diggin round.
If the bot is coming from the FB IP space blocking the IP range would block other FB bots with different names, they only need to change or add one character to the name to get past the "robot.txt" file block.
Blocking the FB IP range may have unintended consequences, I don't know enough about the structure of FB to speculate.
I say Fk FB and anything they try to send to or harvest from OTP.

[hawgrider]

25 years as a hospital Network Administrator left me with a couple skills. I don't have access to the network tools I had at the hospital and don't really want them. I retired last September and have done very little network stuff since but it's 100+ degrees outside and I was bored so I did some diggin round.
If the bot is coming from the FB IP space blocking the IP range would block other FB bots with different names, they only need to change or add one character to the name to get past the "robot.txt" file block.
Blocking the FB IP range may have unintended consequences, I don't know enough about the structure of FB to speculate.
I say Fk FB and anything they try to send to or harvest from OTP.

Looks like I may have to try IP range you suggested. As of this post writing we are still running painfully slow. I'll see if I can figure it out.

[hawgrider]

Another solution might be to block the Facebook IP range (157.240.0.0 - 157.240.255.255). If the bot is coming from FB IP space blocking the range would stop it. This would also stop any direct communication from FB to OTP, that may not be a bad thing.

Not sure how to enter the whole range. Should I enter it like you have it written?

Below is a pic of what Im working with.
I entered the range of IPs but not sure if the way its written is correct. So at this point I did not save that until I got your advise on how to enter that range of IP's in the box.

https://i.imgur.com/eQXIFKO.jpg

[SOCOM42]

It just took quite a while to load to get here.

[1skrewsloose]

It just took quite a while to load to get here.

Weird, I just logged in, went chop-chop. Sumpin screwie goin on round here.

[MoreAmmoOK]

You can try 57.240.*.* or 157.240.0.0/15, both mean the same thing but it looks like the system wants 57.240.*.*. That will ban 131070 IP address but from what I've learned all those IP's belong to FB. There should be no one using those IP's except FB. If the bot is
coming from FB IP space that will stop it.
Site seems to be running pretty good now for me.

[hawgrider]

You can try 57.240.*.* or 157.240.0.0/15, both mean the same thing but it looks like the system wants 57.240.*.*. That will ban 131070 IP address but from what I've learned all those IP's belong to FB. There should be no one using those IP's except FB. If the bot is
coming from FB IP space that will stop it.
Site seems to be running pretty good now for me.

OK I'll try it. 57.240.*.*.

[MoreAmmoOK]

OK I'll try it. 57.240.*.*.

157.240.*.*

looks like I left out a 1 in the last message

[hawgrider]

Its entered so lets see what happens thanks for the help MoreAmmoOK!

[hawgrider]

157.240.*.*

looks like I left out a 1 in the last message

Opps ok I'll go fix it.

[MoreAmmoOK]

Its entered so lets see what happens thanks for the help MoreAmmoOK!

Sorry about the typo it must be 157.240.*.* to exclude all IP's beginning with 157.240
Looks like FB owns all IP's that begin with 157.240.

[1skrewsloose]

For me, the site is as fast as its ever been, just within the last hour. Good thing to know how to stop bots. Hackers crash sites all the time, didn't think OTP was that big of a deal.


Well Shit, that didn't last long, spoke too soon.:(

[hawgrider]

Sorry about the typo it must be 157.240.*.* to exclude all IP's beginning with 157.240
Looks like FB owns all IP's that begin with 157.240.

Got it done.

[MoreAmmoOK]

Got it done.

Could be that the bot is not coming from FB IP space, just has a name that makes it look like FB. If that's the case hopefully HOST support can provide the IP so you can block it. The rabbit hole can get deep.

[Big Ken]

I haven't read much of the posts here but let me just talk a bit, I've never banned a group of IP's just one at a time in V-Bulletin under " Other Banning Options "

What I've done when we had issues is go to '' Who's On Line " and look at the Guests, to the far right you can see their IP's, see if there multiple Guests with the same IP Address, copy paste.

Go into V-Bulletin and run that IP in the IP search area and pick #2, it'll show just how many accounts are under that IP, if a lot or just more than two ban it unless you know them, I've seen 20 plus accounts under one IP before, many are from foreign countries, we have over 94,000 members so it's is very time consuming.

The only way to catch these are when they're On here and the IP shows up, at least that's the only way I know how unless you look at each member that has joined and look at their IP.

Edit: I just looked at all the members and nothing stood out, just check the Guests when you can, we had a huge slow down a couple months ago, our support was no help, G22 went in and shut something off ( I'm not a software guy ) but had to turn it back on a couple days later and it helped.

Good Luck.

[MoreAmmoOK]

Could be that blocking such a large number of IP's has caused the current slowdown.
Hawg, remove the IP block and see if things improve. Contact HOST support and see it there are other bots.

[MoreAmmoOK]

Hawg, get rid of the IP block and contact support and see if they can try this:

block the facebookexternalhit BOT in .htaccess with this:

RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} ^facebookexternalhit/1\.1 [NC]
RewriteRule ^ – [F,L]


This will block FB traffic. There has been a problem for the past few days on multiple websites with FB bots. FB bots tend to ignore the "robots.txt" file. No one knows yet if FB is aware of this proble.

[MoreAmmoOK]

Hawg, get rid of the IP block and contact support and see if they can try this:

block the facebookexternalhit BOT in .htaccess with this:

RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} ^facebookexternalhit/1\.1 [NC]
RewriteRule ^ – [F,L]


This will block FB traffic. There has been a problem for the past few days on multiple websites with FB bots. FB bots tend to ignore the "robots.txt" file. No one knows yet if FB is aware of this proble.

[hawgrider]

Hawg, get rid of the IP block and contact support and see if they can try this:

block the facebookexternalhit BOT in .htaccess with this:

RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} ^facebookexternalhit/1\.1 [NC]
RewriteRule ^ – [F,L]


This will block FB traffic. There has been a problem for the past few days on multiple websites with FB bots. FB bots tend to ignore the "robots.txt" file. No one knows yet if FB is aware of this proble.

Contacted the host with the suggestion so we wait and see.

[hawgrider]

I haven't read much of the posts here but let me just talk a bit, I've never banned a group of IP's just one at a time in V-Bulletin under " Other Banning Options "

What I've done when we had issues is go to '' Who's On Line " and look at the Guests, to the far right you can see their IP's, see if there multiple Guests with the same IP Address, copy paste.

Go into V-Bulletin and run that IP in the IP search area and pick #2, it'll show just how many accounts are under that IP, if a lot or just more than two ban it unless you know them, I've seen 20 plus accounts under one IP before, many are from foreign countries, we have over 94,000 members so it's is very time consuming.

The only way to catch these are when they're On here and the IP shows up, at least that's the only way I know how unless you look at each member that has joined and look at their IP.

Edit: I just looked at all the members and nothing stood out, just check the Guests when you can, we had a huge slow down a couple months ago, our support was no help, G22 went in and shut something off ( I'm not a software guy ) but had to turn it back on a couple days later and it helped.

Good Luck.

Yeah MGO was getting slammed. Pretty much same thing happening here now.

[hawgrider]

Hawg, get rid of the IP block and contact support and see if they can try this:

block the facebookexternalhit BOT in .htaccess with this:

RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} ^facebookexternalhit/1\.1 [NC]
RewriteRule ^ – [F,L]


This will block FB traffic. There has been a problem for the past few days on multiple websites with FB bots. FB bots tend to ignore the "robots.txt" file. No one knows yet if FB is aware of this proble.

Looks like the host is going to do this. The ticket says in progress.

[hawgrider]

MoreAmmoOK the rule has been added by the host.

Let me know you guys if this helped.

Running smooth for me at the moment.

[hawgrider]

Yeah hawg the site is running sweet now yeah fuck off!

Special thanks to MoreAmmoOK for actually figuring this shit hole problem out. Thank you MoreAmmoOK.
Also thanks Big Ken for throwing you 2 cents in and the rest can go fuck yourselves... yeah Im alittle fucking pissed after 4 days of fighting the dumb ass host and dealing with whiney bitchey mother fuckers!

[T-Man 1066]

I really never had issues with the speed of the site. When some of the other members were talking about it being slow, and I didn't experience it, made me wonder if somehow it was only slow at certian times or maybe depending on where we logged in from, or our own ISP providers? But I don't really understand this game a whole lot...

But thanks for taking care of things.

[hawgrider]

I really never had issues with the speed of the site. When some of the other members were talking about it being slow, and I didn't experience it, made me wonder if somehow it was only slow at certian times or maybe depending on where we logged in from, or our own ISP providers? But I don't really understand this game a whole lot...

But thanks for taking care of things.

Yeah it was very intermittent. And annoying as fuck!

[StratBastard]

Yeah hawg the site is running sweet now yeah fuck off!

Special thanks to MoreAmmoOK for actually figuring this shit hole problem out. Thank you MoreAmmoOK.
Also thanks Big Ken for throwing you 2 cents in and the rest can go fuck yourselves... yeah Im alittle fucking pissed after 4 days of fighting the dumb ass host and dealing with whiney bitchey mother fuckers!

Thanx Hawg and MoreAmmoOK!

Sincerely,

a whiney bitchy motherfucker.

[MoreAmmoOK]

Yeah hawg the site is running sweet now yeah fuck off!

Special thanks to MoreAmmoOK for actually figuring this shit hole problem out. Thank you MoreAmmoOK.
Also thanks Big Ken for throwing you 2 cents in and the rest can go fuck yourselves... yeah Im alittle fucking pissed after 4 days of fighting the dumb ass host and dealing with whiney bitchey mother fuckers!

I'm glad I could help, you're very welcome. I feel your pain Hawg. For many years I dealt with working with Corp. networking. I knew what needed to be done but didn't have the access necessary to do it. Had to go through the levels of support to get to someone that had a clue as to what I was talking about. I would finally get to someone and they'd say, "Yeah, you're right", and do what I needed done. Sometimes it would take days and many phone calls and emails. I usually knew the name of someone that could do what I needed done but they couldn't do anything without a "ticket". Creating a ticket meant dealing with low-level lackeys that didn't know what they were doing but wanted to fix it their way even though they were clueless as to what needed to be done. Sometimes it would take weeks to get a very simple but high-level change made.

[Inor]

I really never had issues with the speed of the site. When some of the other members were talking about it being slow, and I didn't experience it, made me wonder if somehow it was only slow at certian times or maybe depending on where we logged in from, or our own ISP providers? But I don't really understand this game a whole lot...

But thanks for taking care of things.

I never had an issue. I've been busy as hell with work, mid-summer round up and other stuff. So my time here has been off-and-on for the last few weeks.

Thanks Hawg for handling it!

[Sparkyprep]

Hawg, I was never having any problems with the site, but thanks for you and moreammo for what you did.

[Jester-ND]

sorry I didn't notice your new haircut..........

[White Shadow]

I'm glad I could help, you're very welcome. I feel your pain Hawg. For many years I dealt with working with Corp. networking. I knew what needed to be done but didn't have the access necessary to do it. Had to go through the levels of support to get to someone that had a clue as to what I was talking about. I would finally get to someone and they'd say, "Yeah, you're right", and do what I needed done. Sometimes it would take days and many phone calls and emails. I usually knew the name of someone that could do what I needed done but they couldn't do anything without a "ticket". Creating a ticket meant dealing with low-level lackeys that didn't know what they were doing but wanted to fix it their way even though they were clueless as to what needed to be done. Sometimes it would take weeks to get a very simple but high-level change made.


Can definitely relate to that story. Throw in a heavy dose of outsourced support, vendors, internal fiefdom wars, and near constant mergers - living the dream (or more accurately the nightmare).

[MoreAmmoOK]

I don't even want to think about vendors and mergers.

[stevekozak]

I was gone on vacation for much of this. I did notice before leaving (and the run up to vacation where I had little to no time to look at the site) that it was very slow. Thank you to hawgrider and to the members that know about this technological shit for fixing it!! It seems to be back to smooth-sailing! I am not sure who the "whiney bitchey mother fuckers" were that could go fuck themselves, but I am glad I was not one of them. :biglaugh: