Is anyone here having a problem with the site loading?

[85_Ranger4x4]

I need to pin down whether or not this is isolated to the forum.

I started browsing the tech library on break, the offroading section is pretty cool.

It messed up twice, once when I went to look at camping with 4x4Junkies BII but I flubbered the picture on that one, it messed up again going to a pickup camper article that I need to go back to.

 

[Jim Oaks]

Can anyone pin down the date that this started happening?

 

[fastpakr]

I believe it was towards the end of last week, but don't have a way to be more specific.

 

[85_Ranger4x4]

Monday on my work computer, windows did an update mid morning and it has been touch and go ever since.

It wanted to update late last week but I was busy and didn't let it.

 

[85_Ranger4x4]

Fireflox flatlined on me and was taking awhile to come back to life so I switched to Microsoft Edge to experiament and it was the same thing.



It stalled out again when I went to correct the spelling of a word in this post too.

Safari on my phone/ipad hasn't missed a beat yet.

 

[Jim Oaks]

If it was a server issue, you wouldn't be able to connect with any devise. The only common factor I can find is that it involves users that have firefox on their computers.

 

[fastpakr]

It's been reported in Firefox, chrome, and internet explorer.

Any changes to the desktop version of the site recently that wouldn't affect the mobile version? So far, nobody seems to be able to confirm the issue on mobile browsers.

Anything going on with web server updates recently?

Sent from my SM-G960U using Tapatalk

 

[Jim Oaks]

There isn't a mobile version of the forum, just a desk top version.

The only changes to the forum was to add a line of script so that premium members don't see the ads.

<if condition="!is_member_of($bbuserinfo, 9)"> 
$vbphrase[ad_header] 
</if>

That was done on 3/15. I would think that it's either going to work, or give an error. Plus, that should limit the problem to just the forum.

I've seen this error in the logs:

[Thu Mar 29 20:27:44 2018] [error] [client 216.244.66.247] FastCGI: server "/hsphere/local/home/jamesoaks/therangerstation.com/cgi-bin/php55.fcgi" stderr: PHP Deprecated: Assigning the return value of new by reference is deprecated in /hsphere/local/home/jamesoaks/therangerstation.com/forums/includes/init.php on line 55

[Thu Mar 29 20:27:44 2018] [error] [client 216.244.66.247] FastCGI: server "/hsphere/local/home/jamesoaks/therangerstation.com/cgi-bin/php55.fcgi" stderr: PHP Deprecated: Assigning the return value of new by reference is deprecated in /hsphere/local/home/jamesoaks/therangerstation.com/forums/includes/init.php on line 107

[Thu Mar 29 20:27:44 2018] [error] [client 216.244.66.247] FastCGI: server "/hsphere/local/home/jamesoaks/therangerstation.com/cgi-bin/php55.fcgi" stderr: PHP Deprecated: Assigning the return value of new by reference is deprecated in /hsphere/local/home/jamesoaks/therangerstation.com/forums/includes/init.php on line 111

[Thu Mar 29 20:27:44 2018] [error] [client 216.244.66.247] FastCGI: server "/hsphere/local/home/jamesoaks/therangerstation.com/cgi-bin/php55.fcgi" stderr: PHP Deprecated: Assigning the return value of new by reference is deprecated in /hsphere/local/home/jamesoaks/therangerstation.com/forums/includes/init.php on line 119

[Thu Mar 29 20:27:44 2018] [error] [client 216.244.66.247] FastCGI: server "/hsphere/local/home/jamesoaks/therangerstation.com/cgi-bin/php55.fcgi" stderr: PHP Deprecated: Assigning the return value of new by reference is deprecated in /hsphere/local/home/jamesoaks/therangerstation.com/forums/includes/init.php on line 130

[Thu Mar 29 20:27:44 2018] [error] [client 216.244.66.247] FastCGI: server "/hsphere/local/home/jamesoaks/therangerstation.com/cgi-bin/php55.fcgi" stderr: PHP Deprecated: Assigning the return value of new by reference is deprecated in /hsphere/local/home/jamesoaks/therangerstation.com/forums/includes/init.php on line 134

[Thu Mar 29 20:27:44 2018] [error] [client 216.244.66.247] FastCGI: server "/hsphere/local/home/jamesoaks/therangerstation.com/cgi-bin/php55.fcgi" stderr: PHP Deprecated: Assigning the return value of new by reference is deprecated in /hsphere/local/home/jamesoaks/therangerstation.com/forums/includes/init.php on line 142

[Thu Mar 29 20:27:44 2018] [error] [client 216.244.66.247] FastCGI: server "/hsphere/local/home/jamesoaks/therangerstation.com/cgi-bin/php55.fcgi" stderr: PHP Deprecated: Assigning the return value of new by reference is deprecated in /hsphere/local/home/jamesoaks/therangerstation.com/forums/includes/init.php on line 211

[Thu Mar 29 20:27:44 2018] [error] [client 216.244.66.247] FastCGI: server "/hsphere/local/home/jamesoaks/therangerstation.com/cgi-bin/php55.fcgi" stderr: PHP Deprecated: Assigning the return value of new by reference is deprecated in /hsphere/local/home/jamesoaks/therangerstation.com/forums/includes/init.php on line 389

[Thu Mar 29 20:27:44 2018] [error] [client 216.244.66.247] FastCGI: server "/hsphere/local/home/jamesoaks/therangerstation.com/cgi-bin/php55.fcgi" stderr: PHP Deprecated: Assigning the return value of new by reference is deprecated in /hsphere/local/home/jamesoaks/therangerstation.com/forums/includes/class_core.php on line 2552

As well as:

[Thu Mar 29 02:14:38 2018] [error] [client 172.82.185.210] FastCGI: server "/hsphere/local/home/jamesoaks/therangerstation.com/cgi-bin/php55.fcgi" stderr: PHP Fatal error: Call to undefined function get_header() in /hsphere/local/home/jamesoaks/therangerstation.com/wp-content/themes/wp-visual/index.php on line

The php55.fcgi file tells the server to run on PHP 5.5. It's been running on PHP 5.5 since June 2017.

I looked up 'Deprecated' and it says:

Deprecation is a status applied to software features to indicate that they should be avoided, typically because they have been superseded. Although deprecated features remain in the software, their use may raise warning messages recommending alternative practices, and deprecation may indicate that the feature will be removed in the future. Features are deprecated—rather than immediately removed—in order to provide backward compatibility, and give programmers who have used the feature time to bring their code into compliance with the new standard.

 

[85_Ranger4x4]

It's been reported in Firefox, chrome, and internet explorer.

Any changes to the desktop version of the site recently that wouldn't affect the mobile version? So far, nobody seems to be able to confirm the issue on mobile browsers.

Anything going on with web server updates recently?

Chrome seems to be doing the best for a computer, Firefox is the worst. I only use Edge for work stuff so I can't really speak for how it does overall. I don't have Chrome on any machine.

My old out of date Firefox on my old laptop runs TRS fine too.

Safari just doesn't seem to care.

 

[alwaysFlOoReD]

I just tried chrome and it won't let me access TRS. It gives me a warning saying the site is unsafe, similar to FF. When I hit the button that says it will send me to TRS regardless, I get to a page that gives me another warning saying that it can't prove that this is TRS. It shows this "*.fluidhosting.com" as the page. When I click to go then a different page shows up called "Parallels H-Sphere". I think somehow you've been compromised.

 

[97RangerXLT]

Interesting. thus far I have not had any issues, but I have not been on TRS but a few times in the last few days.

Running Windows 10 using Chrome, or Verizon Samsung S8 using tapatalk.

AJ

 

[85_Ranger4x4]

 

[Jim Oaks]

I'm assuming that was from 8:19 am this morning.

 

[91stranger]

I haven't had any issues. The only issues I've ran across are not being able to see pictures. Image says something about third party imaging. Pretty dumb when I want to see something interesting and see people talking about how neat something is when I can only see an automatic error picture.

 

[JoshT]

91stranger, that's a known issue. Almost solely thanks to photobucket deciding they weren't getting enough money, so they are the ones you need to complain to about that. Their response will be that the people who posted those photos need to buy a $100+ annual subscription, which ain't going to happen.

Only way to fix it would be for everyone who posted those photos to go back, upload photos to a different host, and edit every post containing a photobucket link. Even if those posters still had access to the original photo it's unrealistic.

There may also be an app you can add to your browser that will bypass photopuckets third party block. Haven't tried it myself so can't tell you more.